Database Users

[ROM - 1.2] Flashback Update 10.3 (12/07/2011)

UPDATE - Flashback 10.3 (12/07/2011) - See Downloads (below)
STANDARD DISCLAIMER:
USE AT YOUR OWN RISK. By running this firmware, you agree that there is the possibility that you may brick your device. You agree that only you are responsible and no one else is responsible for supporting you if that occurs.
Acknowledgments
Roebeet, Mrguy, Pershoot, Zebwen, Clemsyn and all the Adam and VEGA developers, for this excellent port. If you have contributed something I used let me know and I will add you here.
Pre-requisites
1. Setup and learn how to use nvflash. This is your backout in case something bad happens, so I would recommend you understand how to use this, in advance.
2. Have your device on a stock 1.2-based ROM / mod baseline. For example, build 4349 is the latest 1.2-based stock ROM, as of this writing.
NVFlash
-NVFlash rev5 by tlb1961 (Detailed Instructions for Windows and Linux included in download)
Installation for 1.2-based stock (also, see Changelog)
Options for Installing Flashback:
Option 1 (Update)
Download/Copy Flashback-10.X.zip to Internal SDCard (USB storage)
Shutdown and boot into ClockworkMod recovery.
1. Wipe cache partition
2. Advanced > Wipe Dalvik cache
3. Backspace/Return key (back to Main menu) < Very Important Here [DO NOT REBOOT RECOVERY]
4. Install from SDCard
5. Choose zip from SDCard
6. Navigate to and choose Flashback-10.X.zip
7. Accept/Choose Flashback-10.X.zip
8. Backspace/Return key (back to Main menu)
9. Reboot system
Option 2 (Clean)
Download/Copy Flashback-10.X.zip to Internal SDCard (USB storage)
Shutdown and boot into ClockworkMod recovery.
1. Wipe data/Factory reset
2. Wipe cache partition
3. Advanced > Wipe Dalvik cache
4. Backspace/Return key (back to Main menu) < Very Important Here [DO NOT REBOOT RECOVERY]
5. Install from SDCard
6. Choose zip from SDCard
7. Navigate to and choose Flashback-10.X.zip
8. Accept/Choose Flashback-10.X.zip
9. Backspace/Return key (back to Main menu)
10. Reboot system
Option 3 (Wipe & Format)
Download/Copy Flashback-10.X.zip to Internal SDCard (USB storage)
Shutdown and boot into ClockworkMod recovery.
1. Wipe data/Factory reset
2. Wipe cache partition
3. Advanced > Wipe Dalvik cache
4. Backspace/Return key (back to Main menu) < Very Important Here [DO NOT REBOOT RECOVERY]
5. Moints and Storage:
> Format boot
> Format cache
> Format data
> Format system
> Format sdcard - OPTIONAL (FOR ADVANCED USE ONLY)
6. Backspace/Return key (back to Main menu)
7. Install from SDCard
8. Choose zip from SDCard
9. Navigate to and choose Flashback-10.X-signed.zip
10. Accept/Choose Flashback-10.X-signed.zip
11. Backspace/Return key (back to Main menu)
12. Reboot system
Disaster recovery - 'tlb1961' NVFlash (see above)
Flashback Team Members
HiTekRedneck
jazzruby
OtherGuy
rowwor
Sharpe351
TEK112
tlb1961
tlbardelljr
Downloads
Flashback 10.3 (updated 12/07/2011)
Download Link: http://dev-host.org/dn0au4ajdokt/Flashback-10.3-signed.zip
MD5: ce7898ecb48b0a0a9d0b0d45d99b9669
Pershoot's kernel 2632.48 11/24/2011 (included in Flashback 10.3)
Download Link: http://dev-host.org/ol6timuj4aw1/pershoots_2632.48_gb_newbl-112411-signed.zip
MD5: 6606eb179ff22d4738da0b62e14187bd
Clemsyn's kernel Honeycomb Trial 5
Download Link: http://www.mediafire.com/?7s7c1anfv1pnfe3
Changelog
Flashback (see Post #2)
Pics

Changelog:
Flashback 10.3
Updated kernel/WiFi modules
Recommended install method for Flashback 10.3:
'Update' install for 10.2 > 10.3
'Clean' install for all others
Flashback 10.2
Files added:
GalleryNew3DGoogle
Files updated:
Browser (Homepage)
Superuser (3.0.7) - If doing an 'Update' install, you must 'Uninstall update' from Settings > Applications > All
framework-res (Wallpaper)
updater-script (corrected 1 line)
boot.img (new kernel)
Files removed:
TitaniumBackup (issues) - If doing an 'Update' install, you must 'Uninstall update' from Settings > Applications > All
StatusbarToggle (issues)
Wallpapers (app not stock)
[/system/data] folder (contains 3rd party appps and will provide as a separate download)
Recommended install method for Flashback 10.2:
'Clean' install, due to system apps, i.e. TitaniumBackup and Superuser
'Update' install, (for experienced users and from 10.1 only) - You must 'Uninstall update' for TitaniumBackup and Superuser from Settings > Applications > All
-JR-

loving it
The latest update is great! Still having a problem with the flashplayer causing crashes though..any recommendations other than the hacked apk that is available in the build?

Thanks JR,
This will always be the ROM running on my GTAB. You are a great asset to the gtab community!
tlbardelljr

This isn't a new problem (I've had it with all the Honeycomb ROMs I've used), but when I hold the power button and choose "Recovery", my G Tablet doesn't boot into recovery, it just reboots normally. I can only get into recovery by holding the volume up button while rebooting. Is this normal? It isn't really a big deal, but I thought I'd report it.
I'm running Flashback 10.3.

JazzRuby, Thank you so much for posting an update for the Gtab, any new ROM is a welcome, but more so for a HC!!!
So again Thanks!!

Just got the gtab from a friend. This ROM is amazing, but no working flash player, can't play anything. Any ideas?

Seanbest said:
Just got the gtab from a friend. This ROM is amazing, but no working flash player, can't play anything. Any ideas?
Click to expand...
Click to collapse
Flash player DOES work (kind of). If you long press on the area where the flash "would be." And then press in the upper-left of the area, you can make the flash object full screen, where it WILL work!

which version?
miker2431 said:
Flash player DOES work (kind of). If you long press on the area where the flash "would be." And then press in the upper-left of the area, you can make the flash object full screen, where it WILL work!
Click to expand...
Click to collapse
Are you using the hacked flash.apk?

Nope, just update or fresh download the newest version that shows up in the market and most browser pages with flash videos will play (you can hear them but prob not see them) then you kind of have to "guess" where that "full screen" button is on the video window, and if you hit it spot on, it should launch the flash video full screen. It's a *****, but it works. I'm going back and reloading some of the other HC roms to see which one I can live with for now.

Hey everyone!
Just put this on my gtab, and i have an issue. When i go to install an app, it causes a reboot from the splash screen, and when it comes back up, the wifi doesnt work(gives an error) until i restart the tablet.
Any ideas?
Thanks!
-Steve

mq1991 said:
Hey everyone!
Just put this on my gtab, and i have an issue. When i go to install an app, it causes a reboot from the splash screen, and when it comes back up, the wifi doesnt work(gives an error) until i restart the tablet.
Any ideas?
Thanks!
-Steve
Click to expand...
Click to collapse
Hi Steve,
Can you be a little more specific, i.e. previous ROM, install method, what app, etc...
-JR-

timbck2 said:
This isn't a new problem (I've had it with all the Honeycomb ROMs I've used), but when I hold the power button and choose "Recovery", my G Tablet doesn't boot into recovery, it just reboots normally. I can only get into recovery by holding the volume up button while rebooting. Is this normal? It isn't really a big deal, but I thought I'd report it.
I'm running Flashback 10.3.
Click to expand...
Click to collapse
This is a known issue with the Shutdown.apk (app), unfortunately no resolve at the moment, but will look into it further.
Thanks,
-JR-

Thanks for the quick repsonse!
Alright, well a bit of a rollercoaster here..
I went through and followed this guide to get my tablet up to 4349.
This one
Then, I attempted to install CWM .8 to manage roms and such.
That did not work, it soft bricked the device, so i went and NVFlashed it back, and went through the process of getting it back to 4349.
I then used the included recovery (v3?) to install Flashback.
Any tips on getting CWM to go on along with 4349?
EDIT: So far its happened with every app, it downloads fine. When it switches to "installing..." the tablet goes to the Flashback splashscreen.

mq1991 said:
Thanks for the quick repsonse!
Alright, well a bit of a rollercoaster here..
I went through and followed this guide to get my tablet up to 4349.
This one
Then, I attempted to install CWM .8 to manage roms and such.
That did not work, it soft bricked the device, so i went and NVFlashed it back, and went through the process of getting it back to 4349.
I then used the included recovery (v3?) to install Flashback.
Any tips on getting CWM to go on along with 4349?
Click to expand...
Click to collapse
OK, I think I follow you, your currently running Flashback 10.3, correct?
If so, you can flash/install ClockworkMod 3.0.2.8 rev5 internally.
FB 10.3 includes the recovery binaries for Stock and ClockworkMod, you just need to flash/install via terminal.
Open/Run Terminal Emulator and type the following:
$ su - become Superuser
# cwmrecovery.sh - will flash/install ClockworkMod 3.0.2.8
# fixrecovery.sh - will flash/install Stock recovery
Terminal Emulator: https://market.android.com/details?id=jackpal.androidterm&hl=en

Thanks! I will try that out and post back!
Haha yeah I was, Im just gonna start from the beginning to try and iron out any problems I may have caused.
Also, the kernel in the first post, will that help improve stability? Or is it simply the overclock?
Thanks for your help!

mq1991 said:
Thanks! I will try that out and post back!
Haha yeah I was, Im just gonna start from the beginning to try and iron out any problems I may have caused.
Also, the kernel in the first post, will that help improve stability? Or is it simply the overclock?
Thanks for your help!
Click to expand...
Click to collapse
First of all, make sure you're on 1.2 bootloader; if you've already NVFlashed 4349 then you are.
Second, download and flash/install this ClockworkMod:
http://dev-host.org/g4e68tsmgdlp/gTab.cwm.3028.1.2.zip
If you already got ClockworkMod 3.0.2.8 rev5 then skip the above, if not, and you have Stock recovery, then rename to update.zip and flash.
Third, use the 'Clean' install method in the OP.
Flashback 10.3 already has pershoot's kernel baked in, the 2 kernel pkgs in the OP are to allow trying/testing between the two.
-JR-

Could you point me in the direction of finding that version of NVFlash? Im using one that goes to a very old version of TnT and then i need to wait for an OTA update.
Ive searched on the forum but havent turned up much.
That makes more sense. Thanks for all your help. I dont want to come across as a noob, but for some reason this tablet has been giving me the most trouble of all getting this stuff right. haha
---------- Post added at 09:46 PM ---------- Previous post was at 09:27 PM ----------
*facepalm* All I had to do was reinstall Flashback.
Thanks so much for your help! It no longer restarts when I install apps.
So i think the problem was down to that I didnt use CWM to install it, after I used NVFLASH v5 it installed that new version of CWM you mentioned. I then did a CLEAN install of Flashback and so far so good! I hope this can help someone else out as well.

Looking good JR. Keep up the great work!

Is anyone else missing the \system\ data\ folder where the hacked adobe flash apk
I'm coming from flashback 10.1 upgrade install, wiped cache and dalvik cache
Sent from my Nexus S 4G using xda premium

Flashing Guide [Team 3xtr3m3 | ICS333 ROM]

FLASHING GUIDE​<Team 3xtr3m3 | ICS333 ROM>​NOTE : NOT ALL THESE STEPS ARE A MUST OR NEEDED TO BE DONE IN THIS PARTICULAR WAY, BUT IT IS BEST TO DO SO IN ORDER TO AVOID FURTHER PROBLEMS AND MAKE SURE THE FLASHING PROCESS IS AS CLEAN AS POSSIBLE.​
>EVERYTHING WILL BE WIPED<​
PAY ATTENTION AND TAKE YOUR TIME !
THIS ROM AUTOMATICALLY SAVES YOUR IMEI FOR RESTORING IN CASE YOU LOSE IT!
SOME MAY LOSE THEIR IMEI AFTER FLASHING ICS SO JUST USE THE GUIDE FOR
RESTORING IMEI AT THE BOTTOM OF THE PAGE!
I DO NOT ANSWER TO QUESTIONS WHICH HAVE ALREADY BEEN ANSWERED IN THIS TUTORIAL OR IN THE LINKS THIS TUTORIAL PROVIDES !​
THIS IS WHAT YOU HAVE TO DO STEP BY STEP :​
IT IS ALWAYS BETTER TO FLASH ICS FROM GB TO MAKE THE FLASHING PROCESS AS CLEAN AS POSSIBLE AND TO AVOID POTENTIAL ISSUES!​
1. Download the GB Flash KIT which includes the following (XXJW5 2.3.6 GB ROM, PIT file, CF-Root Kernel for Odin, Odin3-v1.85 and Samsung Driver) : http://d-h.st/4nP
NOTE : It would be best to have your phone fully charged before flashing
2. If you haven`t already installed the driver, install it from the GB Flash KIT.
> Plug your phone into the PC and format internal SD
NOTE : The steps below require the know-how of download mode and clockworkmod recovery (CWM) :
For putting the phone in download mode : Keep pressed volume down + home button + power button until it goes into download mode.
For accesing CWM : Keep pressed volume up + home button + power button until the phone reboots.As soon as you see the "Galaxy S" logo, release the buttons.Now you are in CWM.
3. Enter Download Mode, open Odin, check Re-Partition, press PIT button and browse for the PIT file, press PDA button and browse for the PDA file in the ROM folder, press PHONE button and browse for the PHONE file, press CSC button and browse for the CSC file and finally press START button.Wait till it`s finished and when the phone reboots disconnect from PC.
4. When the phone has booted into the ROM and you see the wizard screen just enter download mode again, plug your phone into the PC, open Odin, press PDA button and browse for the CF-Root kernel, press START button and wait for it to finish.After the phone reboots disconnect it from the PC, let it boot and when you`re in the ROM, set your phone to mass storage mode from settings>wireless & network>usb settings and plug your phone into the PC, copy the ICS333 ROM to your internal SD root location, assuming you have downloaded it from here : http://goo.gl/LuXvH and disconnect from PC.
5. Enter CWM, Wipe Data/Factory Reset, Wipe Cache, Wipe Dalvik Cache and flash the ROM.You will notice the phone will reboot immediately because it will switch kernels, from CF-Root to Semaphore, prior to flashing the actual ROM.As a result, it will boot loop or get stuck on Semaphore logo, so just force it into CWM using the 3 key combo (no need to take the battery out).Now flash the rom again and wait till it`s finished and > Reboot to system!.
IMPORTANT : After reboot, enter CWM, flash GAPPS provided here : http://goo.gl/LuXvH and reboot.That`s it.You`re done!.
NOTE : You may not succeed from the first try with the 3 key combo, it`s a matter of timing when releasing the buttons to enter CWM.Just make sure you release the buttons as soon as you see the Galaxy S logo.You will get passed the bootloop/Semaphore logo and enter CWM eventually!
If you still didn`t succeed, turn off phone and turn it on by using the 3 key combo to go directly into CWM.
IMPORTANT : You may encounter a Phone Encryption problem at first boot, so all you need to do is > enter CWM > flash the rom again > Reboot!
As a last resort, if every method above failed, try this :
1. Flash GB ROM
2. Flash CF-Root Kernel
3. Wipe Data/Factory Reset, Wipe Cache, Wipe Dalvik Cache
4. Flash this script : http://d-h.st/P2M
5. Flash Devil Kernel [choose any CFS_BLN_CMC version] : http://devil.haxer.org
6. Flash ICS333 ROM, don`t reboot yet
7. Flash the script again : http://d-h.st/P2M
8. Flash Devil Kernel again : http://devil.haxer.org
9. Flash GAPPS provided here : http://goo.gl/LuXvH
10. Reboot twice
>> Done!
If you are not satisfied with your modem`s performance or you end up with "Baseband Unknown", try a different one from here : http://goo.gl/R9q5l
Depending on the region you are in, modems can make a huge difference!
But usually 3G/Internet usage will discharge battery faster than Wi-Fi usage.
THERE IS NO "BEST MODEM" > you have to experiment yourselves with these modems!
You may experience soft reboots or slow downs/hangs if you mess with voltages, specific governor-scheduler combos or if you overclock.
If you are not satisfied with the stock launcher, in terms of speed and stability, I highly recommend using Nova Launcher instead, it performs better than Apex Launcher, as I`ve tested myself, it has great features and customizations and it compliments the rom, plus it looks like stock, preserving the ICS look : http://goo.gl/y479F
NOTE : For fully working H/W Decoding on video playing please use DicePlayer : http://goo.gl/4BHth
IMPORTANT : If you encounter "Low on Storage" issue just flash this via CWM and reboot! : http://d-h.st/94L
IMPORTANT : If you have problems with media storage (file detection/duplicates issues) this is what you have to do :
Go to System Settings > Apps > ALL tab > scroll down for Media Storage > Clear Data, Force Stop!
Reboot phone and give it some more time to scan for everything (especially if you have lots of multimedia files)!
Everything should be OK now.
Also, when an app FC`s, go to > Manage apps > find the app > Clear Data > Reboot!
IMPORTANT [Titanium Backup] : Before you make a backup do this : Open Titanium Backup > Tap Menu Button > Preferences > Scroll down to "Troubleshooting settings" > check "Follow all symbolic links".Done.
IMPORTANT [GPS] : Make sure you install FasterFix : http://goo.gl/660r6 > open it > choose a region/server according to your location > press GO.Now your GPS will work properly and get a lock faster.
> Tested iGO and it works just fine
NOTE [VIBER] : In order for Viber to fully work, use Root Explorer or Ghost Commander, go to > /system/build.prop > edit build.prop file > find the line "ro.product.model=GT-I9000" and replace "GT-I9000" with "Nexus S".Save and exit.Reboot!
HOW TO RESTORE IMEI [EFS Folder], IF NEEDED, USING Nitrality (free app) > http://goo.gl/9hxOB :​
1. Install "Nitrality" from Google Play Store, open it, grant root acces.
2. Go to "Tools" > Restore /efs > Reboot!
3. Done!
NOTE : If for some reason Nitrality doesn`t do the job, restore your IMEI using the guides below.
HOW TO RESTORE IMEI [EFS Folder], IF NEEDED, USING Root Explorer (paid app) > http://goo.gl/xBqok :​
First check if you`ve lost your IMEI : open Dialer, input *#06# and if the IMEI number starts with "049" then it means you lost your IMEI and you have to restore it.​​
1. After you flashed the ICS333 Rom, install Root Explorer.
2. Go to "/sdcard/backup", open "efs" folder, press "Menu" button > Multi-Select > Select All > Copy.
3. Go back to root "/", open "efs" folder and paste the contents here, when asked, check to replace all files.
4. Reboot
5. Done!
NOTE : It is important not to copy the EFS folder itself , when you want to restore IMEI, but the contents within the EFS folder, which will replace the contents of the EFS folder from the root "/EFS".
HOW TO RESTORE IMEI [EFS Folder], IF NEEDED, USING Ghost Commander File Manager (free app) > http://goo.gl/J0TF9 :​
1. After you flashed the ICS333 Rom, install Ghost Commander File Manager.Open Ghost Commander File Manager > Menu button > Application > Settings > Scroll down to "Advanced" > Check "Show root and mounts", check "Automatic root mode" > Go back and hold the phone in landscape mode.Now you will have two panels (left panel next to the front camera and right panel next to the home button).
2. On the left panel, tap on "root mode", open "/efs" folder
3. On the right panel, tap on "root mode", go to "/mnt/sdcard/backup" (open folders by double tap), open "/efs" folder, select all files within the efs folder, one by one (one tap to select a file), tap on "5 copy", a windows will open saying "Copy # items to : root:/efs", which is the location you are in the left panel, tap on "OK" and all the files will be automatically overwritten.
4. Reboot
5. Done!
HOW TO EXPORT A LOG FILE​ (LOGCAT) FOR DEBUGGING via Android Terminal Emulator : http://goo.gl/oLRC0​<by providing the logcat to the devs, you can REALLY help the debugging process when something goes wrong with the rom>​
[Semaphore Kernel Users] :
1. Open Semaphore app > Kernel Features > check "Logger" > Reboot!
2. Install Android Terminal Emulator : http://goo.gl/oLRC0
3. Let the phone run for 3/4 hours > open Android Terminal Emulator > type "su" (without quotes), tap on return (enter) key, grant root if asked, now type "logcat>/sdcard/logcat.txt" (without quotes), tap on return (enter) key.
4. Now you have created a text file with the logcat.Done!
[USERS WITH ANOTHER KERNEL] :
1. If the kernel you are using, comes with an app (like the Semaphore app), search for an option which allows you to enable the logger.If you don`t have any app, most probably you have to enable the logger via CWM, just acces CWM and search where you can enable the logger and reboot.
2. Let the phone run for 3/4 hours > install and open Android Terminal Emulator > type "su" (without quotes), tap on return (enter) key, grant root if asked, now type "logcat>/sdcard/logcat.txt" (without quotes), tap on return (enter) key.
3. Now you have created a text file with the logcat.Done!
If you followed every step in this tutorial it is highly unlikely to fail this, only if you can`t read English properly.
If you have questions/problems or you just want to chat about it, go here : http://webchat.freenode.net
Channel : ##ICS333
If you found this guide helpful just press “Thanks” . Keep the thread clean and use the IRC channel!
Good Luck!
Enjoy this wonderful ROM !

Hi mate I tried flashing using your guide but I am still stuck.
My phone keeps trying to boot after I wipe for the second time (after the bootloop from changing kernels, I already sorted that out)
After flashing the rom (properly after the bootloop due to kernel change) I wipe data/cache/dalvik. That happens fine but when I boot I get the gt-i9000 startup splash then the semaphore splash stays on for a while then the phone resets. It then loops the same thing.
I took the battery out and tried to enter recovery mode but the same happens again. Turning the phone on normally result n the same thing happening.
I haven't overclocked or anything like that.
However altering your method I have it working (I did however have the same problem as I mentioned above (the bootloop between the starting screen and the kernel screen) but that came after using the rom for a few hours leaving it in my pocket.
I got it working by:
1. download the files
2. formatted internal sd
3. flashed JW5 and let it load
4. flashed cf-root
5. put ICS333, kernel cleanup script, devil kernel that you suggested and GAPPS zip files on internal sd
6. turn phone off and then boot into recovery
7. wiped data/cache/dalvik
8. run the kernel cleanup zip
9. flash ICS333 and wait for bootloop
10. get into recovery
11. flash ICS333 zip again
12. when done flash GAPPS
13. when done reboot into recovery.
14. run kernel cleanup zip for second time
15. Install devil kernel
16. reboot system
Job done.
It is currently 00:22 in the UK so I'm going to bed. I'll leave my phone running through the night and I will see if I have the same issue as before.

yep.it seems semaphore 1.1.1 version is really causing problems for some people. thanks for your feedback so people with similar issues like yours can try flashing the rom like you did as an alternative.

I faced problem with 3 keys combo recovery mod, they are not working while downloading keys working, and recovery working from CWM manager,phone stucked in boot loop after installed new ICS333 Rom. do you have idea if I can install kernel first then not go into boot loop, thanks.

gazza1988 said:
Hi mate I tried flashing using your guide but I am still stuck.
My phone keeps trying to boot after I wipe for the second time (after the bootloop from changing kernels, I already sorted that out)
After flashing the rom (properly after the bootloop due to kernel change) I wipe data/cache/dalvik. That happens fine but when I boot I get the gt-i9000 startup splash then the semaphore splash stays on for a while then the phone resets. It then loops the same thing.
I took the battery out and tried to enter recovery mode but the same happens again. Turning the phone on normally result n the same thing happening.
I haven't overclocked or anything like that.
However altering your method I have it working (I did however have the same problem as I mentioned above (the bootloop between the starting screen and the kernel screen) but that came after using the rom for a few hours leaving it in my pocket.
I got it working by:
1. download the files
2. formatted internal sd
3. flashed JW5 and let it load
4. flashed cf-root
5. put ICS333, kernel cleanup script, devil kernel that you suggested and GAPPS zip files on internal sd
6. turn phone off and then boot into recovery
7. wiped data/cache/dalvik
8. run the kernel cleanup zip
9. flash ICS333 and wait for bootloop
10. get into recovery
11. flash ICS333 zip again
12. when done flash GAPPS
13. when done reboot into recovery.
14. run kernel cleanup zip for second time
15. Install devil kernel
16. reboot system
Job done.
It is currently 00:22 in the UK so I'm going to bed. I'll leave my phone running through the night and I will see if I have the same issue as before.
Click to expand...
Click to collapse
I have the same problem, the device's bootloop & bootloop, someone help us please

chientn said:
I have the same problem, the device's bootloop & bootloop, someone help us please
Click to expand...
Click to collapse
NOTE : You may not succeed from the first try with the 3 key combo, it`s a matter of timing when releasing the buttons to enter CWM.Just make sure you release the buttons as soon as you see the Galaxy S logo.You will get passed the bootloop and enter CWM eventually!
If you still didn`t succeed, turn off phone and turn it on by using the 3 key combo to go directly into CWM.

perfect guide

Consider using Midnight-Kernel for next release. No reboots and zero FC's here.
Gesendet von meinem GT-I9000 mit Tapatalk 2

salzheld said:
Consider using Midnight-Kernel for next release. No reboots and zero FC's here.
Gesendet von meinem GT-I9000 mit Tapatalk 2
Click to expand...
Click to collapse
problems solved by reverting to semaphore 1.0.0s version.

sorry, wrong thread ;-)

psyqiq said:
NOTE : You may not succeed from the first try with the 3 key combo, it`s a matter of timing when releasing the buttons to enter CWM.Just make sure you release the buttons as soon as you see the Galaxy S logo.You will get passed the bootloop and enter CWM eventually!
If you still didn`t succeed, turn off phone and turn it on by using the 3 key combo to go directly into CWM.
Click to expand...
Click to collapse
thank you but i cannot pass the booloop, after i enter CWM and re-install the ICS rom i get bootloop again, after that, i cannot access the CWM again....

chientn said:
thank you but i cannot pass the booloop, after i enter CWM and re-install the ICS rom i get bootloop again, after that, i cannot access the CWM again....
Click to expand...
Click to collapse
flashing guide updated.

psyqiq said:
flashing guide updated.
Click to expand...
Click to collapse
Thank you for the guide

Data Network not working
Hi i installed this ROM today and it really seems flawless. I really love that it's on the SGS.
My problem is that i have never had a problem getting my data network to work when i have installed e new ROM. I have deleted and rebooted and reinstalled the APN in the mobile network settings but it's still not working.
Could someone tell me what the problem is?

elvismercado said:
Hi i installed this ROM today and it really seems flawless. I really love that it's on the SGS.
My problem is that i have never had a problem getting my data network to work when i have installed e new ROM. I have deleted and rebooted and reinstalled the APN in the mobile network settings but it's still not working.
Could someone tell me what the problem is?
Click to expand...
Click to collapse
do you have "Data enabled" checked in Mobile networks menu?

Should EFS be an EMPTY folder?
I noticed the EFS folder on this phone is empty, is that as it should be?

LazPL said:
I noticed the EFS folder on this phone is empty, is that as it should be?
Click to expand...
Click to collapse
you have lost your IMEI. EFS Folder should contain some files where IMEI is stored.
Use the guide to restore your IMEI.
Cheers ~

I just installed this rom and till now 0 problems, everything it's OK
Kernel: Semaphore ICS 1.2.0s
Modem: JVU
Just as it was, without any change....now let see how it's the battery life.

Thanks for the guide worked 100%

psyqiq said:
HOW TO BACKUP IMEI [EFS Folder] using Root Explorer :
1. After you flashed the GB Rom and obtained root, install Root Explorer.
2. Enter Root Explorer, go to root "/", long press "efs" folder and copy it to "external_sd".
4. After you flashed the ICS Rom, install Root Explorer.
5. Go to root "/", search for "/emmc", open "efs" folder you saved, press "Menu" button > Multi-Select > Select All > Copy.
6. Go back to root "/", open "efs" folder and paste the contents here, when asked, check to overwrite for all files.
7. Reboot
8. Done!
Click to expand...
Click to collapse
Is it really essential to to change anything in EFS folder unless any one face any problem related to IMEI no.
Till backup of EFS is fine but restoring EFS folder for no reason is not good thing
As i know efs folder contain very dedicated data.
If i am wrong just correct me..

[GUIDE/TUTORIAL/HOWTO] Samsung Galaxy S5 mini G800F Any version to Android 9 Pie

[GUIDE/TUTORIAL/HOWTO] Samsung Galaxy S5 mini G800F to Android 9 Pie
[GUIDE/TUTORIAL/HOWTO] Samsung Galaxy S5 mini G800F/kminilte (Exynos) Any version to Android 9 Pie
This detailed step-by-step guide helps you transform your Samsung Galaxy S5 mini G800F to a powerful one with Android 9.
Verify your phone is G800F before going further : in Android, go to Settings > About > Check model is G800F.
If not, quit this tutorial.
CHANGELOG
v10. TWRP 3.6, check links
v9. Latest TWRP + Magisk 23 + ROM
v8. TWRP 3.5, Magisk 22
v7. Updated pack for TWRP recovery 3.4.0-0 + ROM download link + Samsung USB drivers, Magisk for root, MagiskManager-v8.0.2
v6. Updated pack for TWRP recovery 3.3.1-0 + IMEI backup
v5. Updated tutorial and pack to Android 9 Pie
v4. Updated pack with Odin 3.13.1, TWRP Recovery 3.2.3-0 and Spookcity kernel 6.0-1
v3. Added Google Play certification, TWRP recovery 3.2.1-0
v2.1. Updated Spookcity kernel to v6
v2. Updated to Android 7.1 Nougat, TWRP3.1.1-1, Spookcity kernel 5, overclock, fixed bootloops
v1. Initial release for Android 6
1) DOWNLOAD
- djibe Galaxy S5 mini G800F pack v3: http://bit.ly/G800Fdjibepackv3
(contains Samsung tweaked Odin 3.13.1 + Samsung USB drivers + TWRP 3.6.0_9-0 official recovery + Magisk 23). Unzip files.
+ ROM Unofficial Lineage OS 16: https://forum.xda-developers.com/galaxy-s5-mini/development/rom-lineageos-16-0-t3868612
Download latest build here: https://androidfilehost.com/?w=files&flid=64356&sort_by=date&sort_dir=DESC
### ROM perfectly working except Encryption, Video recording doesn't work in all apps or with all camera applications
+ OpenGApps ARM 9 pico : http://opengapps.org/?arch=arm&api=9&variant=pico
+ a microSD card. Copy ROM, Gapps and Magisk 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 an app like Backupyourmobile to backup texts, contacts, etc.
Check that backup is located on microSD card.
Then copy the backup on your PC.
Erase your Google Account: Go to Settings > Account > Google and erase it.
3) FLASH TWRP 3.6 RECOVERY
Shut down phone.
Boot in Download Mode : hold Home + Power + Volume- for 3 seconds and release.
Confirm with Volume+.
Phone now displays: Downloading, do not turn off target.
Connect phone in USB, wait for 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 AP > select twrp-3.6.0_9-0-kminilte.img.tar
### Warranty will be Void after next click ###
Click Start.
When PASS! success green message appears.
Wait a few seconds, then hold again Home + Power + Volume- to reboot phone.
Let phone restart then shut it down.
4) BACKUP IMEI PARTITION
Boot in Recovery Mode: Hold Home + Power + Volume+ until you see the Samsung logo then release and wait a few seconds for TWRP recovery to boot.
If it asks for Keep System Read Only ? > Swipe to Allow Modifications.
Go to Backup > you can select the partitions you want to save.
Select all partitions in order to be able to restore phone to it's original state.
Select at least EFS partition to backup your IMEI. If a flash fails and partition is damaged you will still be able to restore this partition and use the phone.
If IMEI is lost during a flash, phone won't be able to reach cellphone networks.
I prefer to backup EFS, Boot and System.
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.
Connect phone or microSD to PC.
Open microSD folder and backup TWRP folder to a safe place.
Youe /efs partition is now safe (+/- other partitions if you need to fix some crashes).
5) WIPE PARTITIONS
Go to Wipe > Format Data
Type yes and confirm with bottom right Check icon.
Then go to Wipe > Advanced wipe,
select Dalvik, Cache, System, Data, Internal Storage (if you really made a backup from step 2), then Swipe to Wipe,
then back.
Go back to TWRP Home screen > Reboot > Recovery and Swipe to confirm.
At reboot, if TWRP asks for Keep System Read Only ? > Swipe to Allow Modifications.
6) FLASH ROM, GAPPS AND MAGISK
Back to TWRP Home menu. Then tap on Install > choose LOS16*.zip,
(if you don't see the files, tap on Select Storage and make sure Micro SDCard is active).
then Add more Zips > open_gapps*.zip,
then Swipe to confirm Flash.
Wait for operation to end.
### OPTIONAL FOR ROOT
Go to Reboot > Recovery.
Once phone rebooted, go to Install > Magisk.
Then tap Wipe cache/dalvik, swipe to confirm,
then Reboot System.
Wait for the phone to boot during 10 minutes.
7) ROOT ACCESS
No extra steps for root. Magisk starts with Android.
Open Magisk Manager app to manage root permissions.
8) DON'T USE BUILT-IN CAMERA APP
Using LineageOS default camera app will crash when switching from photos to videos.
Use Simple Camera app included (or Google Camera, Footej camera).
9) EXTRA
You can use GPS Status & Toolbox app for faster GPS fix.
For faster phone, go to Settings > About.
Tap 7 times on Build number.
Go to Settings > System > Avdanced > Developer options.
Set Windows animation scale, Transition animation scale and Animator duration scale to 0.5x.
For better battery longevity, set Dark mode. Settings > Display > Avanced > Style > Style > Dark
And Dark mode > Dark.
Enjoy,
djibe
Thanks : @panzerknacker, LOS Team, TWRP Team, @spookcity138, @hennymcc, @rodman01, @Friedensfurz, @cschsz, @ayke, @CTXz, @psyafter

Update: Thanks to C0rn3j in the TWRP thread I got it to work with heimdall and pulling the battery.
Great guide, worked well for me except rebooting to TWRP recovery failed with the kernel length error. Tried using the previous version of TWRP and then with the stock kernel but both failed with the same error. Does TWRP work with LOS14.1 on kminilte?

Nice guide! I have been using custom roms on my mini for about a year and never knew mutch about that I can change the filesystem.
However sometimes my phone becomes very laggy, and unresponsive.(Maybe memory settings problems) I tried several kernel settings but did not find the best yet.
What is Your opinion? What are the best kernel settings to our model?

Evos11 said:
Nice guide! I have been using custom roms on my mini for about a year and never knew mutch about that I can change the filesystem.
However sometimes my phone becomes very laggy, and unresponsive.(Maybe memory settings problems) I tried several kernel settings but did not find the best yet.
What is Your opinion? What are the best kernel settings to our model?
Click to expand...
Click to collapse
Hi, try not to overclock too much, like 1600 Mhz, cause overheating can slow down phone.
What other parameters did you try ?

rimc100 said:
Update: Thanks to C0rn3j in the TWRP thread I got it to work with heimdall and pulling the battery.
Great guide, worked well for me except rebooting to TWRP recovery failed with the kernel length error. Tried using the previous version of TWRP and then with the stock kernel but both failed with the same error. Does TWRP work with LOS14.1 on kminilte?
Click to expand...
Click to collapse
Hi. Yes LOS 14.1 and TWRP 3.1 both work very well on my dad's G800F.
You can't boot in TWRP ?
What kernel do you use ?

