Database Users

[GUIDE] How to Install Cyanogenmod 7.1 from Stock 2.1

The procedure is quite simple.
Step 1.
Download the following tools:
Cyanogen Mod 7.1 for Xperia X8 (code named Shakira)
FlashTool
FXP030 kernel (2.6.29)
Step 2.
Step 2.1
Follow the guide located here to unlock your bootloader, do this before continuing with the rest of this guide it is important to have your stock firmware rooted for this step.
Step 2.2
Unzip flashtool to its own folder e.g. /Flashtool/.
Unzip FXP030 kernel to the Flashtool/firmwares/ folder - the directory should look like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 3.
Step 3.1
Open Flashtool and click on the 'Flash' button, select the FXP firmware from the list on the left hand side and click OK.
Step 3.2
Follow the on screen instructions.
Step 4.
Copy the update-cm-7.1.0-X8-signed.zip to the root of your MicroSD Card as shown below. (Please note that you can do this using a MicroSD Card reader OR your USB cable.
If you do not have a card reader then switch your phone on after flashing the FXP kernel and when you see the FreeXperia logo, repeatedly press the Back button until CWM loads. Once CWM has loaded scroll down to the Mounts and Storage menu. Once on the mounts and Storage menu scoll down to mount USB Storage and copy the update-cm-7.1.0-X8-signed.zip file to the root of the SD card.
Step 5.
Load CWM via the method described in Step 4 and select 'Install Zip from SD card.' then select 'Choose Zip from sdcard' and select the update-cm-7.1.0-X8-signed.zip that you copied over to the root of the SDCard in the previous step, Select the yes option using the volume buttons and let CWM work its witchcraft.
Step 6.
Go back to the main menu of CWM and select 'wipe data/factory reset'.
Next from the main menu of CWM select 'wipe cache partition'.
Finally from the main menu of CWM select 'Advanced' and 'wipe dalvik cache.
Optional
If you want the google apps installed you can download them here. To install them perform Step 4 through to Step 5 and instead of copying 'update-cm-7.1.0-X8-signed.zip' to the root of your sdcard, copy gapps-gb-20110613-signed.zip instead. All instructions in Step 4 and Step 5 that state you should use 'update-cm-7.1.0-X8-signed.zip' should use the file 'gapps-gb-20110613-signed.zip' instead.
Notes:
I'm having issues with the networking with this custom firmware, specifically the network (3G or WiFi) seems to 'drop' after any amount of small usage. If I use a Browser or the Market place for a short amount of time, they simply end up unable to load any pages whilst android reports that wifi/3g signal strengths are full. I tested the connectivity using ping commands from terminal and pings are succesfull. I'm unsure where the issue lies. I suspect however the issue is in the FXP Kernel, some people have reported using FXP 028 Kernel resolves the issues but I've been unable to find them.
Anyway I hope this helps people who are confused as to how to install this.
Credits:
Thanks to Paschalis for correcting an error in my wording.
Thanks go to dbts25 for pointing out mistakes and un-neccessary steps in the guide, sincethen the guide has been edited to be easier to follow and less convoluted.
Thanks go to rav3n_pl for the revised bootloader bundled with the kernel.

Vanilla is the AOSP, Android Open Source Project..
You mean stock, right?
Btw this kernel has wifi issues?
Tried many kernels, and wifi wont open with none of them..

Paschalis said:
Vanilla is the AOSP, Android Open Source Project..
You mean stock, right?
Btw this kernel has wifi issues?
Tried many kernels, and wifi wont open with none of them..
Click to expand...
Click to collapse
Ah Yes, I mean stock. It's 2:34am... That's my excuse haha, between university and sleep deprivation the mistakes keep mounting hehe. Thanks for pointing that out anyways.
And yes, it seems this kernel has issues with data connectivity, and call volume as well for some odd reason. It boggles the mind as to why it's been labelled 'stable'. Stable usually means it's solid and won't fall over and die, plus data connectivity on an android handset is really a critical feature, if it is buggy the custom firmware should not be labelled as stable.

It really need custom kernel?

Hehe.. Same university thing here, only difference here its 4:40, and got lesson at 8:30..
On my other phone, CM is beta and not Official yet, and its working perfectly, except 2 special features they didnt port yet, from stock rom..
If you find the 28 kernel, post it, until they release the 31!
Thanks!

EL_BELLACO said:
It really need custom kernel?
Click to expand...
Click to collapse
Yes, if you don't use a custom firmware it will get stuck in a boot loop and be unable to boot.
Paschalis said:
Hehe.. Same university thing here, only difference here its 4:40, and got lesson at 8:30..
On my other phone, CM is beta and not Official yet, and its working perfectly, except 2 special features they didnt port yet, from stock rom..
If you find the 28 kernel, post it, until they release the 31!
Thanks!
Click to expand...
Click to collapse
If I come across it I will, I'll edit my guide to feature it as a work around for connectivity issues for people in the meantime, if it works correctly.
I've got to admit though, issues aside - it is amazing what the open source community is capable of creating. CM 7.1 looks absolutely fantastic, I love the boot animation.

I have tried FXP028, FXP030 and the one that is included with the CM7.1 release, i'm having network problems with all of them.

termin8tor said:
.
Step 5.
Turn your phone on and repeatedly press the back button until you are displayed with the CWM menu. On this menu select 'install zip from sdcard' and then choose the 'choose zip from sdcard' select the cyanogenmod file you downloaded and let it do its thing.
Click to expand...
Click to collapse
In step 5 you forgot one thing:
Flash Google Apps. You can find it here: http://cmw.22aaf3.com/gapps/gapps-gb-20110613-signed.zip
Step 2 is unnecessary, because CWM Recovery is built-in FXP Kernel so you don't need to install it.

poisike said:
I have tried FXP028, FXP030 and the one that is included with the CM7.1 release, i'm having network problems with all of them.
Click to expand...
Click to collapse
Can you please share the FXP028 kernel?

has any of you tried the dx kernel yet? with cynanogen mod 7.1

No workie. Rom+kernel need match.
An I wrote it that way:
http://forum.xda-developers.com/showpost.php?p=18364335&postcount=1879

dbts25 said:
In step 5 you forgot one thing:
Flash Google Apps. You can find it here: http://cmw.22aaf3.com/gapps/gapps-gb-20110613-signed.zip
Step 2 is unnecessary, because CWM Recovery is built-in FXP Kernel so you don't need to install it.
Click to expand...
Click to collapse
I've edited the guide to eliminate that pointless step in the original guide version, thankyou for pointing it out!
Additionally the google apps step has been added to the end of the tutorial.
tonks22 said:
has any of you tried the dx kernel yet? with cynanogen mod 7.1
Click to expand...
Click to collapse
Unfortunately the rom will not boot with the DX kernel, I tried it myself and it gets stuck in a boot loop.
rav3n_pl said:
No workie. Rom+kernel need match.
An I wrote it that way:
http://forum.xda-developers.com/showpost.php?p=18364335&postcount=1879
Click to expand...
Click to collapse
I have included the correct kernel for the official cyanogenmod 7.1 rom and slipstreamed your edited loader into the kernel package for peoples convenience. Thanks for linking me to your post!
Hope this helps people!

It seems that this Rom and kernel [cm7] doesn't work.When i flash the kernel my SD is not recognized.And if i uninstall the kernel and try to flash the rom...i get a biiiiigg eror

i hope that they will also make a ROM that is compatible with stock kernel so that it will be easy to install... im having second thought of unlocking my bootloader because of this:
Before I start I must emphasise the fact that meddling with the bootloader is highly dangerous and will result in a hard brick if you don't follow proper instructions. Then, you will have to go and repair your phone by sending it to SE . I am not responsible if your phone dies on you because you didn't follow instructions or you screwed up somehow. I must also mention that this will probably void your warranty (rooting already probably voided it though) and that there is NO WAY to relock bootloader as of now.
Click to expand...
Click to collapse
i know they can make one because they are great programmer...

if you have bought your phone unlocked, things are pretty simple..
That tutorial, should be writtenmore clearly/easy..
Cos in fact its not too dificult..
Sent from my MB860 using XDA App

Paschalis said:
if you have bought your phone unlocked, things are pretty simple..
That tutorial, should be writtenmore clearly/easy..
Cos in fact its not too dificult..
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
yes i bought my phone from SE and its already unlocked... i think i'll try it when this ROM will be released as a completely working ginger without bugs...
i find this http://forum.xda-developers.com/showthread.php?t=1254225
as very informative but confusing tutorial... is there any other short and simple tutorial here??

mikel_0004 said:
yes i bought my phone from SE and its already unlocked... i think i'll try it when this ROM will be released as a completely working ginger without bugs...
i find this http://forum.xda-developers.com/showthread.php?t=1254225
as very informative but confusing tutorial... is there any other short and simple tutorial here??
Click to expand...
Click to collapse
There:
http://forum.xda-developers.com/showpost.php?p=17656148&postcount=1

Can it be installed WITHOUT unlocking the bootloader?
Thanks

thu001 said:
Can it be installed WITHOUT unlocking the bootloader?
Click to expand...
Click to collapse
I`m not 100% sure that cm71 rom will work on stock kernel...
When I flashed it under installed CM7 it stuck on bootanimation. Mybe full wipe? Not tried.

Hello
I installed on my Xperia X8 CM7.1 (I had version 2.1 of Android root), but it does not work the WiFi network and the 3G connection is disconnected, it did not work properly Market (having installed the GAPPS). My question, is there any way to get back to my terminal to android 2.1? I did a Back up of my system, but in trying to restore from CWM mistake I make, I guess it is for the kernel.

[L09][C432][7.0][EMUI 5.0.X] octoPLUS v1.1 - B382 (03.24.18)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
octoPLUS is a ROM resulted by a headproject on P9 and at least an addition to all P9 Plus running an L09 model on C432.
We know 99%, oreo will come to this device and someaday more of my builds
I hope everyone get it working
Instructions
000. If rooted before, use unSU script by osmOsis
1. Use latest TWRP + Firmware as possible (every build is listed to work with followed build state)
2. Wipe data, vendor and system + internal for clean flash (cust,version and product wiped by script)
3. Flash zip and wait until its finish
4. Reboot device
5. Be happy with a hopefully better working device.
Safetynet Workaround
1. After boot enable developer options
2. Enable ADB debugging
3. Enable USB debugging
4. Rebootdevice again
5. Check Safetynet
Changelog (comming soon)
v1.1
March security patch
Download
XDA:DevDB Information
[L09][C432][7.0][EMUI 5.0.X] octoPLUS v1.1 - B382 (03.24.18), ROM for the Huawei P9 Plus
Contributors
dkionline
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 4.x
ROM Firmware Required: 382
Version Information
Status: Stable
Current Stable Version: v1.1
Created 2018-03-27
Last Updated 2018-03-26

Wonderful news this ROM is. Would you be kind to post some screenshots, more details etc... Is it only for the model you have written on the thread or it could be flashed to other P9+ models? I own VIE-L29C185.
Either way thank you for your effort.

Video or image? Good work

Works great. The only issue i have is that Snapchat isnt working anymore. How can i solve this?
Solved: hide via magisk!

dkionline said:
octoPLUS is a ROM resulted by a headproject on P9 and at least an addition to all P9 Plus running an L09 model on C432.
We know 99%, oreo will come to this device and someaday more of my builds
I hope everyone get it working
Instructions
000. If rooted before, use unSU script by osmOsis
1. Use latest TWRP + Firmware as possible (every build is listed to work with followed build state)
2. Wipe data, vendor and system + internal for clean flash (cust,version and product wiped by script)
3. Flash zip and wait until its finish
4. Reboot device
5. Be happy with a hopefully better working device.
Safetynet Workaround
1. After boot enable developer options
2. Enable ADB debugging
3. Enable USB debugging
4. Rebootdevice again
5. Check Safetynet
Changelog (comming soon)
v1.1
March security patch
Download
XDA:DevDB Information
[L09][C432][7.0][EMUI 5.0.X] octoPLUS v1.1 - B382 (03.24.18), ROM for the Huawei P9 Plus
Contributors
dkionline
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 4.x
ROM Firmware Required: 382
Version Information
Status: Stable
Current Stable Version: v1.1
Created 2018-03-27
Last Updated 2018-03-26
Click to expand...
Click to collapse
good work！after p9 get oero，it may get a pt. could you built the rom like lineage on p9plus?

jakiced said:
Wonderful news this ROM is. Would you be kind to post some screenshots, more details etc... Is it only for the model you have written on the thread or it could be flashed to other P9+ models? I own VIE-L29C185.
Either way thank you for your effort.
Click to expand...
Click to collapse
We have to test it together, maybe we find the needed part.
nightcervant said:
Video or image? Good work
Click to expand...
Click to collapse
Mostly same like P9. Will post after april patch arrives.
dgqyushen011223 said:
good work！after p9 get oero，it may get a pt. could you built the rom like lineage on p9plus?
Click to expand...
Click to collapse
Its a mather of how stable the EMUI sources are, but im too want run it more or less with 8.1 or later with P, but time will say what comming to us.

Sorry but I don't understand , what are the main differences Vs stock rom ?

Fil76 said:
Sorry but I don't understand , what are the main differences Vs stock rom ?
Click to expand...
Click to collapse
Deleted some apps and changed structure on screen. Updated most apps to actual version.

- Fingerprint sensor does not work (back to previous screen)
- Developer options does not work (I cannot enter to enable USB debugging or allow unknown applications)
- Advanced settings does not work either (I cannot allow connection to Hisuite for restore / backup)
- PIN for unlock screen not work, forced close settings. A security bug or error?
- Bluetooth not work
- Impossible to uninstall anything, crash and soft reboot

Solved (parcially)
An error during installation not installing /cust and other things.
Only bluetooth, NFC and notepad, calculator and other apps installation errors persists.

@NandoHerrera tell me what you did before flashing. Maybe i can Change the script in Next build.

Hi, i wan't to go back to stock rom. But if i try to install via sdcard, i get the error, that the firmware is up to date and it don't want to install. I think the problem is the build-number. How can i fix this problem?

Works great... just asking in advance, if I want to go back to original stock rom, can I just do the dload folder with update.app and press all 3 side buttons to flash back? Thank you

n8210 said:
Works great... just asking in advance, if I want to go back to original stock rom, can I just do the dload folder with update.app and press all 3 side buttons to flash back? Thank you
Click to expand...
Click to collapse
No, this is blocked. Better load with erecovery, or hwota/HuRu.

dkionline said:
No, this is blocked. Better load with erecovery, or hwota/HuRu.
Click to expand...
Click to collapse
Thanks again. I was playing around with eRecovery before this and but I never got it to work. It will connect to the house wifi but never did managed to download or restore. Using mobile data is the same. Nothing gets done.
Btw, with P9 Plus VIE-L29, when we use update.app, do we put the dload folder on the external sd card or on the phone's internal memory???
Currently everything works great. Definitely increased in sound volume. With the original rom, i always have the volume at 80-90%. With your rom, I have to set it to 40-50% or else it is too loud for my environment. Loving it so far...

n8210 said:
Thanks again. I was playing around with eRecovery before this and but I never got it to work. It will connect to the house wifi but never did managed to download or restore. Using mobile data is the same. Nothing gets done.
Btw, with P9 Plus VIE-L29, when we use update.app, do we put the dload folder on the external sd card or on the phone's internal memory???
Click to expand...
Click to collapse
eRecovery is working on European brands only with changing DNS in Router and register the exact Firmware.
dload isn't working with FullOTA-MF, as @dkionline mentioned.
For going back to Stock Firmware (for some reason in the future) you can use for VIE this method:
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3

Tecalote said:
eRecovery is working on European brands only with changing DNS in Router and register the exact Firmware.
dload isn't working with FullOTA-MF, as @dkionline mentioned.
For going back to Stock Firmware (for some reason in the future) you can use for VIE this method:
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
Click to expand...
Click to collapse
Thanks. Well, always have a Plan B instead of searching for one when I absolutely need it. And going back to original stock rom is the safest. Have a nice weekend, thank you once again.

How do i get the navigation keys to the bottom of the screen when i am in landscape mode?

[CLOSED][EOL][RECOVERY] TWRP 3.5.0-1 For Samsung Galaxy J2 2016

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This thread is done for.
Use https://forum.xda-developers.com/t/...-0-for-samsung-galaxy-j2-2016-j2xlte.4224479/ from now on
No more replies/updates will be done to this thread.
About Team Win Recovery Project
Team Win Recovery Project 3.x, or TWRP3.x for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface so no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Working:​
Boots
Restore function works
Backup works
Flashing works
Wiping works
Changing the settings works
Current Bugs [will hopefully be resolved soon]: ​
MTP does not work (use ADB push/pull)
TOUCH SCREEN LAG FIX: https://forum.xda-developers.com/t/...-samsung-galaxy-j2-2016.4194407/post-84232565 [WARNING: THIS HAS A CHANCE TO DESTROY YOUR TOUCH SCREEN]
Installation Instructions:
There are two methods for the installation:
1: Flashing directly via ODIN.
2: Flashing from existing TWRP or PitchBlack Recovery Project.
Method one:
[MAKE SURE YOU HAVE OEM UNLOCK AND USB DEBUGGING ENABLED]
1: Download the tar file from my Github (link will be given below).
2: Put your Samsung device into Download Mode.
3: After doing that, open ODIN v3.10.7 inside of your PC.
4: Click on AP, and locate to the place where you have saved the TWRP tar file.
5: After doing that, connect your phone to the PC and hit START.
6: The phone should automatically reboot. Then turn it off again and reboot to recovery. Done!
Method two:
1: Download the img file and reboot to recovery of your choice.
2: Select "Install".
3: Press "Install Image".
4: Then search for the place where you saved the img.
5: Flash it and reboot to recovery again. Done!​
Downloads
v3.5.0-0 Flashable Image and Tar file can be found here
https://github.com/NullCode13/TWRP_tree_j2xlte/releases/tag/v3.5.0-stable
v3.4.0-0 Flashable Image and Tar file can be found here
https://github.com/NullCode13/TWRP_tree_j2xlte/releases/tag/v3.4.0-beta
v3.2.3-0 has been REMOVED (due to its unstable and laggy nature)
v3.1.1-1 Tar file can be found here (extract img file by opening Tar file)
https://androidfilehost.com/?fid=817906626617934570
Device Tree with compiling instructions:
https://github.com/NullCode13/TWRP_tree_j2xlte/
XDA:DevDB Information
Team Win Recovery Project, Tool/Utility for the Samsung Galaxy J2
Contributors
NullCode, Aditya Kr
Source Code: https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni
Version Information
Status: Testing
Current Beta Version: 3.5.0-1_nullcode
Beta Release Date: 2020-11-24
Created 2020-11-24
Last Updated 2020-12-29

Reserved
Credits:​Aditya Kr for compiling TWRP v3.1.1-1
@fichl for the dark theme [which I modified of course] [sorry for not taking your permission fichl, please forgive me]
And me for compiling the upgraded recovery versions

Screenshots:

Version upgraded even further (to v3.5.0-0)

Bro, don't port more custom recoveries. Take this twrp and resolve its touch problem please. Pls port android 8,9,10 or 11 stock android rom for j210f. But first, please fix twrp's touch on this phone.

Kartikkala said:
Bro, don't port more custom recoveries. Take this twrp and resolve its touch problem please. Pls port android 8,9,10 or 11 stock android rom for j210f. But first, please fix twrp's touch on this phone.
Click to expand...
Click to collapse
Number 1: I don't port custom recoveries. I take my time to compile everything from source with my own tree (because ported TWRP laggy).
Number 2: I'm not listening to you. If you don't appreciate what a 13 year old does, I will just cancel my order of a Hard Disk that I bought specifically for compiling Android Oreo (and save my money)
Number 3: I have already fixed the touch problem, I forgot to put it in the thread. But because of people like you, I won't put it in ever again (Proof: https://mega.nz/file/NcRiHLbB#ly9jT1CPtign_-Di_Eq6ieRYljq-mn09TJm_fKPnEtw ).
Number 4: This phone WILL NOT run android 9, 10, 11 and even if it does, I won't release it because they will be unstable as ****

Na na na nullcode bro we appreciate your work hope u make android soon and amaze to know u are 13 yo and what does mtp means

And pls put touch fix bcz u can't keep it hidden due to some people who doesn't do anything rather than demotivating others

Touch Lag fix:​Warning: This method is extremely dangerous because it has a 70% chance of trashing your Touch Screen. I bricked my touch screen panel after doing this (Display works, but the touch does not function). But after you get the display replaced, everything including TWRP works like a charm. However, there have been some cases where the touch screen does not die, and the users' phones were untouched. So, try at your own risk
Step 1: Flash full stock ROM through ODIN​Step 2: After flashing, setup your phone as quick as possible​Step 3: After doing this, go to the phone app​Step 4: Type *#2663#​[WARNING: NO GOING BACK AFTER YOU DO THIS. DON'T BLAME ME IF SOMETHING HAPPENS]​Step 5: Press TSP Firmware Update (General)​Step 6: DO NOT do anything, until it says "PASS"​Step 7: Now, reboot your device.​(If your touch screen works, WONDERFUL. Now try going to recovery mode to see if the bug is fixed)​​# This is only for if your TWRP touch screen still doesn't work​Step 8: Go back to *#2663#​Step 9: Press "TSP Softkey Update" or something (GUARANTEED DEATH)​Step 10: After it says PASS, remove the battery from the phone and turn it back on​Step 11: Your touchscreen should now be dead. Go to your nearest service center and get it replaced.​​​After doing this, your touch screen inside TWRP will be fully functional. If you want poof, go to this website:
https://mega.nz/file/NcRiHLbB#ly9jT1CPtign_-Di_Eq6ieRYljq-mn09TJm_fKPnEtw

Uniqueshiva said:
Na na na nullcode bro we appreciate your work hope u make android soon and amaze to know u are 13 yo and what does mtp means
Click to expand...
Click to collapse
Touch fix has been put because of your request
MTP means Media Transfer Protocol; it's basically an easier way to transfer files between your phone and your computer

NullCode said:
There are many things wrong with what you said.
Number 1: I don't port custom recoveries. I take my damn time to compile everything from source with my own tree (because ported TWRP laggy).
Number 2: I'm not listening to you. If you don't appreciate what a 13 year old does, I will just cancel my order of a Hard Disk that I bought specifically for compiling Android Oreo (and save my money)
Number 3: I have already fixed the touch problem, I forgot to put it in the thread. But because of people like you, I won't put it in ever again (Proof: https://mega.nz/file/NcRiHLbB#ly9jT1CPtign_-Di_Eq6ieRYljq-mn09TJm_fKPnEtw ).
Number 4: This phone WILL NOT run android 9, 10, 11 and even if it does, I won't release it because they will be unstable as ****
Click to expand...
Click to collapse
Brother why are you getting angry? I just requested. And i did'nt knew that you are a 13 year old. I am sorry if i said any thing wrong.

This thread will be deprecated soon
I am working on making TWRP official
So I will be done with this thread for now
Till the official thread is done, keep downloading TWRP from here
Edit: This thread has been ABANDONED
No more replies/updates to TWRP

Can't wait for your android 8 port

bfox89 said:
Can't wait for your android 8 port
Click to expand...
Click to collapse
you're going to be waiting a long time for something then : P
(might not even work after i buy the storage)

Which version of TWRP should I install for your ViperOS Coral 3.1.1 rom???

shuvo030 said:
Which version of TWRP should I install for your ViperOS Coral 3.1.1 rom???
Click to expand...
Click to collapse
you can use v3.1.1 or my latest twrp (it's still kinda buggy)
https://forum.xda-developers.com/t/...-0-for-samsung-galaxy-j2-2016-j2xlte.4224479/
I recommend you install the MTP beta version in magicalmammal's viperOS thread

MOD ACTION:
Thread closed at the request of the OP.

[ROM][11][TOCO][UNOFFICIAL] crDroid v7.9

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Flashing Instructions:
Pre-installation:
TWRP (Download from here)
FlameGapps FULL
Magisk 23.0 (after first boot) - (Download from here)
First-time installation:
Be sure to be on the latest stock MIUI v12.1.5.0 base
Boot into TWRP or OrangeFox
Flash Rom
Reboot to recovery
Flash Gapps
Format Data
Reboot to system
Update installation:
Boot into TWRP or OrangeFox and flash rom
Reboot to recovery and flash Gapps, Magisk, etc.
Wipe cache
Reboot to system
Sources:
ROM: https://github.com/crdroidandroid
Kernel: VantomKernel
Download:
ROM: OSS Releases
Known issues:
You tell me
Visit the official website @ crDroid.net
crDroid Community Telegram
Donate to help our team pay server costs

Thanks for the roms man

a query, the brightness is always turned up to the maximum when using the fingerprint?

fuathan said:
Thanks for the roms man
Click to expand...
Click to collapse
Welcome

Jcyeici said:
a query, the brightness is always turned up to the maximum when using the fingerprint?
Click to expand...
Click to collapse
That has not been fixed yet

Thank you very much for your great work, I will look forward to the fix of the brightness when using the footprint.
A suggestion
1- they can put the option to hide the notch drop,
2- double tap to lock screen please

i think my storage is encrypted? i cant copy things onto the phone

Thank you @AndroidHQ254. I installed the rom and it runs very smooth. FOD and face unlock works quite well.
I use NikGapps macro from 12/14/20 and it runs very well.
A part of my storage is still encripted, but no idea how to fix. Maybe someone can share his experience.

Bernd K said:
Thank you @AndroidHQ254. I installed the rom and it runs very smooth. FOD and face unlock works quite well.
I use NikGapps macro from 12/14/20 and it runs very well.
A part of my storage is still encripted, but no idea how to fix. Maybe someone can share his experience.
Click to expand...
Click to collapse
More details please on the part of your storage you mean?

hanste (SM-G901F) said:
i think my storage is encrypted? i cant copy things onto the phone
Click to expand...
Click to collapse
Did your format data and reboot reboot recovery?

Jcyeici said:
Thank you very much for your great work, I will look forward to the fix of the brightness when using the footprint.
A suggestion
1- they can put the option to hide the notch drop,
2- double tap to lock screen please
Click to expand...
Click to collapse
DT2W works on FTS screens

AndroidHQ254 said:
More details please on the part of your storage you mean?
Click to expand...
Click to collapse
See added screenshots.
1. error message if you wipe dalvik cache.
2. if you install from twrp recovery from internal storage
3. system is not encrypted only internal storage (sdcard)
My system run very well every think works and I followed your Flashing Instructions .
Maybe it make sense to use the no-vertiy-opt-encrypt script if you install the rom first time?

Works great! Only some issues / wishes:
Sometimes the screen wont wake (if i get a phone call, or unlock with FOD, the screen can sometimes stay all black with no other possibilty than to reboot trough the power menu.
No Home controls on power menu
SELinux is set to permissive. Im using SELinuxModeChanger to automatically set it to enforced every boot so i can use Google Pay.
FOD icon stays on top of first pin lock input on boot.
To flash and root i had to use different recoveries. PBRP for the rom, then TWRP for Magisk.
Other than what is mentioned above, everything seems to work great!

Duplicate

Very interested in this rom. Used a nexus 6p for 2 or 3 years and the last rom I used for it was crdroid rom. It was excellent for that device, but the device showed its age and I had to replace it. I quite like this device and I'm willing to depart from the stock rom. But I'm going to wait for a while until all the bugs are fixed as I use it for work too, so I need it to be stable as possible.

I used that rom the last 4 weeks without any problem. FOD and face unlock works quite well. Any update planned to CrDroid 7.2?

@AndroidHQ254 What is the status of this rom, have there been any updates? Unfortunately, there is no official support for this phone on crdriod site. I'm not sure where to track any progress if there is one.

Bernd K said:
See added screenshots.
1. error message if you wipe dalvik cache.
2. if you install from twrp recovery from internal storage
3. system is not encrypted only internal storage (sdcard)
My system run very well every think works and I followed your Flashing Instructions .
Maybe it make sense to use the no-vertiy-opt-encrypt script if you install the rom first time?
Click to expand...
Click to collapse
I have not had issues with decryption personally

vetle666 said:
Works great! Only some issues / wishes:
Sometimes the screen wont wake (if i get a phone call, or unlock with FOD, the screen can sometimes stay all black with no other possibilty than to reboot trough the power menu.
No Home controls on power menu
SELinux is set to permissive. Im using SELinuxModeChanger to automatically set it to enforced every boot so i can use Google Pay.
FOD icon stays on top of first pin lock input on boot.
To flash and root i had to use different recoveries. PBRP for the rom, then TWRP for Magisk.
Other than what is mentioned above, everything seems to work great!
Click to expand...
Click to collapse
About missing features - That is a rom side thing
Selinux - For now we are permissive
About FOD - I have not encountered that. Plus I do not think you keep rebooting your phone
Include logs for bugs

sage of six paths said:
@AndroidHQ254 What is the status of this rom, have there been any updates? Unfortunately, there is no official support for this phone on crdriod site. I'm not sure where to track any progress if there is one.
Click to expand...
Click to collapse
I work alone so the rom will be updated in due time

Cannot boot to latest version of TWRP on SM-N910G

Hello!
I bought an SM-N910G on ebay recently. The stock rom is a little bit slow and I would like to flash lineage or something else.
When i try to flash the latest version of twrp with odin it passes and shows the splash screen with the logo and version (all normal) but doesnt load and reboots to Android.
Does anyone have any ideas? ive tried most things that i found online but nothing works. the first available version on the twrp website does flash and work but wont flash latest lineage.

del32 said:
Hello!
I bought an SM-N910G on ebay recently. The stock rom is a little bit slow and I would like to flash lineage or something else.
When i try to flash the latest version of twrp with odin it passes and shows the splash screen with the logo and version (all normal) but doesnt load and reboots to Android.
Does anyone have any ideas? ive tried most things that i found online but nothing works. the first available version on the twrp website does flash and work but wont flash latest lineage.
Click to expand...
Click to collapse
Which bootloader is active?
So 3.6.2-9-0 doesn't start?
Tried flashing that .img using old TWRP as well or only .tar with Odin?
What did 3.1.0-0 say when flashing LOS fails?

bmwdroid said:
Which bootloader is active?
So 3.6.2-9-0 doesn't start?
Tried flashing that .img using old TWRP as well or only .tar with Odin?
What did 3.1.0-0 say when flashing LOS fails?
Click to expand...
Click to collapse
sorry i am not sure what you mean by which bootloader is active, is there a way to check this?
Nope, it just loads on the splash screen for a while then boots back to android
I have tried old twrp to flash and odin tar
It said an error about this rom is for *phone* you are using blank or something along those lines.
Afaik 3.5(?) is the only one that can install past oreo roms

del32 said:
sorry i am not sure what you mean by which bootloader is active,
is there a way to check this?
Click to expand...
Click to collapse
That's the one from the stock firmware you came from.
Should be the latest stock possible.
Did you check or can you tell?
del32 said:
Nope, it just loads on the splash screen for a while then boots back to android
I have tried old twrp to flash and odin tar
It said an error about this rom is for *phone* you are using blank or something along those lines.
Click to expand...
Click to collapse
Can you provide a screenshot?
del32 said:
Afaik 3.5(?) is the only one that can install past oreo roms
Click to expand...
Click to collapse
Well mine is on 3.6.1_9-0 and currently on Havoc 4.16 I got from the telegram group.
Has of course the battery drain problem (like all A11 custom versions for this device) when shut down.
With that TWRP I've installed A11 versions of LOS, crDroid and Havoc mulitple times.

bmwdroid said:
That's the one from the stock firmware you came from.
Should be the latest stock possible.
Did you check or can you tell?
Can you provide a screenshot?
Well mine is on 3.6.1_9-0 and currently on Havoc 4.16 I got from the telegram group.
Has of course the battery drain problem (like all A11 custom versions for this device) when shut down.
With that TWRP I've installed A11 versions of LOS, crDroid and Havoc mulitple times.
Click to expand...
Click to collapse
im using the latest 6.0.1 australia optus firmware (im australian and on optus)
there were bootloader files there available there for download but i dont think they worked for me. and also gave me no service in android
I am currently at school, so i will be able to provide a screenshot later
should i try a different stock firmware version/ different country carrier when i get home?

del32 said:
im using the latest 6.0.1 australia optus firmware (im australian and on optus)
Click to expand...
Click to collapse
So that should be ok.
del32 said:
...
should i try a different stock firmware version/ different country carrier when i get home?
Click to expand...
Click to collapse
No idea if that wil do any good or even harm your device.
I know that on some that works but idk about yours.
Perhaps it will help to start from scratch flashing the latest stock if available via samfirm_reborn_3.6.3 (gets it directly from Samsungs servers).

bmwdroid said:
So that should be ok.
No idea if that wil do any good or even harm your device.
I know that on some that works but idk about yours.
Perhaps it will help to start from scratch flashing the latest stock if available via samfirm_reborn_3.6.3 (gets it directly from Samsungs servers).
Click to expand...
Click to collapse
I'll try samfirm_reborn_3.6.3
currently installing the files it needs
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

@del32 which files?
Didn't need any additional ones on my W11 system.
SamFirm_Reborn itself starts directly without installation.
Took it from here:
GitHub - ivanmeler/SamFirm_Reborn
Contribute to ivanmeler/SamFirm_Reborn development by creating an account on GitHub.
github.com

bmwdroid said:
@del32 which files?
Didn't need any additional ones on my W11 system.
SamFirm_Reborn itself starts directly without installation.
Took it from here:
GitHub - ivanmeler/SamFirm_Reborn
Contribute to ivanmeler/SamFirm_Reborn development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
not sure what it needed but i just installed anyways and it all worked
used the same github link
also now in twrp, getting error 1 got a screenshot

del32 said:
not sure what it needed but i just installed anyways and it all worked
used the same github link
also now in twrp, getting error 1 got a screenshot
Click to expand...
Click to collapse
Well your device is trltedt so ROM should fit.
Which TWRP right now?
Did updaing it work?
You did "Format data" after wiping?
Tried with 2nd download of that ROM?
Tried crDroid or Havoc?
Once when I had flashing problems I changed filesystem of several partitions to and fro which helped.
If that all doesn't help I'ld start from scratch.

bmwdroid said:
Well your device is trltedt so ROM should fit.
Which TWRP right now?
Did updaing it work?
You did "Format data" after wiping?
Tried with 2nd download of that ROM?
Tried crDroid or Havoc?
Once when I had flashing problems I changed filesystem of several partitions to and fro which helped.
If that all doesn't help I'ld start from scratch.
Click to expand...
Click to collapse
I am using 3.1.0
I tried a later version and still didnt work, 3.2.2 does not even work!!!
Yes, format data after wiping.
I have tried to redownload
will try havoc right now

@bmwdroid
same issue with havoc, error one and your device is blank
not sure what happened with it

del32 said:
@bmwdroid
same issue with havoc, error one and your device is blank
not sure what happened with it
Click to expand...
Click to collapse
I suppose you definitely need a higher TWRP version but don't understand why you can't flash it.
What does TWRP say when you flash a higher version?

@del32 regarding higher TWRP.
As I understood you you're either flashing 3.5 or higher using Odin and it then TWRP doesn't start afterwards.
Correct?
What happens when you flash high TWRP...img using the older 3.1. TWRP and reboot after that into recovery from TWRP menu?

bmwdroid said:
@del32 regarding higher TWRP.
As I understood you you're either flashing 3.5 or higher using Odin and it then TWRP doesn't start afterwards.
Correct?
What happens when you flash high TWRP...img using the older 3.1. TWRP and reboot after that into recovery from TWRP menu?
Click to expand...
Click to collapse
I just got it to work!!! TWRP 3.5.2 and Havoc are running!!!
i was recording a video to show what i did and how it failed and it just worked
as long as i dont screw around with twrp i should be fine, thank you for your help.
if it wasnt for your response i was just going to give up and not bother.
Your browser is not able to display this video.

@del32 glad I could somewhat help.
May I quote from the film "Galaxy Quest":
Never give up, never surrender
Additional advices: I saw you rebooting after flashing but it's recommended to wipe Cache/Dalvik before the reboot.
It's useful to activate "advanced reboot" so that you can directly reboot to TWRP from the system without button combo.
When you want to get a higher TWRP you can flash it directly within the old one using a .img file.
Worked always for me so it should for you as well.
And you could mark the thread as solved so that others have no need to answer.

bmwdroid said:
@del32 glad I could somewhat help.
May I quote from the film "Galaxy Quest":
Never give up, never surrender
Additional advices: I saw you rebooting after flashing but it's recommended to wipe Cache/Dalvik before the reboot.
It's useful to activate "advanced reboot" so that you can directly reboot to TWRP from the system without button combo.
When you want to get a higher TWRP you can flash it directly within the old one using a .img file.
Worked always for me so it should for you as well.
And you could mark the thread as solved so that others have no need to answer.
Click to expand...
Click to collapse
Thank you very much, also ive never had issue with not wiping after flash but ill keep it in mind and try to remember for later on
I also had advanced reboot on but i didnt have an os on the phone at time of recording
once again, many thanks!!!!!!!
so excited to have Havoc on my phone

del32 said:
Thank you very much, also ive never had issue with not wiping after flash but ill keep it in mind and try to remember for later on
I also had advanced reboot on but i didnt have an os on the phone at time of recording
once again, many thanks!!!!!!!
so excited to have Havoc on my phone
Click to expand...
Click to collapse
Which Havoc version btw?

bmwdroid said:
Which Havoc version btw?
Click to expand...
Click to collapse
4.6, working nicely on android 11
faster than i thought it would be!

@del32 here you find much newer ones: