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

[HOW TO] Install CM9/CM10 on GB 2.3.6 LATAM (R01 and R02 firmwares)

DISCLAIMER!!!
THIS TUTORIAL IS INTENDED FOR THOSE WHO HAVE FLASHED THE LATAM GINGERBREAD 2.3.6 VERSION WHICH ARE R01 AND R02, SUCH AS RETAIL LATAM, PERSONAL, CLARO, MOVISTAR AND VIVO
If you come from a different firmware this tutorial may not be entirely useful because the root method may vary and if you come from froyo you may need to use CH version for CM9, and flash a GB kernel for CM10... but that's not the point of this thread, go to the ROM's thread and READ the OP before asking dumb questions!
Click to expand...
Click to collapse
ROOT your phone (Check nicofff's method: http://forum.xda-developers.com/showthread.php?t=1750277)
Download and install Droid2Bootstrap (see attachments or http://www.mediafire.com/?rbie0acs53rdfwc)
Download bootmenu1.1.0 and put it on your SD Card (see attachments or http://www.mediafire.com/?lh61gvslph4x4sv)
For CM9 download latest European GB Kernel version this thread: http://forum.xda-developers.com/showthread.php?t=1623385 and latest ICS gapps from http://goo.im/gapps/ and put both zips on your SD Card
For CM10 download latest version from this thread: http://forum.xda-developers.com/showthread.php?t=1827801 and latest JB gapps from http://goo.im/gapps/ and put both zips on your SD Card
Open Droid2Bootstrap and grant it root permission
Hit "Bootstrap Recovery" You'll see a pop-up telling you "SUCCESS!"
Hit "Reboot Recovery" and your phone will reboot and enter on custom recovery
Select "Install zip from sd card" and then choose the bootmenu1.1.0.zip (use slider keyboard arrow keys to move, and "OK" button to select)
Reboot
When booting, the led will turn blue, press both volume buttons to enter bootmenu
In the bootmenu, go to "Recovery" > "Custom Recovery" (use volume buttons to move, power button to select)
In the custom recovery, select "Wipe data/factory reset" and "Wipe cache partition"
Go to "Advanced"
Select "Wipe Dalvik Cache" and "Wipe Battery Stats"
Go back and select "Install zip from sd card" and then choose the CyanogenMod zip file (CM9 or CM10)
Do the same for gapps: Choose gapps-ics-xxxxx.zip for CM9 and gapps-jb-xxxxx.zip for CM10
Reboot
Be happy
You should be booting into CyanogenMod now!
If your signal is not working try installing the MS2Toolbox (see attachments or http://www.mediafire.com/?k3h8vpcj6b2it0e) and then go to Baseband Switcher and choose your right band and then reboot, you might need to try more than once, but this tool will get your signal up
ALL CREDITS TO nicofff FOR THE ROOT METHOD, TO sfc3001 FOR THE CM9 ROM, AND TO tezet FOR THE CM10 ROM

Caesarivs said:
Well, now that it's possible to root this firmwares (check this thread: http://forum.xda-developers.com/showthread.php?t=1750277) it's possible to try some custom roms on our MS2, in this particular case I'll make a little guide on how to install sfc3001's CM9:
ROOT your phone (Check nicofff's method: http://forum.xda-developers.com/showthread.php?t=1750277)
Download and install Droid2Bootstrap (see attachments or http://www.mediafire.com/?rbie0acs53rdfwc)
Download bootmenu1.1.0 and put it on your SD Card (see attachments or http://www.mediafire.com/?lh61gvslph4x4sv)
Download CM9 and put it on your SD Card (download the latest version from this thread: http://forum.xda-developers.com/showthread.php?t=1623385)
Download Google Apps and put them on your SD Card (download the latest version from http://goo.im/gapps/)
Open Droid2Bootstrap and grant it root permission
Hit "Bootstrap Recovery" You'll see a pop-up telling you "SUCCESS!"
Hit "Reboot Recovery" and your phone will reboot and enter on custom recovery
Select "Install zip from sd card" and then choose the bootmenu1.1.0.zip (use slider keyboard arrow keys to move, and "OK" button to select)
Reboot
When booting, the led will turn blue, press both volume buttons to enter bootmenu
In the bootmenu, go to "Recovery" > "Custom Recovery" (use volume buttons to move, power button to select)
In the custom recovery, select "Install zip from sd card" and then choose the CM9 zip file
Do the same for gapps: "Install zip from sd card" > gapps.zip
Select "Wipe data/factory reset" and "Wipe cache partition"
Go to "Advanced"
Select "Wipe Dalvik Cache" and "Wipe Battery Stats"
Go back and reboot
You should be booting into ICS now!
If your signal is not working try installing the MS2Toolbox (see attachments or http://www.mediafire.com/?k3h8vpcj6b2it0e) and then go to Baseband Switcher and choose your right band and then reboot, you might need to try more than once, but this tool will get your signal up
ALL CREDITS TO nicofff FOR THE ROOT METHOD AND TO sfc3001 FOR THE CM9 ROM
Click to expand...
Click to collapse
:good::good: good, and now, i am on cm9:good::good:

THANKS! It was really helpful as I find it a bit difficult to install a custom ROM after getting root following nicofff procedure. Don't know why, but installing a zip the usual way didn't work. Then I followed your instructions and it worked like a charm.

Thanks that was almost too easy
I was already rooted before but did not dare the Cyanomod mainly to their alpha (still?) status, but when I heard about the feature that volume rocking allows skipping to the next song, I knew that I was doomed !
EDIT: BTW found it very stable after 1 day of extensive trial. I am really impressed !

Love this :good::good::good:

Hi,
first of all, thanks for this howto!
I am however getting problems. Coming from Brazilian VIVO 2.3.6. I succesfully completed all steps, until I get to rebooting after installing the bootmenu file. When I do a normal reboot, my phone's just rebooting into VIVO. When I choose to reboot recovery then I get an triangle image. When I push both volume rockers, I'm getting in another recovery menu. When I apply CM9 update, it will not verify.. That is where I'm stuck. Am I doing something wrong here?
SOLVED:
When you've installed bootmenu 1.1.0, it is possible that it does not load the first reboot. Just let it reboot normally, than reboot again! Now it worked!
thanks!

This is great! :good:
Few days ago I was looking for something like this but just can't find.
I experimented myself and got CM9 working on my phone.
(Took quite a lot of time waiting booting)
Thank god i did not brick my phone.
This will be great helpful to those who would like to try CM9.

Quick question - does this work with UK stock kernel?
Or does this require a specific kernel.
(How do I check?)

regiment said:
Quick question - does this work with UK stock kernel?
Or does this require a specific kernel.
(How do I check?)
Click to expand...
Click to collapse
This works for european GB kernels, and specifically for latinamerican R01 and R02 GBkernels (which are based on the european GB kernel)
When you go to settings -> About phone, what does it say in Android Version?

Nice Tutorial
Nice Tutorial! Really easy to follow.

:good: Great posts, thanks to you and the makers of "PreInstalameEsta" I've my phone working with this rom , for new updates of the rom do you know if it's necessary to wipe dalvik and cache or factory reset, I just don't want to sync all my accounts again ..
Thanks.

kainlite said:
:good: Great posts, thanks to you and the makers of "PreInstalameEsta" I've my phone working with this rom , for new updates of the rom do you know if it's necessary to wipe dalvik and cache or factory reset, I just don't want to sync all my accounts again ..
Thanks.
Click to expand...
Click to collapse
To update CMx roms from another version of the same branch (ie : a 7 to a 7, a 9 to a 9 and so on) you only need to :
- wipe cache partition
- wipe dalvik cache
- wipe battery stats (optional, it's just to get more accurate battery duration)

Ashareth said:
To update CMx roms from another version of the same branch (ie : a 7 to a 7, a 9 to a 9 and so on) you only need to :
- wipe cache partition
- wipe dalvik cache
- wipe battery stats (optional, it's just to get more accurate battery duration)
Click to expand...
Click to collapse
K, great, thanks

it works! thx a lot !
wait.....where is market ??
EDIT 3: done, i have just reflashed the file (gapp ) in recovery mode

hi all....new problems here
when i open play store it says me: server error
i avoided the problem flashing the gapp file from april instead the last one, now i would ask...what is the differences between the two files ? have i less features or a less fluidity ?
i have another question: where is swype keyboard ? i cant find it in settings !

sminatore said:
hi all....new problems here
when i open play store it says me: server error
i avoided the problem flashing the gapp file from april instead the last one, now i would ask...what is the differences between the two files ? have i less features or a less fluidity ?
i have another question: where is swype keyboard ? i cant find it in settings !
Click to expand...
Click to collapse
I haven't had any problems with latest ICS gapps, are you sure you flashed ICS gapps? Anyway you should always do at least wipe cache and dalvik cache, it's best if you do full wipes AFTER flashing gapps
Swype keyboard is not included in CM9... you can get it from beta.swype.com

Caesarivs said:
I haven't had any problems with latest ICS gapps, are you sure you flashed ICS gapps? Anyway you should always do at least wipe cache and dalvik cache, it's best if you do full wipes AFTER flashing gapps
Swype keyboard is not included in CM9... you can get it from beta.swype.com
Click to expand...
Click to collapse
yes yes im sure ....
ok thx for infos :good:

Caesarivs said:
This works for european GB kernels, and specifically for latinamerican R01 and R02 GBkernels (which are based on the european GB kernel)
When you go to settings -> About phone, what does it say in Android Version?
Click to expand...
Click to collapse
I am currently running Tezet's CM7 ROM 120221-1901-NIGHTLY (Android 2.3.7).
Still not sure what kernel is running!

regiment said:
I am currently running Tezet's CM7 ROM 120221-1901-NIGHTLY (Android 2.3.7).
Still not sure what kernel is running!
Click to expand...
Click to collapse
You must be on Froyo... because tezet's CM7 doesn't work on gingerbread, so if you want to try CM9 you must use Chinese version

In this case, can I follow the 1st post tuto ?
Caesarivs said:
You must be on Froyo... because tezet's CM7 doesn't work on gingerbread, so if you want to try CM9 you must use Chinese version
Click to expand...
Click to collapse
Sent from my MotoA953 using xda premium

can't change TWRP 2.1.1 settings to stop official recovery from reinstalling

Hi all,
I have a Nexus 7, rooted, running stock 4.1.1 rom, and just installed TWRP 2.1.1
I have been reading this thread, http://forum.xda-developers.com/showthread.php?t=1779092 , however I cannot post on the thread due to being a new/low post count member.
I read that, and it does happen, that each time I reboot, the stock recovery reinstalls itself.
I attempted to follow this....
NOTE: The stock ROM may automatically replace TWRP with the stock recovery. To prevent the stock ROM from replacing TWRP, boot TWRP, go to the mount menu and mount system, press the home button, then press Advanced -> File Manager. Browse to /system and select the file named recovery-from-boot.p then choose to rename the file to recovery-from-boot.bak
Click to expand...
Click to collapse
but it doesn't seem to work.
Firstly, when I go to the "Mount" menu, there is only 3 entries.....1 large button which says "Mount USB Storage", and 2 boxes which are selected with a cross in the box, "Unmount Data", and "Unmount Cache". If I do press Mount USB Storage I can only Unmount it to return to menu.
So regardless of that part, if I then go to the file manager, and browse to the system folder, the folder shows up empty, and the only thing showing is a Bin subfolder (also empty)
any ideas whats wrong?

Use the one-click root tool. Install TWRP via GooManager. Profit.
Sent from my Nexus 7

TheBiles said:
Use the one-click root tool. Install TWRP via GooManager. Profit.
Sent from my Nexus 7
Click to expand...
Click to collapse
hi,
yeah I did use the tool, all is rooted fine. If you install TWRP from GooManager, and then press to reset to recovery, TWRP loads fine. Once you reboot again however, the stock roms overwriting the TWRP so it no longer works each time. The steps there were supposedly to stop this from happening, from within TWRP, however the options aren't even there. Sadly, I can't post in the TWRP thread due to having less than 10 posts

How r u booting into recovery? Do u power off then use button combo? I use quickboot from market. Its free and boots u into recovery without having to manually turn off the device. I had the same exact issue u drescribe when attempting to follow op instructions. I couldn't do it so I said what the hell, let me see if I boot into recovery using quickboot it overwrites. I was happy to discover that it didn't.
Sent from my EVO using Tapatalk 2

Hi.
I booted into recovery directly from the GooManager option which restarts it into it for me. After a reboot though choosing the same option gives the official recovery I presume (android robot with chest open and exclamation mark)....until I tell it to install the OpenRecoveryScript again
I'm not familiar with Quickboot - take it its just a button to press to get it into recovery the same way as the GooManager option of "Reboot Recovery"?
I'm looking at this TeamEOS nightly build at the moment, toying with the idea of whether to stick with stock rom or flash their custom rom over it.....hard call as its still early days for the roms I think, but if spend ages again installing my apps, will have to do it again afresh when do eventually change the rom

Midnight Tboy said:
Hi.
I booted into recovery directly from the GooManager option which restarts it into it for me. After a reboot though choosing the same option gives the official recovery I presume (android robot with chest open and exclamation mark)....until I tell it to install the OpenRecoveryScript again
I'm not familiar with Quickboot - take it its just a button to press to get it into recovery the same way as the GooManager option of "Reboot Recovery"?
I'm looking at this TeamEOS nightly build at the moment, toying with the idea of whether to stick with stock rom or flash their custom rom over it.....hard call as its still early days for the roms I think, but if spend ages again installing my apps, will have to do it again afresh when do eventually change the rom
Click to expand...
Click to collapse
Yes quickboot is as u describe. I know what u mean about starting to flash. It's a bit early for me considering conditions of the roms ( early stages). I am getting tempted tho...lol. won't be long I'm sure.
Sent from my EVO using Tapatalk 2

pathtologos said:
Yes quickboot is as u describe. I know what u mean about starting to flash. It's a bit early for me considering conditions of the roms ( early stages). I am getting tempted tho...lol. won't be long I'm sure.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
yup....just installed Quick Boot (Reboot),
chose Recovery, and again its rebooting back to the original recovery instead of the TWRP.
Guess I'll have to flash to a custom rom to get around it if want it sorting now....or wait till I have the minimum post count to post on the main TWRP thread
Not end of the world to reinstall apps and games I guess when the custom roms are more mature, so long as I remember to use Titanium Backup to save my games progress

you need to rename the recovery-restore.sh file in /system/etc/ (I forget the name offhand - if you look at the filenames there you'll figure it out). It restores the stock recovery at every reboot unless deleted or renamed. Then flash your 3rd party recovery.

Hi,
thats the trouble.....I use the file manager in TWRP, and I can't see that file anywhere.
The TWRP page says to go to /system......but when I go there its empty, only one subfolder, /system/bin, which also shows up empty

[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.

[GUIDE/TUTORIAL/HOWTO] Samsung Galaxy S7 herolte Stock to Android 13

[GUIDE/TUTORIAL/HOWTO] Samsung Galaxy S7 herolte Stock to Android 13
[GUIDE/TUTORIAL/HOWTO] Samsung Galaxy S7 herolte (Exynos SOC) Stock to Android 13 / LineageOS 20
Supported models:
International & Canada:
- SM-G930F
- SM-G930FD
- SM-G930W8
Korea:
- SM-G930S
- SM-G930K
- SM-G930L
This detailed step-by-step guide helps you transform your Samsung Galaxy S7 herolte to a powerful one with Android 13.
Make sure your phone is herolte/Exynos before going further: in Android, go to Settings > About phone > Check model number is listed below.
If not, quit this tutorial.
### READ THOSE WARNING COMMENTS
CHANGELOG
v9. Back to TWRP 3.6 until 3.7 is fixed
v8. Android 13, TWRP 3.7
v7. BiTGApps v1, Magisk v25
v6. Switch to MindTheGApps as BiTgapps are dead, TWRP 3.6.2
v5. Add Screen definition override with adb folder + screen sensitivity recalibration, TWRP 3.6.1
v4. Android 12, improve readability, fix ROM download link, TWRP 3.6
v3. Android 11, Magisk 22, fixed the missing OEM unlock description
v2. Moved to LineageOS 17.1 because of low call sound on earpiece with Pixel Experience
v1. Initial release for Android 10 / Pixel Experience
1) DOWNLOAD
- djibe Galaxy S7 herolte pack: https://bit.ly/djibe-galaxys7-pack
(contains Samsung tweaked Odin 3.13.1 + Samsung USB drivers + TWRP 3.6.2_9-0 official recovery + Magisk Root + adb.exe). Unzip files.
+ ROM Unofficial LineageOS 20: https://forum.xda-developers.com/t/...e-spoofing-ota-updates-for-s7-exynos.4484505/
Download latest build: https://ivanmeler.github.io/devices/herolte.html
+ BiTGApps Package ARM64 13: https://github.com/BiTGApps/BiTGApps-Release/releases
OR NikGApps T Basic: https://sourceforge.net/projects/nikgapps/files/Canary-Releases/NikGapps-T/
OR MindTheGApps 13 ARM64: http://downloads.codefi.re/jdcteam/javelinanddart/gapps
+ Charge phone to 100%
2) BACKUP DATA
Install Samsung USB drivers (you unzipped earlier).
Then plug phone to PC in File transfer mode.
Collect all .jpg or .mp4
Use Google built-in cloud to backup apps like SMS Backup & Restore to backup texts, contacts, etc.
Backup your WhatsApp messages in Google Drive.
Everything else: podcasts, Authenticators, TODOs etc...
Then copy the backup on your PC.
Make sure you have latest official updates for your phone:
Connect to Wifi and go to Settings > About device > Software update > Update now
### BACKUP NOW, you will lose everything.
3) FLASH TWRP 3.7 RECOVERY
Go to Settings > About phone.
Tap 7 times on Build number item to unlock Developer options.
Go to Settings > Developer options, switch OEM unlock ON.
Shut down phone.
Boot in Download Mode: hold Home + Power + Volume- until you see Samsung's logo and release all buttons.
Confirm access to Download mode by pressing Volume+.
Phone now displays "Download mode, do not turn off target".
Connect phone in USB, wait for 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.2_9-0-herolte.img.tar
### Same recovery for Korean models (G930S/K/L variants)
### Warranty will be Void after next click ###
Click Start.
Wait until flash Success message appears.
Unplug phone.
Restart phone to recovery :
- hold Power + Home + Volume- until phone screen becomes black.
- and immediatly switch from Volume- to Volume+ (still holding Power + Home) to land in TWRP recovery.
### If Android launches, hold 3 buttons until phone restarts and Samsung logo appears.
4) BACKUP IMEI PARTITION AND SYSTEM (Nandroid backup)
Boot in Recovery Mode : Hold Home + Power + Volume+ until you see Samsung's logo then release and wait a few seconds for TWRP recovery to boot.
Recovery asks for Keep System Read Only ? > Swipe to Allow Modifications.
Go to Wipe > Format Data.
Type: yes and confirm with bottom right check icon.
Encryption is removed. You can now access partitions.
### If you miss this step you won't have access to any partition.
Back to home menu > Backup.
You can now select the partitions you want to save.
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 Boot, System, Cache, Baseband and EFS partitions. In case of problem, you will have your phone in its original state.
Swipe to Backup and wait during process.
Go to Home screen and continue with next chapter.
Save backup: still under TWRP recovery, connect phone to PC.
Go to Mount menu and check Data partition is checked and MTB button is on "Disable MTP" state.
From Windows explorer, access phones memory and copy-paste the TWRP folder (located in root folder, beside DCIM and Music folders) somewhere safe on your computer.
5) FORMAT PARTITIONS
### Make sure you copied TWRP backup from internal memory to somewhere safe.
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.
Back to TWRP home screen, go to Reboot > Recovery and swipe to reboot.
On next launch, check the checkbox to remember choice and swipe to allow modifications.
6) FLASH ROM, (MAGISK ROOT) AND GAPPS
Back to TWRP main menu, go to Mount menu again to connect phone to PC again.
Connect phone to PC and use Windows explorer to copy files on phone's internal memory.
Copy TWRP folder from your phone to somewhere safe on PC.
This backup can restore your phone to its original Samsung state.
Copy files of ROM + GApps + Magisk on phone.
Go back to TWRP Home menu. Then tap on Install > choose lineage*.zip,
Optional for root: Add More zips > Magisk*.zip
then Swipe to confirm Flash.
Wait for operation to end.
Go to Reboot > Recovery and swipe to reboot.
After restart, go to Install, select bitgapps*.zip and swipe to flash.
Then tap Wipe cache/dalvik, swipe to confirm,
then Reboot System and on Install TWRP App? menu, tap on button Do Not Install
Wait for the phone to boot during 5 minutes.
7) ROOT ACCESS (OPTIONAL)
Configure Android as you like.
Don't try to set fingerprints at first setup. It will crash.
No need for extra work to be root.
Magisk launches with Android.
Superuser permissions can be managed from Magisk Manager app.
8) TWEAKS
- Calibrate battery: https://www.ifixit.com/Wiki/Battery_Calibration
- Set dark Mode to improve battery by 30%
Settings > Display > Dark theme.
- For better battery, remove Always on display
Settings > Display > Screen saver > Desactivated
- Activate Developer options
Go to Settings > About.
At bottom, tap 7 times on Build number. You activated Developer options.
Go to Settings > System > Avdanced > Developer options.
- Change screen definition for low GPU/CPU usage: from 1440x2560 to 1080x1920
You need developer options to enable USB debugging.
Open a terminal where adb.exe from my pack is located.
Plug phone and Authorize USB debugging.
Then type:
Code:
adb shell wm size 1080x1920 && adb shell wm density 480
// Defaults 1440x2560 and 640
- Screen sensitivity is too low ?
Try to recalibrate screen sensitivity with https://play.google.com/store/apps/details?id=touchcalibration.favoritappindia&hl=en&gl=US
Enjoy,
djibe
Thanks: @Ivan_Meler, LineageOS team, TWRP team
---------------------------------------
Coming from another ROM
- Backup
- Recovery: Wipe Cache, Dalvik cache, System and Format Data > yes
- Reboot recovery
- Flash rom
- Reboot recovery
- Flash BitGApps
Enjoy
Force Samsung Galaxy S7 restart
Hold Power + Volume down for 10-20 seconds

Updated tutorial for LineageOS 17.1 as Pixel Experience call volume is really too low.

Thank you for this guide.
Used with 18.1 + NikGapps core 65 + Magisk and work absolutely fine.

ytccts said:
Thank you for this guide.
Used with 18.1 + NikGapps core 65 + Magisk and work absolutely fine.
Click to expand...
Click to collapse
Hi,
Thanks for sharing.
I'll test your packages and then update tutorial for everyone.
Enjoy.
S7 is damn good.

Hey, thanks for the detailed explanation. Will root and install Lineage in upcoming weekend. Before proceeding with tripping knox, will I be able to use Google Pay and banking apps after installing Lineage ROM? Will wireless charging work? And if I do not want to take backup, will I be able to flash stock firmware in future to revert back to original? There was a time when I was into this stuff rooting and custom ROMS, but now I am too old for it and just being cautious. Thanks again dear.

abhi_qwerty said:
Hey, thanks for the detailed explanation. Will root and install Lineage in upcoming weekend. Before proceeding with tripping knox, will I be able to use Google Pay and banking apps after installing Lineage ROM? Will wireless charging work? And if I do not want to take backup, will I be able to flash stock firmware in future to revert back to original? There was a time when I was into this stuff rooting and custom ROMS, but now I am too old for it and just being cautious. Thanks again dear.
Click to expand...
Click to collapse
Hi,
Thanks for your message.
PLEASE make a TWRP backup before flashing, it just takes 2 minutes.
No idea for wireless charging. You may ask in ROM's thread
Normaly banking apps work with Magisk + MagiskHide module

Hi, updated pack for latest TWRP and Magisk.
Switched ROM to Android 11.

thanks a lot for this guide!
I successfully used it on my SM-G930F with following files:
- twrp-3.5.2_9-0-herolte.img.tar
- lineage-18.1-20210505-UNOFFICIAL-herolte.zip
- MinMicroG-NoGoolag-2.10-20210428084817-signed.zip

Thank you Master especially for the tutorial, Before this I was tried out 10 methods but only this works with oreo.

Hi, I updated tutorial for Android 12

I'v found a bug in a 11.
The battery only charging max 75%, but if I turn off it can be load normally

djibe89 said:
Hi, I updated tutorial for Android 12
Click to expand...
Click to collapse
Thank you kindly this is exactly what I have been looking for. God bless you and Merry Christmas

donnytuco said:
Thank you kindly this is exactly what I have been looking for. God bless you and Merry Christmas
Click to expand...
Click to collapse
Glad you liked it ! Merry Christmas

Thanks for this excellent instruction.
Maybe you'd like to consider one small change in part 6 - Flash ROM, Gapps, Magisk.
According to the devs of BitGapps they suggest to do a reboot to recovery after flashing of ROM:
GitHub - BiTGApps/BiTGApps: The main repository of The BiTGApps Project
The main repository of The BiTGApps Project. Contribute to BiTGApps/BiTGApps development by creating an account on GitHub.
github.com

bgsdeluxe said:
Thanks for this excellent instruction.
Maybe you'd like to consider one small change in part 6 - Flash ROM, Gapps, Magisk.
According to the devs of BitGapps they suggest to do a reboot to recovery after flashing of ROM:
GitHub - BiTGApps/BiTGApps: The main repository of The BiTGApps Project
The main repository of The BiTGApps Project. Contribute to BiTGApps/BiTGApps development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Done, thanks !!

Could you add part 9) UPDATE, please. In case of a newer rom.

blinthor said:
Could you add part 9) UPDATE, please. In case of a newer rom.
Click to expand...
Click to collapse
Hi, then you have to "Clean flash"

djibe89 said:
Hi, then you have to "Clean flash"
Click to expand...
Click to collapse
I do not know if I understand correctly.
1. Install new rom
2. Wipe Dalvik, Cache
What about BitGapps. Do you install after rom or not?

blinthor said:
I do not know if I understand correctly.
1. Install new rom
2. Wipe Dalvik, Cache
What about BitGapps. Do you install after rom or not?
Click to expand...
Click to collapse
- Backup
- Wipe Cache, Dalvik cache, System and Format Data > yes
- Reboot recovery
- Flash rom
- Reboot recovery
- Flash BitGApps
Enjoy

djibe89 said:
- Backup
- Wipe Cache, Dalvik cache, System and Format Data > yes
- Reboot recovery
- Flash rom
- Reboot recovery
- Flash BitGApps
Enjoy
Click to expand...
Click to collapse
Thanks