djibe89 said:
Hi. Yes LOS 14.1 and TWRP 3.1 both work very well on my dad's G800F.
You can't boot in TWRP ?
What kernel do you use ?
Click to expand...
Click to collapse
I got it working now. All is well.

rimc100 said:
I got it working now. All is well.
Click to expand...
Click to collapse
Glad to hear it.
Enjoy

Latest version of tutorial is available to obtain GOOGLE MOBILE SERVICES (GMS) CERTIFICATION
+ updated TWRP recovery
+ updated Kernel

Do you think LOS is stable enough to propose it in my tutorial ?

Thank you for the guide! It worked really well. There were a number of details I didn't know, like the performance difference between filesystem formats, and everything was very step-by-step and super helpful.
One issue: TWRP 3.2.1 doesn't work with the 6.0 Spookcity kernel. You have to disable the device check to get it to work. Looks like Panzerknakker uploaded one with that change: https://forum.xda-developers.com/showpost.php?p=77725358&postcount=285
djibe89 said:
Do you think LOS is stable enough to propose it in my tutorial ?
Click to expand...
Click to collapse
Are you talking about LOS 15? If so, no IMO. It was stable but buggy. I'm actually downgrading back from 15.1 to 14 due to issues with internal storage and battery consumption, and sometimes it would stop charging and require a hard restart..

Frostcrystal said:
Thank you for the guide! It worked really well. There were a number of details I didn't know, like the performance difference between filesystem formats, and everything was very step-by-step and super helpful.
One issue: TWRP 3.2.1 doesn't work with the 6.0 Spookcity kernel. You have to disable the device check to get it to work. Looks like Panzerknakker uploaded one with that change: https://forum.xda-developers.com/showpost.php?p=77725358&postcount=285
Are you talking about LOS 15? If so, no IMO. It was stable but buggy. I'm actually downgrading back from 15.1 to 14 due to issues with internal storage and battery consumption, and sometimes it would stop charging and require a hard restart..
Click to expand...
Click to collapse
Hi, thank you very much for your help.
I'll fix the Kernel thing and stick to LOS 14.
Thanks,
djibe

v4. Updated pack with TWRP Recovery 3.2.3-0 and Spookcity kernel 6.0-1

Update: I'm having some major issues with lag on my device. 15 seconds to open Chrome, occasional overheating, high CPU usage on small things, etc.
I've had LOS14.1 (a slightly older version) on this device before, minus the different filesystem format and the Spookcity kernel, and not experienced this issue. So I'm thinking about rolling back some of the changes to see which ones were the cause.
Is there an unmodified version of the kernel out there?

Frostcrystal said:
Update: I'm having some major issues with lag on my device. 15 seconds to open Chrome, occasional overheating, high CPU usage on small things, etc.
I've had LOS14.1 (a slightly older version) on this device before, minus the different filesystem format and the Spookcity kernel, and not experienced this issue. So I'm thinking about rolling back some of the changes to see which ones were the cause.
Is there an unmodified version of the kernel out there?
Click to expand...
Click to collapse
Hi,
I didn't experience that but we never know.
To have a fresh system, reboot to TWRP recovery. Wipe cache + system.
Flash LOS, addonsu, OpenGApps.
Wipe cache and reboot.

Thank you for posting this guide. Much appreciated.
Was thinking of getting a Galaxy S i9000 ready for moms but didn't quite understand all the dated guides/roms so decided to buy a 2nd hand s5 mini which now works like a charm!
(struggled a bit with the power off/power on after twrp flash but removing battery for shutdown and holding home+power+vol+ a little longer works!)

rewre said:
Thank you for posting this guide. Much appreciated.
Was thinking of getting a Galaxy S i9000 ready for moms but didn't quite understand all the dated guides/roms so decided to buy a 2nd hand s5 mini which now works like a charm!
(struggled a bit with the power off/power on after twrp flash but removing battery for shutdown and holding home+power+vol+ a little longer works!)
Click to expand...
Click to collapse
Hi, you are very welcome for this tuto.
I like when phones don't go to the rubbish !
You are quite right, Galaxy S2 i9100 can be tricky when USB is badly recognized by the PC. And to be honest its performances are low.
Hope you had a merry christmas,
cheers

Hi, i have this device now. ¿Which rom its the most stable and smooth?

Zsheoran said:
Hi, i have this device now. ¿Which rom its the most stable and smooth?
Click to expand...
Click to collapse
Hi,
use the LineageOS build from the 1st post of this thread.
My mother is very happy with it !
Enjoy

Tutorial is up to date

djibe89 said:
Tutorial is up to date
Click to expand...
Click to collapse
Hi,
I have followed the steps and it works pretty well.
However i have some issues:
1. Mobile network is not detecting unless i switch on then off Airplane mode
2. The STK is not working when you use online banking and other isp services.

[FIXED] How to remove data encryption in TWRP

Users of TWRP 3.1 on Doogee Mix (including myself) faced the mammoth problem of an encrypted storage after unlocking the bootloader and flashing the custom recovery. This problem is not peculiar to the Doogee Mix, any other device with TWRP 3.1+ will likely face the same issue and the solution preferred here would work.
By default, your device storage is encrypted (Settings > Security > Encryption) and any TWRP from 3.1+ respects that protocol.
This means that the internal storage would be showing 0mb because it can't be mounted, (no) thanks to the encryption.
Previous versions of TWRP (eg 3.0.3) could easily decrypt the device using the default password but from version 3.1, things changed.
SOLUTION
Needed:
1. An unlocked bootloader
2. TWRP installed (download from the TWRP thread)
3. An SD CARD (or USB OTG)
4. Magisk.zip (latest version, copy it to the SD card)
NOTE: Copy/Backup your files from your internal storage into your PC as this process would wipe everything from the internal storage.
STEPS
> With the bootloader unlocked and TWRP flashed, boot into recovery.
> The screen might be dark when in recovery, just press the power button and the the vol- button, it'll turn ON. Then swipe to unlock.
> You can change the language to English by clicking on the 2nd rectangle by the right above the swipe function.
> Tick "do not show again" and the swipe to allow modification.
> Confirm device encryption by clicking "Backup" or "Install", if the storage size is 0mb or no folder is showing while trying to install, then the device is encrypted.
> Go back, click "Wipe"
> You can choose to Factory reset, Format data or Advanced wipe > tick /data. Either way, it's going to wipe EVERYTHING in the internal storage (that's the purpose of device encryption, to prevent unauthorized access to the storage). However, I recommend you choose "FORMAT DATA"
> If you chose "Format data", then type yes in the next screen and swipe to format.
> When completed, go home, click Reboot and choose Recovery to boot into recovery (very important, do not reboot the phone into system otherwise you'll start all over. Reboot into recovery, not system).
> When in the recovery, click install > select storage > SD card (or USB OTG) (note that the internal storage will display as normal but remember it is now empty following the data reset)
> Navigate to the Magisk in /Sdcard (or USB OTG) and install.
> When completed, you can now reboot safely into system.
> Complete the phone setup and Open Magisk Manager. Notice that Magisk is now installed and "Preserve force encryption" is now unticked". You can also go to Settings > Security > Encryption and notice that it will ask you to encrypt your device, meaning it is decrypted now.
> The next time you will boot into recovery, TWRP may still be in Russian language, just change it one more time and you are good to go.
> Now you can flash anything you want including Xposed (download latest version from the official Xposed thread/website).
That's all. Cheers! Happy tweaking

If you try to install font, module, busybox or any other system framework/tweak without success, then change the installation mode to recovery.
Recommended:
iFont
Busybox for Android or the busybox from Magisk Repo
iFont: switch to "My" tab > Settings > Installation mode > Recovery
Busybox for Android: tap settings (top right) > Installation mode > Recovery

I love you broo!!
I was like 5 hours with this encryption problem without being able to solve it, Thank you very much. I LOVE YOU! Hahaha :good::victory::victory::fingers-crossed:

Cheers!

dwapking said:
If you try to install font, module, busybox or any other system framework/tweak without success, then change the installation mode to recovery.
Recommended:
iFont
Busybox for Android or the busybox from Magisk Repo
iFont: switch to "My" tab > Settings > Installation mode > Recovery
Busybox for Android: tap settings (top right) > Installation mode > Recovery
Click to expand...
Click to collapse
How to you get OTA update when you are rooted? I can't

dwapking said:
If you try to install font, module, busybox or any other system framework/tweak without success, then change the installation mode to recovery.
Recommended:
iFont
Busybox for Android or the busybox from Magisk Repo
iFont: switch to "My" tab > Settings > Installation mode > Recovery
Busybox for Android: tap settings (top right) > Installation mode > Recovery
Click to expand...
Click to collapse
Your screenshot of the about phone page, shows you are on kernel 3.18, thought device had kernel 4.4?

Ersid Kapaj said:
How to you get OTA update when you are rooted? I can't
Click to expand...
Click to collapse
Being rooted shouldn't prevent you from getting the OTA.
OTA's arrive based on System language, region, model/variant, etc.
If you still can't get the OTA and your language is set to "English (US or UK)", then download the latest flashable ROM and flash via PC. It should help for subsequent OTA's.
If you have done this before and still stuck, then just download the local update file and install.

dwapking said:
Being rooted shouldn't prevent you from getting the OTA.
OTA's arrive based on System language, region, model/variant, etc.
If you still can't get the OTA and your language is set to "English (US or UK)", then download the latest flashable ROM and flash via PC. It should help for subsequent OTA's.
If you have done this before and still stuck, then just download the local update file and install.
Click to expand...
Click to collapse
That's the problem. When i click check for update it says "Root detected" and then it says that my system is up to date. I don't want to delete anything from my phone, that's why i don't do it via PC.

have another problem witch F2SF I cant flash any modules in magisk
Magisk.img mount failed do you have this problem?

Ersid Kapaj said:
That's the problem. When i click check for update it says "Root detected" and then it says that my system is up to date. I don't want to delete anything from my phone, that's why i don't do it via PC.
Click to expand...
Click to collapse
I have root, and I don't get any such errors when I check for updates. Perhaps you should just backup ur apps/OS (with TB & TWRP) and files in a PC then flash a clean updated ROM.

mrmazak said:
Your screenshot of the about phone page, shows you are on kernel 3.18, thought device had kernel 4.4?
Click to expand...
Click to collapse
The kernel version is correct. The 4.4 is only shown in CPU_Z app

TheSpartanM4 said:
have another problem witch F2SF I cant flash any modules in magisk
Magisk.img mount failed do you have this problem?
Click to expand...
Click to collapse
Yes... Some modules (Viper4Android, Busybox NDK) did flash successfully (though not mounted in Magisk modules section but are working just fine) while many others refused to install.
I am currently trying to verify the cause. For now, no solution yet.

dwapking said:
I have root, and I don't get any such errors when I check for updates. Perhaps you should just backup ur apps/OS (with TB & TWRP) and files in a PC then flash a clean updated ROM.
Click to expand...
Click to collapse
I have downloaded the update once but when i try to install it says the it's rooted and can't install. Since then it's the same problem.

Yes of course, before any update is installed, root integrity check is performed. Once any modifications has been detected, it will abort.
That's why I said you should flash back your STOCK SYSTEM, RECOVERY AND BOOT, since they're the partitions affected by the root.
Don't forget to wipe the data of "Wireless Update" before proceeding to install.

ok, i'm gonna give this a try once i'm properly awake. i had been trying to install magisk via adb push and it would not work, so we'll see how this does. thanks!

Does safetynet pass for anyone? MobileIron still detects the phone as rooted with Magisk installed...

I got it to work! I have TWRP installed, I have Magisk working, and Safetynet check passes. I can't post screenshots because I don't have enough posts, but I suppose I have root now! ...it's not nearly as exciting on a non-bloated phone with no available roms. But I think we're maybe ready to say we officially have root? I can't learn coding or I'd try to make my own rom.

Cheers!

Doogee Mix only reboots to Doogee Splash which warns: Orange State
Your device has been unlocked and can't be trusted. YOur device will boot in 5 seconds. Then TWRP boots in English instead of Russian. Thats all I get. Is there a custom ROM for Doogee Mix? Did I wiped the OS? Thank you for getting me out off the Encryption - loop.

Can someone please help me understand why I can only boot into TWRP Recovery now???

Need pixelexperience rom installation guide

Hey I want to try pixel experience rom in my nexus 6p but the installation guide there is too complex can someone from the forums break it down and explain so I can install it and also my device is a 8core model so I am not sure weather or not I need a BLOD patch and why I need a custom recovery (other then the normal custom recovery) Thanks in advance

1.No need to flashing blod
2.remove any passwords or screen lock before flashing
3.boot into fastboot make sure bootloader is unlocked
4.flash the twrp recovery provided in the forum u can't use the usual one
5.after installing recovery wipe everything from the advance wipe except internal storage
6.locate and install the rom don't flash the gapps its already included
7.before booting in the system make sure to wipe ur data from wipe or ur phone will not boot
8.time to enjoy!!!

varunvrk said:
Hey I want to try pixel experience rom in my nexus 6p but the installation guide there is too complex can someone from the forums break it down and explain so I can install it and also my device is a 8core model so I am not sure weather or not I need a BLOD patch and why I need a custom recovery (other then the normal custom recovery) Thanks in advance
Click to expand...
Click to collapse
It is quite simple. You'll just need to do a bit if reading about adb and fastboot and make sure you follow these steps methodically. You do not need BLOD patch. You need the custom recovery version from the pixelexperience thread because of the way files are encrypted.
1 . Go to settings - system - about phone. Tap on build number 7 times until you see a pop up saying developer options enabled.
2. Go to settings - system - advanced - developer options. In there you want to enable oem unlocking and usb debugging.
3. Go to settings - security. Remove all device security so it's just swipe to unlock.
4. Follow this guide to setup google drivers, adb, fastboot and unlock the bootlader https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
5. Download latest rom version and twrp recovery version from pixelexperience thread to your pc and follow instruction in above guide for flashing twrp via fastboot.
6. Boot into your custom recovery (hold power + volume down while phone is off, use volume keys to select recovery, power for enter) ignore warning screen.
7. Go to backup. Select system, data and boot. Name it something like stock_todaysdate. Swipe to create backup. Reboot system.
8. Connect phone to pc. Through pc find twrp folder in phone, find your backup, copy to pc for safe keeping (this can restore your phone to how it was if anything goes wrong). Copy the rom zip you downloaded to your phone's internal storage.
9. Boot back into recovery. Go to wipe. Wipe everything except internal storage. Go to install. Locate the rom zip file and install it. Go to wipe again. Select format data and confirm.
10. Reboot system and wait for rom to boot this can take a while. Once booted leave your phone alone for a few minutes then you are good to go. If all is well make another backup and store on pc.

Champdroid said:
It is quite simple. You'll just need to do a bit if reading about adb and fastboot and make sure you follow these steps methodically. You do not need BLOD patch. You need the custom recovery version from the pixelexperience thread because of the way files are encrypted.
1 . Go to settings - system - about phone. Tap on build number 7 times until you see a pop up saying developer options enabled.
2. Go to settings - system - advanced - developer options. In there you want to enable oem unlocking and usb debugging.
3. Go to settings - security. Remove all device security so it's just swipe to unlock.
4. Follow this guide to setup google drivers, adb, fastboot and unlock the bootlader https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
5. Download latest rom version and twrp recovery version from pixelexperience thread to your pc and follow instruction in above guide for flashing twrp via fastboot.
6. Boot into your custom recovery (hold power + volume down while phone is off, use volume keys to select recovery, power for enter) ignore warning screen.
7. Go to backup. Select system, data and boot. Name it something like stock_todaysdate. Swipe to create backup. Reboot system.
8. Connect phone to pc. Through pc find twrp folder in phone, find your backup, copy to pc for safe keeping (this can restore your phone to how it was if anything goes wrong). Copy the rom zip you downloaded to your phone's internal storage.
9. Boot back into recovery. Go to wipe. Wipe everything except internal storage. Go to install. Locate the rom zip file and install it. Go to wipe again. Select format data and confirm.
10. Reboot system and wait for rom to boot this can take a while. Once booted leave your phone alone for a few minutes then you are good to go. If all is well make another backup and store on pc.
Click to expand...
Click to collapse
That is the best instructions I have seen in a while. I kinda figured that that was how to do it but I am not confident in my abilities. This confirms what I thought needed to be done.
I am not new to flashing I have been doing it since the LG g2x. But I did take a 3 year break from flashing and now everything is a little different.
Anyway thank you for this

mojorisin7178 said:
That is the best instructions I have seen in a while. I kinda figured that that was how to do it but I am not confident in my abilities. This confirms what I thought needed to be done.
I am not new to flashing I have been doing it since the LG g2x. But I did take a 3 year break from flashing and now everything is a little different.
Anyway thank you for this
Click to expand...
Click to collapse
Pleasure mate glad you appreciate it.
I also took a long break. Started back in the HTC sensation days! It's amazing how much everything changes when you don't check in for a while. Magisk for example blows my mind.

Champdroid said:
Pleasure mate glad you appreciate it.
I also took a long break. Started back in the HTC sensation days! It's amazing how much everything changes when you don't check in for a while. Magisk for example blows my mind.
Click to expand...
Click to collapse
Yeah magisk is crazy the devs here at xda can do anything. They really are the best of the best. Everything I know I learned here on xda. I just read they are working on a new way to root at the kernel level so it's built in right from the when it's compiled. That's just crazy smart.