{
"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:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Unlocked Bootloaders Only!
Nightlies: http://download.cyanogenmod.org/?device=huashan
ChangeLog: http://www.cmxlog.com/12.1/huashan/
Report bugs only if:
- You are using the stock kernel
- You don't any mods/tweaks installed like xposed, etc.
- You searched in the thread for a solution or isn't a know bug.
- You have a log (if apply).
Please don't spam with useless posts here. Talk about Cm12.1 and do questions here: http://forum.xda-developers.com/xperia-sp/help/qa-cyanogenmod-12-1-t3070956
Don't ask for eta's! Be patient!
Screenshots: http://forum.xda-developers.com/devdb/project/?id=9523#screenshots
Thanks to:
-All the Cyanogenmod Team
-uberlaggydarwin
-asanan1
-Adrian DC
-Dark Passenger
XDA:DevDB Information
Cyanogenmod 12.1, ROM for the Sony Xperia SP
Contributors
Mrcl1450
Source Code: https://github.com/CyanogenMod/android_device_sony_huashan
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Version Information
Status: Nightly
Created 2015-04-29
Last Updated 2015-07-24
Instructions:
- Boot into Recovery
- Full Wipe (dalvik, system, data, cache)
- Flash Rom
- Flash Gapps (optional)
- Reboot
Note: You don't need to clean install if you are updating the rom.
Change to F2FS File System: This will delete all you user data!
- Reboot into recovery
- Plug the usb cable to computer
- Use the following adb commands
- adb shell mkfs.f2fs /dev/block/platform/msm_sdcc.1/by-name/Cache
- adb shell mkfs.f2fs /dev/block/platform/msm_sdcc.1/by-name/Userdata
- Reboot
How to do a logcat1º Download Logviewer and extract the files.
2º Connect the phone to pc an check if you have usb debugging active
3º Opening logview.bat it will ask for adb path (adb is in the logview folder)
4º Now you should see the log spamming about sensors. Right click in the message and press "Hide with this tag". Do this for the 5 sensors messages and you should be good to start logging.
5º Now go to the menu adb and click reset logs. After this reproduce the bug.
Example:
Camera app is crashing.
-Click reset log.
-Open camera.
-Disconnect device from pc to stop logging
-Go to file, save, give a name.
6º Send me the log.
All good now.
Thank you:good:
Why did u move the thread
daniyal.dssb said:
Why did u move the thread
Click to expand...
Click to collapse
Because CyanogenMod is considered original development
Can you please explain how to install the 'Alternative Recovery' in detail. I am getting bootloop when it try to install XZDualRecovery.
Steps taken:
1. After installing this ROM, we get simple CM Recovery.
2. Downloaded the installable zip of Xperia SP Dual Recovery. After getting installed, the phone reboots and gets stuck in bootloop.
Can you please help?
anmolkakkar said:
Can you please explain how to install the 'Alternative Recovery' in detail. I am getting bootloop when it try to install XZDualRecovery.
Steps taken:
1. After installing this ROM, we get simple CM Recovery.
2. Downloaded the installable zip of Xperia SP Dual Recovery. After getting installed, the phone reboots and gets stuck in bootloop.
Can you please help?
Click to expand...
Click to collapse
Did you tried the installer method?
CM12.1 for LBL is almost here. Tomorrow we should have the first test build in cm test group. I know I said yesterday but I'm still fixing build errors, sorry.
I will not create a thread until I have sure the rom is working.
Join us here
Mrcl1450 said:
CM12.1 for LBL is almost here. Tomorrow we should have the first test build in cm test group. I know I said yesterday but I'm still fixing build errors, sorry.
I will not create a thread until I have sure the rom is working.
Join us here
Click to expand...
Click to collapse
@Mrcl1450 i think you should tell us how we flash the imgs you stated ! like philz huashan once they are only recoveries and not kernels !
Theliakos said:
@Mrcl1450 i think you should tell us how we flash the imgs you stated ! like philz huashan once they are only recoveries and not kernels !
Click to expand...
Click to collapse
Done
You going to add it here ?
According to the battery log, whenever wifi is turned on and turned off, the battery log says that the wifi is still on despite the wifi switched off via the toggle.
It's a bug?
Mrcl1450 said:
Did you tried the installer method?
Click to expand...
Click to collapse
I had installed using the install.bat file only which comes in the zip package of the recovery. But got stuck in bootloop.
Can anybody help
---------- Post added at 02:32 AM ---------- Previous post was at 02:26 AM ----------
Android_trucker said:
According to the battery log, whenever wifi is turned on and turned off, the battery log says that the wifi is still on despite the wifi switched off via the toggle.
It's a bug?
Click to expand...
Click to collapse
Nope, that is not a bug. If you go to Advanced settings inside the Wifi, you will see a few options.
Firstly, Turn off the 'Scanning Always' option.
Secondly (the reason why Wifi always shows 'ON' under Battery tab), switch 'Keep wifi on during sleep' to 'Never'. Doing this, after sometime when you check back, you'll be able to spot the difference. Wifi module actually is turned off after changing the above mentioned setting.
anmolkakkar said:
I had installed using the install.bat file only which comes in the zip package of the recovery. But got stuck in bootloop.
Can anybody help
---------- Post added at 02:32 AM ---------- Previous post was at 02:26 AM ----------
Nope, that is not a bug. If you go to Advanced settings inside the Wifi, you will see a few options.
Firstly, Turn off the 'Scanning Always' option.
Secondly (the reason why Wifi always shows 'ON' under Battery tab), switch 'Keep wifi on during sleep' to 'Never'. Doing this, after sometime when you check back, you'll be able to spot the difference. Wifi module actually is turned off after changing the above mentioned setting.
Click to expand...
Click to collapse
Fyi I have turned off "scanning always on" for location - however I didn't change the wifi keep as always on when sleeping, will do that and see if it makes a difference.
...I did this ->Flashed stock rom-->root-->installed xzdualreocvery-->flashed -20150425- rom-->reboot--> flashed supersu-->reboot-->lost xzdualrecovery-->intalled it again--> booted to recovery and tried flashing gapps but failed in both twrp and philz touch....and im unable to boot to CWM as CM recovery still exists....how to solve this?.....should i have to flash a cm11 based 4.4.4 rom before flashing your rom?.....which 4.4.4 rom should i download?.... Pls help dev.....
First LBL test build is now up in the test group.
Join us here
backstaber said:
...I did this ->Flashed stock rom-->root-->installed xzdualreocvery-->flashed -20150425- rom-->reboot--> flashed supersu-->reboot-->lost xzdualrecovery-->intalled it again--> booted to recovery and tried flashing gapps but failed in both twrp and philz touch....and im unable to boot to CWM as CM recovery still exists....how to solve this?.....should i have to flash a cm11 based 4.4.4 rom before flashing your rom?.....which 4.4.4 rom should i download?.... Pls help dev.....
Click to expand...
Click to collapse
Try the other way (mentioned at second post) to flash recovery imgs using Rashr then flash GApps
OsGhaly said:
Try the other way (mentioned at second post) to flash recovery imgs using Rashr then flash GApps
Click to expand...
Click to collapse
No flash tangerine via rashr,don't flash rashrs recovery as it changes the fota
kunal9007 said:
No flash tangerine via rashr,don't flash rashrs recovery as it changes the fota
Click to expand...
Click to collapse
And where do i get this tangerine kernel?.....n why is not right to follow the xzdualrecovery method??.....
Related
Since there aren't any (recent) TWRP builds any more for our devices, I built an new image by using the binaries from [NUT]'s XZDualRecovery and the kernel from CyanogenMod 's latest Recovery. Additionally, I added some features and wrote an automated installer, for easy and foolproof installation.
It should work with all custom built ROMs, like Cyanogen, Omni, PAC, etc., but won't work with unmodified stock-kernels.
WARNING: Installing this and especially (mis)using TWRP has the potential to brick your device and/or causing a complete loss of your data! No guarantee, use your common sense! You have been warned..
Automatic installation (easier and safer): Just download the proper the zip-file for your device, boot into the current recovery (e.g. CyanogenMod Recovery from nightly builds, old TWRP or CWM) and install it!
Manual installation (only needed if no recovery is installed yet, or automated installation fails):
download the proper zip-file for your device
open a terminal/console
type (and allow):
Code:
su
goto the download directory, probably:
Code:
cd /sdcard/Download
unzip the installer (or use a file-manger):
Code:
unzip TWRP-*.zip
run (this is the dangerous part, make sure it's written correctly!):
Code:
dd if=twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Special thanks to [NUT] for allowing me to use his binaries and the TeamWin Recovery Project for creating this great tool!
ADB (conditions for access in TWRP): Make sure that you have enabled "Android debugging" and "Root access" for ADB in the Developer options of your ROM. Additionally, you need to connect your tablet once while Android is running and authorise ADB first, in order to be able to use it later in TWRP!
Changelog:
2015-08-23:
based on TWRP 2.8.7.0 and latest XZDualRecovery/CyanogenMod Recovery
added automated zip-installer
added CM's mkfs.f2fs (allows to format/create F2FS partitions)
added support for flashing and backing up recovery images
XDA:DevDB Information
[RECOVERY] TWRP (pollux/pollux_windy), Tool/Utility for the Sony Xperia Tablet Z
Contributors
BlackAfghan, [NUT], Dees_Troy, TeamWin Recovery Project, CyanogenMod
Source Code: https://github.com/TeamWin/Team-Win-Recovery-Project
Version Information
Status: Stable
Current Stable Version: 2.8.7.0
Stable Release Date: 2015-06-22
Created 2015-08-27
Last Updated 2015-08-27
Thank you, looks great with @z31s1g's reworked stock theme!
{
"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"
}
Tapatalked that shiznit.
Thanks! Is working perfectly on my pollux! (and finally we have something dedicated to this model)
Sent from my A0001 using XDA Free mobile app
CyanogenMod Recovery installation works now!
Sorry, I found a bug in the installation procedure, which prevented automated flashing when CyanogenMod Recovery was used..
So if you are still with bare CyanogenMod Recovery, and haven't performed a manual installation yet, please download it again!
Thanks a Million for the fix
BlackAfghan said:
Sorry, I found a bug in the installation procedure, which prevented automated flashing when CyanogenMod Recovery was used..
So if you are still with bare CyanogenMod Recovery, and haven't performed a manual installation yet, please download it again!
Click to expand...
Click to collapse
It works!!! At last i got twrp on my cyanogenmod 12.1. Thanks a lot @BlackAfghan :highfive: :laugh: :highfive:
Keep getting 'error: device unauthorized. Please check the confirmation dialog on your device.' whenever I try to send anything through adb from my computer. I have updated to the latest adb, as older ones seemed to show me the device as being offline when using this version of TWRP.
Any ideas?
georgecarstoiu said:
Keep getting 'error: device unauthorized. Please check the confirmation dialog on your device.' whenever I try to send anything through adb from my computer. I have updated to the latest adb, as older ones seemed to show me the device as being offline when using this version of TWRP.
Any ideas?
Click to expand...
Click to collapse
Did you enable "Android debugging" AND "Root access" for ADB in the Developer options?
BlackAfghan said:
Did you enable "Android debugging" AND "Root access" for ADB in the Developer options?
Click to expand...
Click to collapse
Yes, but this happens while being in TWRP. The first time I am seeing this type of message when trying to push files from my computer to a device that is in recovery mode.
georgecarstoiu said:
Yes, but this happens while being in TWRP. The first time I am seeing this type of message when trying to push files from my computer to a device that is in recovery mode.
Click to expand...
Click to collapse
OK, I solved it. It's no bug, it's a feature..
You have to connect and authorise it first, while the ROM is running. Than it also works in TWRP next time!
I don't know if that behaviour really makes sense, but I guess Google or CyanogenMod intended it that way.. That would also explain why you needed a more recent version of ADB.
This recovery is based on Android 5.1.1, unlike the older TWRP builds which were based on 4.3 or even 4.2.
Maybe the TWRP-team can add that authorization dialogue in a future release.
BlackAfghan said:
OK, I solved it. It's no bug, it's a feature..
You have to connect and authorise it first, while the ROM is running. Than it also works in TWRP next time!
I don't know if that behaviour really makes sense, but I guess Google or CyanogenMod intended it that way.. That would also explain why you needed a more recent version of ADB.
This recovery is based on Android 5.1.1, unlike the older TWRP builds which were based on 4.3 or even 4.2.
Maybe the TWRP-team can add that authorization dialogue in a future release.
Click to expand...
Click to collapse
Thought so too eventually, although it doesn't make perfect sense. It is especially bad when you realize this after you have wiped the system clean in preparation for a clean install of a new ROM. Good that I had a USB stick and OTG adapter cable around, otherwise it would have been impossible.
The more interesting thing is how exactly does TWRP know that a computer is authorized or not and does this information actually survive a wipe of the system before the actual flash of a new one?
edit....
Just signed up to say thank you for this! Excellent work!
Any change this will be updated to the latest version?
Verstuurd vanaf mijn LG-H815 met Tapatalk
*justintime* said:
Any change this will be updated to the latest version?
Verstuurd vanaf mijn LG-H815 met Tapatalk
Click to expand...
Click to collapse
https://dl.twrp.me/pollux_windy/ - Seems you need to be on a MM rom for 3.x versions
scoobyjenkins said:
https://dl.twrp.me/pollux_windy/ - Seems you need to be on a MM rom for 3.x versions
Click to expand...
Click to collapse
No that's not working on Pollux (tablet LTE) when updating in Cyandelta twrp thinks it's a pollux_windy device.
And won't update. Because of Pollux update file.
*justintime* said:
No that's not working on Pollux (tablet LTE) when updating in Cyandelta twrp thinks it's a pollux_windy device.
And won't update. Because of Pollux update file.
Click to expand...
Click to collapse
Why not use a pollux one for pollux https://dl.twrp.me/pollux/ ? 3.0.2.0 works perfectly on CM13.1.
Rootk1t said:
Why not use a pollux one for pollux https://dl.twrp.me/pollux/ ? 3.0.2.0 works perfectly on CM13.1.
Click to expand...
Click to collapse
Haha nice..... Strange thing is on twrp.me Pollux is not mentioned in the device list. That's why I thought it was not available.
Thanks.
Can someone help me? I am unable to flash this recovery.
First i tried to root my Tablet Z (WiFi) with the Kingsroot and SuperSU Me method but i got stuck in a bootloop after the reboot.
But now i have rooted my device but i am unable to flash this recovery to use cm13.
My bootloader is unlocked and i gave the manual installation a try with the android terminal and it said it copied some files but nothing is happening.
I am unable to boot into TWRP
checks0n said:
Can someone help me? I am unable to flash this recovery.
First i tried to root my Tablet Z (WiFi) with the Kingsroot and SuperSU Me method but i got stuck in a bootloop after the reboot.
But now i have rooted my device but i am unable to flash this recovery to use cm13.
My bootloader is unlocked and i gave the manual installation a try with the android terminal and it said it copied some files but nothing is happening.
I am unable to boot into TWRP
Click to expand...
Click to collapse
for cm13 you need to use 3.x.x twrp.img.
Rootk1t said:
for cm13 you need to use 3.x.x twrp.img.
Click to expand...
Click to collapse
No, CM13 works fine with TWRP 2.8.7.0, as long as you don't use Adopted Storage!
Unofficial release -TWRP recovery for the Galaxy A7 2018 - SM-A750F EXYNOS 7885
{
"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"
}
TWRP 3.2.3-0 Released
Aug 6, 2018
TWRP 3.2.3-0 is out now for most currently supported devices.
What's new in 3.2.3-0:
* Fix automatic installing of OTA zips on encrypted devices
* Remove SuperSU from TWRP
* Support both md5 and md5sum file extensions when doing MD5 checking for zip files
Want to get notifications when we release new versions of TWRP? Install the TWRP app and select your device!
We need your help! The bulk of TWRP work is done by a handful of people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
You can track the progress of builds here
Update 25/12/2018
Beta build released.
Current status - (Tested working)
Treble supported
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
NOTE: ON ANDROID 5.1.1> DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
*****INSTALL INSTRUCTIONS:*****
Flash with ODIN in the AP slot.
1. Put your device in DOWNLOAD mode.
(Hold POWER + VOL DOWN + VOL UP)
2. Load the file below into the AP slot, uncheck AUTO-REBOOT and hit start.
twrp_3.2.3-1_a750_251218
3. After flashing and ODIN reports PASS immediately force reboot to recovery. Do NOT let the device boot to the OS.
You should now see TWRP recovery.
4. Flash the RMM bypass zip
https://forum.xda-developers.com/attachment.php?attachmentid=4481843&d=1524258795
NOTE: FAILURE TO FOLLOW THE STEPS ABOVE IMPLICITLY WILL RESULT IN STOCK RECOVERY REPLACING TWRP AT FIRST BOOT.
5. Reboot to TWRP (Do not boot to the OS yet)
*****OREO ROOT INSTRUCTIONS:*****
NOTE: To mount data it is necessary to first *FORMAT* (not wipe) the /DATA partition using the FORMAT DATA button under the wipe options.
PLEASE NOTE THIS WILL DELETE EVERYTHING ON INTERNAL STORAGE AND FACTORY RESET THE DEVICE, SO BACK UP ANYTHING YOU WISH TO KEEP.
Continue with the instructions below to prevent the data partition becoming re-encrypted.
1. To root I suggest downloading and installing the latest Magisk as this is a currently supported project, SuperSu is no longer getting active development.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
2. Copy the Magisk zip to a Micro sd card then install with TWRP.
3. Enjoy your rooted device.
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, Teamwin, @BlackMesa123 for RMM bypass zip.
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
158 views, 20 downloads and not one reply.
Smashing guys. :good:
4. перепрограммируйте обходной zip- архив rmm.можно поподробнее?
Mod edit: English please!
Google translation:
4. reprogram the rmm bypass zip archive. can you be more specific?
Odin shows Failed !! Tried 3 Times ? Had to Flash the Firmare Again.
Help !!
notoriouschyld said:
Odin shows Failed !! Tried 3 Times Had to Flash the Firmare Again.
Help !!
Click to expand...
Click to collapse
Sorry about that, build error on my end. Fixed now.
It will not work on SM-A750FNXXU1ARIC?
Sfuj24 said:
It will not work on SM-A750FNXXU1ARIC?
Click to expand...
Click to collapse
Is that a statement or question?
Hey. Does it work well? I wanted to install myself. but it seems to me that this is not a complete instruction. Does OEM unlock need to be enabled?
powermen27 said:
Hey. Does it work well? I wanted to install myself. but it seems to me that this is not a complete instruction. Does OEM unlock need to be enabled?
Click to expand...
Click to collapse
No matter how complete an instruction is, if you don't bother reading it in the first place it's not going to make any difference.
As clearly posted in the OP:
NOTE: ON ANDROID 5.1.1> DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Click to expand...
Click to collapse
sorry
ashyx said:
Sorry about that, build error on my end. Fixed now.
Click to expand...
Click to collapse
Tried with the new TWRP.img but I'm having a Bootloop on the Samsung Boot Screen.
Help
Take your Time !!
notoriouschyld said:
Tried with the new TWRP.img but I'm having a Bootloop on the Samsung Boot Screen.
Help
Take your Time !!
Click to expand...
Click to collapse
Can you tell me which firmware build number you are running and if possible a screen shot of your device screen while booted to download mode?
Stuck in bootloop after flashing twrp
A750FXXU1ARK7
A7whatever said:
Stuck in bootloop after flashing twrp
A750FXXU1ARK7
Click to expand...
Click to collapse
Can you try this build, it's built with the kernel from the latest source available - A750FNXXU1ARIC.
Be aware OEM unlock must be enabled and you MUST boot to TWRP immediately after flashing with ODIN. Do not boot to the OS.
In TWRP immediately install Magisk.
https://androidfilehost.com/?fid=11410963190603874542
ashyx said:
Can you try this build, it's built with the kernel from the latest source available - A750FNXXU1ARIC.
Be aware OEM unlock must be enabled and you MUST boot to TWRP immediately after flashing with ODIN. Do not boot to the OS.
In TWRP immediately install Magisk.
Click to expand...
Click to collapse
Same bootloop at the Samsung screen
However i use heimdall not odin so I have to unpack the tar file and flash the recovery image. i also use it to flash the stock recovery and it works perfectly
Does using it make a difference?
Edit: my phone is A750FNXXU1ARK2
A750FXXU1ARK7 Was my build number
A7whatever said:
Same bootloop at the Samsung screen
However i use heimdall not odin so I have to unpack the tar file and flash the recovery image. i also use it to flash the stock recovery and it works perfectly
Does using it make a difference?
Edit: my phone is A750FNXXU1ARK2
A750FXXU1ARK7 Was my build number
Click to expand...
Click to collapse
Can you flash the bootloader from A750FNXXU1ARIC and see if it boots twrp?
ashyx said:
Can you flash the bootloader from A750FNXXU1ARIC and see if it boots twrp?
Click to expand...
Click to collapse
Flashed the old sboot.bin however got the same bootloop
A7whatever said:
Flashed the old sboot.bin however got the same bootloop
Click to expand...
Click to collapse
So just to be clear :
Immediately after flashing twrp you are forcing a boot to recovery directly from ODIN?
ashyx said:
So just to be clear :
Immediately after flashing twrp you are forcing a boot to recovery directly from ODIN?
Click to expand...
Click to collapse
Yes
A7whatever said:
Yes
Click to expand...
Click to collapse
Hmm looks like I'll have to take another look at the twrp config or kernel build.
If I pack the kernel into a boot image would you be willing to test if it boots?
{
"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"
}
ArrowOS
Code:
/*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, We will laugh at you.
* It is your fault because you chose to do all the modifications on your device.
* Remember projects like these and the work done on them is a hobby to the
* contributors and the team members, no one is working for you nor is getting paid for it
* have some respect for the work done by them since it is done purely on interest or a hobby
*/
ABOUT
ArrowOS is an Android Open Source Project based Android mobile operating system started with the aim of keeping things simple, clean and neat.
Website: https://arrowos.net
Telegram: Channel
Github: https://github.com/ArrowOS
WHAT WORKS?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Bluetooth
Fingerprint reader
Face unlock
NFC
Lights
Sound/vibration
WHAT DOESN'T WORK?
DT2W
You tell me
Be sure to include a log : check how to
DOWNLOADS
ROM [VANILLA]: https://www.androidfilehost.com/?fid=2981970449027577433
MD5: 3BEBDBD50CEF18A0BC7EE4B91FFB4556
SHA-1: 088D01620FAC2198C41BAAB5C4B7373545CE0F1C
ROM [WITH GAPPS]: https://www.androidfilehost.com/?fid=2981970449027577434
MD5: 2CB7B3426A300BB3CC3975936A50B4A3
SHA-1: 8C8DE3CA640C769FEE44A6BA413C28E70DDC430D
*NOTE: ArrowOS Recovery not currently working properly, included PixelExperience recovery in the meantime, which will work fine*
RECOVERY: https://www.androidfilehost.com/?fid=2981970449027577417
MD5: BFE3114F2A966E03CFD0CF6C0040146B
SHA-1: B14B3102C97C15E3C7C045182489514C0827713F
In case you need it for magisk or any other reason, here's the boot image as well:
BOOT IMAGE: https://www.androidfilehost.com/?fid=2981970449027577435
MD5: F1C858AF7E4037098595016570ACF773
SHA-1: 75B9B0337651D09813FBF494715C93AF307953CA
Read our blog article/post about:
* HOW-TO report a bug
* GAPPS and VANILLA variants
Contributors: @iamsaalim, @kronflux
Source Code: https://github.com/ArrowOS
Device Sources: - https://github.com/kronflux/device_oneplus_billie
Kernel Sources: - https://github.com/danascape/kernel_oneplus_sm6350
ROM OS Version: 11.x Android R
Version Information
Status: STABLE
Release Date: 27-01-2022
Last Updated: 21-03-2022
ROM Firmware Required: OxygenOS 11.x
ROM Kernel: 4.19.125
Please provide instructions on how to install it.
Thank you!
I agree with the person above, there should be installation instructions.
Michael0620 said:
I agree with the person above, there should be installation instructions.
Click to expand...
Click to collapse
I agree as well, I wanted to install this on my phone, but I was running into error's.
art2111 said:
Please provide instructions on how to install it.
Thank you!
Click to expand...
Click to collapse
arrow os installation in nord n10 5G with 100% working method
Just wanted to say that I've been having a hell of a time lately getting my N10 5g back up and running properly everything fails in twrp or otherwise. First install attempt with arrow well see for yourself. Works wonderfully so far.
How long should I be watching the boot screen? I have had problems getting almost anything to install on this phone, I though OP was supposed to be more friendly to tinkerers! That being said, Orangefox Recovery installed like a champ, Arrow seemed to flash without any problem, now I'm going on 30min watching the Arrow icon on the boot screen. Am I stuck in a bootloop? There hasn't been any noticeable restarting of the boot screen animation
***Please ignore my question, after watching the install video I realized I was missing a couple crucial steps. Arrow is installed and working perfect!***
Nds99 said:
How long should I be watching the boot screen? I have had problems getting almost anything to install on this phone, I though OP was supposed to be more friendly to tinkerers! That being said, Orangefox Recovery installed like a champ, Arrow seemed to flash without any problem, now I'm going on 30min watching the Arrow icon on the boot screen. Am I stuck in a bootloop? There hasn't been any noticeable restarting of the boot screen animation
***Please ignore my question, after watching the install video I realized I was missing a couple crucial steps. Arrow is installed and working perfect!***
Click to expand...
Click to collapse
hello,can you tell me how stable is this rom?
BloodMist said:
hello,can you tell me how stable is this rom?
Click to expand...
Click to collapse
Only been running for a couple days but I haven't had one single problem out of it.
Honestly, when I get the time I want to install this ROM since I pretty much ripped everything google related out of pixel experience when I realized that I didn't have to.
I might post the step-by-step instructions I followed
Isabelinc said:
Honestly, when I get the time I want to install this ROM since I pretty much ripped everything google related out of pixel experience when I realized that I didn't have to.
I might post the step-by-step instructions I followed
Click to expand...
Click to collapse
Yes please,instructions will be appreciated
BloodMist said:
Yes please,instructions will be appreciated
Click to expand...
Click to collapse
INSTRUCTIONS (leave a like so that more people see this):
So everything is going well but here is how I did it (Note be sure to have a computer with android-tools (for adb and fastboot):
1. make sure your device is unlocked
2. Download your desired version of the rom (Vanilla or GAPPS, I picked Vanilla), the boot image (for rooting with magisk or flashing if you have another rom previously installed), and the recovery image
3. From within your normal rom, make sure adb debugging is enabled then do "adb reboot bootloader"
4. Flash the recovery image with "fastboot flash recovery recovery.img"
5. Perform a system wipe from within the recovery
6. Go to apply update then choose apply from ADB
7. adb sideload rom.zip
8. Voila
With my phone I had to repeat steps 4-7 again in slot a(or b)* and flash the boot image on both slots*
*Enter fastboot mode and enter fastboot --set-active=(a/b)
*fastboot flash boot.img
Side Note: it can be finicky entering fastboot mode so make sure you reboot to a screen that says one plus fastboot mode or something of the sorts
Isabelinc said:
So everything is going well but here is how I did it (Note be sure to have a computer with android-tools (for adb and fastboot):
1. make sure your device is unlocked
2. Download your desired version of the rom (Vanilla or GAPPS, I picked Vanilla), the boot image (for rooting with magisk or flashing if you have another rom previously installed), and the recovery image
3. From within your normal rom, make sure adb debugging is enabled then do "adb reboot bootloader"
4. Flash the recovery image with "fastboot flash recovery recovery.img"
5. Perform a system wipe from within the recovery
6. Go to apply update then choose apply from ADB
7. adb sideload rom.zip
8. Voila
With my phone I had to repeat steps 4-7 again in slot a(or b)* and flash the boot image on both slots*
*Enter fastboot mode and enter fastboot --set-active=(a/b)
*fastboot flash boot.img
Side Note: it can be finicky entering fastboot mode so make sure you reboot to a screen that says one plus fastboot mode or something of the sorts
Click to expand...
Click to collapse
i think i did same,but after flashing recovery and sideloading the rom,i was getting stock rom!
i forgot -set active command and boot image i think lol
thank you!
just installed and works perfectly!
is there any chance i can have stock camera back though?
BloodMist said:
just installed and works perfectly!
is there any chance i can have stock camera back though?
Click to expand...
Click to collapse
Which stock camera app, the one plus camera app or the google one? On the Vanilla version is came with the one plus camera app which I disabled and replaced with SImple Camera.
For the google one, I bet you could find the apk or on the play store/aurora store.
Also I'm glad I was able to help!
Isabelinc said:
Which stock camera app, the one plus camera app or the google one? On the Vanilla version is came with the one plus camera app which I disabled and replaced with SImple Camera.
For the google one, I bet you could find the apk or on the play store/aurora store.
Also I'm glad I was able to help!
Click to expand...
Click to collapse
i mean the Oneplus stock camera one,it would be better with it,any chance i can have it back?
thank you
BloodMist said:
i mean the Oneplus stock camera one,it would be better with it,any chance i can have it back?
thank you
Click to expand...
Click to collapse
Try looking for apk mirrors online of it and see if they work
Isabelinc said:
Try looking for apk mirrors online of it and see if they work
Click to expand...
Click to collapse
no they don't,they crash immediately without warning right when clicked open
BloodMist said:
no they don't,they crash immediately without warning right when clicked open
Click to expand...
Click to collapse
ah rip, well I guess you're going to have to get used to something different
Isabelinc said:
ah rip, well I guess you're going to have to get used to something different
Click to expand...
Click to collapse
there is no way to get stock one back? even with root?
{
"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"
}
ArrowOS
Code:
/*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, We will laugh at you.
* It is your fault because you chose to do all the modifications on your device.
* Remember projects like these and the work done on them is a hobby to the
* contributors and the team members, no one is working for you nor is getting paid for it
* have some respect for the work done by them since it is done purely on interest or a hobby
*/
ABOUT
ArrowOS is an Android Open Source Project based Android mobile operating system started with the aim of keeping things simple, clean and neat.
Website: https://arrowos.net
Telegram: Channel | TG Portal/Links
Github: https://github.com/ArrowOS
Code Review: review.arrowos.net
E-mail: arrowos.contact
PayPal: Donate to us
Blog: blog.arrowos.net
Checkout more documentation at (maintainership/contributing): Check this out
WHAT WORKS?
Almost everything
WHAT DOESN'T WORK?
4G
You tell me
Be sure to include a log : check how to
DOWNLOADS[/BG]
Blueline
Crosshatch
Only GAPPS variants
Read our blog article/post about:
* HOW-TO report a bug
* GAPPS and VANILLA variants
* Checking build integrity
GPL compliance:
ROM Source- https://github.com/ArrowOS
Device Source- https://github.com/ArrowOS-Devices/android_device_google_crosshatch
Kernel Source- https://github.com/ArrowOS-Devices/android_kernel_google_bluecross
Vendor Source- https://github.com/ArrowOS-Devices/android_vendor_google_bluecross
ROM OS Version: Android 13
ROM Kernel: Linux 4.9.x
ROM Firmware: built-in
Created 2022-08-22
Last Updated 2022-08-22
How to install?
nameless354 said:
How to install?
Click to expand...
Click to collapse
Download the boot.img and flash it.
Reboot to recovery
Wipe data factory reset.
reboot to bootloader
fastboot update rom.zip
4G doesn't work - it's not good.
If I install this since its Android 13 is it gonna lock me on android 13 like its doing to the Pixel 6's? or will i still be able to go back to Android 12 if i wanted to?
crisis_trustee said:
4G doesn't work - it's not good.
Click to expand...
Click to collapse
That's stated in the first post.. please read the entirety of posts before commenting next time. Thank you
Waiting pixel experience android 13
This is cool. Waiting for the 4G to be working
dhaniynhy said:
Waiting pixel experience android 13
Click to expand...
Click to collapse
i also
Stoner242020 said:
If I install this since its Android 13 is it gonna lock me on android 13 like its doing to the Pixel 6's? or will i still be able to go back to Android 12 if i wanted to?
Click to expand...
Click to collapse
no it won't. It doesn't have the bootloader update that Google put it in Android 13 official update. That means if the device had 13 updated and it was only effecting the 6 and up models from what I understand. Either way. I flashed if and No. It's not locked again. This is a OTA zip and I flashed boot img and OTA in TWRP so. Other than the OS not getting data it works nicely. Hopefully it's something simple
Slim2none4u said:
Download the boot.img and flash it.
Reboot to recovery
Wipe data factory reset.
reboot to bootloader
fastboot update rom.zip
Click to expand...
Click to collapse
when i will flash boot img isn't it be a dirty flashing?
on the third step when i will wipe data and do factory reset isn't it remove the OS?
on last step, there is rom zip which i have to update but after downloading files i have only GAPPS zip
please help me in understanding the whole process.
You flash boot image first, fastboot flash boot (nameofbootimg).img. Once that flashes, go into recovery, I just used volume up and down buttons in fastboot and entered that way. Once in recovery, wipe data and factory reset. It'll ask you if you're sure. Select yes. Once that's finished, you have to flash the zip with name ending with gapps. I had trouble flashing mine in fastboot, kept getting an error about android-info.txt not being in the archive, so I just went back into recovery and chose the option to adb side load the zip (I can't remember what it says exactly). Once that finished, I just chose the reboot option, and it loaded up just fine. It took about 5min or so on the boot animation screen before the Welcome screen appeared, but once loaded everything worked great!
mattprice86 said:
You flash boot image first, fastboot flash boot (nameofbootimg).img. Once that flashes, go into recovery, I just used volume up and down buttons in fastboot and entered that way. Once in recovery, wipe data and factory reset. It'll ask you if you're sure. Select yes. Once that's finished, you have to flash the zip with name ending with gapps. I had trouble flashing mine in fastboot, kept getting an error about android-info.txt not being in the archive, so I just went back into recovery and chose the option to adb side load the zip (I can't remember what it says exactly). Once that finished, I just chose the reboot option, and it loaded up just fine. It took about 5min or so on the boot animation screen before the Welcome screen appeared, but once loaded everything worked great!
Click to expand...
Click to collapse
Except 4G right?
thehassanrasool said:
when i will flash boot img isn't it be a dirty flashing?
on the third step when i will wipe data and do factory reset isn't it remove the OS?
on last step, there is rom zip which i have to update but after downloading files i have only GAPPS zip
please help me in understanding the whole process.
Click to expand...
Click to collapse
I just used TWRP formate data then flash the boot img and sideload the zip
mattprice86 said:
You flash boot image first, fastboot flash boot (nameofbootimg).img. Once that flashes, go into recovery, I just used volume up and down buttons in fastboot and entered that way. Once in recovery, wipe data and factory reset. It'll ask you if you're sure. Select yes. Once that's finished, you have to flash the zip with name ending with gapps. I had trouble flashing mine in fastboot, kept getting an error about android-info.txt not being in the archive, so I just went back into recovery and chose the option to adb side load the zip (I can't remember what it says exactly). Once that finished, I just chose the reboot option, and it loaded up just fine. It took about 5min or so on the boot animation screen before the Welcome screen appeared, but once loaded everything worked great!
Click to expand...
Click to collapse
Thank you so much for your help.
JovialQuestion said:
I just used TWRP formate data then flash the boot img and sideload the zip
Click to expand...
Click to collapse
Thank you so much.
Slim2none4u said:
Download the boot.img and flash it.
Reboot to recovery
Wipe data factory reset.
reboot to bootloader
fastboot update rom.zip
Click to expand...
Click to collapse
install from bootloader or recovery?
viynera said:
install from bootloader or recovery?
Click to expand...
Click to collapse
flash it from custom recovery
thehassanrasool said:
flash it from custom recovery
Click to expand...
Click to collapse
There is no custom recovery for a13 for our models as of yet.
Has 4g being fixed yet?
{
"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"
}
/*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, We will laugh at you.
* It is your fault because you chose to do all the modifications on your device.
* Remember projects like these and the work done on them is a hobby to the
* contributors and the team members, no one is working for you nor is getting paid for it
* have some respect for the work done by them since it is done purely on interest or a hobby
*/
BEFORE FLASHING PLEASE READ THE 2ND POST IT CONTAINS CRUCIAL INFORMATION ABOUT FLASHING 12
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.
Website: https://crdroid.net
Downloads
Credits:
@xxseva44
@AShiningRay
@askermk2000
@Stealth1226
@bernardobas
@TheWolfSVK
Rom details
Release Kernel: 4.4.205
Android Version: 12.1
Security Patch: September 5th, 2022
Adreno Driver: 5xx
Selinux: Permissive
Maintainer: ROMSG
WHAT WORKS?
-Audio(input, output)
-Display
-Bluetooth
-Wifi
-FM (unsure)
-Miracast
-usb*(refer to not working section)
-Media playback
-Hardware buttons
-GPS
WHAT DOESN'T WORK?
-Radio (cellular connectivity)
-Using the "Advanced Reboot" menu can cause your phone to become stuck in Rocovery Mode
-Usb does not work with powered docks
-Fingerprint
-Drm
-MTP USB Mode
-Camera
-Dac (Only H870DS has this feature)
-Charging is capped at about 6w
-Double-Tap-to-Wake only works with the Always on Display Enabled
Please don't spam the thread with questions regarding these issues I am aware of them and I along with many others are working hard to fix them. If you have another problem not listed here please include a log with your post.
AND A MESSAGE FROM ONE OF THE TWO KERNEL DEVS, PLEASE REFER TO THIS LINK BEFORE POSTING ABOUT ANY BUGS/ISSUES
TREES (G5/G6/V20):
##################################################################################
##################################################################################
CAF display
GitHub - xxseva44/hardware_qcom-caf_msm8996_display
CAF media
GitHub - PixelExperience/hardware_qcom-caf_msm8996_media
Broadcom FM(Modified)
GitHub - stendro/android_hardware_broadcom_fm
Kernel
GitHub - LGE-G5-G6-V20/msm8996_lge_kernel
Dac interface
GitHub - SGCMarkus/android_hardware_lge
V20 variants
GitHub - xxseva44/LGE_8996-Variants
V20 common
GitHub - xxseva44/LGE_device_v20-common
(G5/G6 Common Folder Only)
GitHub - LGE-G5-G6-V20/Android-device-lge-G5_G6_V20_Variants
LG common
GitHub - xxseva44/LGE_Device_common
Vendor
GitHub - xxseva44/LGE_proprietary_vendor##################################################################################
##################################################################################
Screenshots
AShiningRay said:
Hi there! I'm the "One of the two kernel devs" cited above, mainly developing for the LG V20.
To anyone who wants to beta test this rom on the G6: Please read the main post very carefully, and go to the linked thread's post as well. There's lots of crucial info there.
As an example: You can actually brick your phone if you flash it too much. It appears to be an issue with TWRP and SHRP not supporting 12.1 very well, so have a complete backup outside of the phone before venturing in, as the fastest way to recover is by running "fastboot erase system -w" to reformat almost the whole device, then reflashing recovery through fastboot and later restoring data.
Click to expand...
Click to collapse
This won't work on H872 or any other device with removed fastboot commands. For those I have been using the older root method that involves flashing TWRP to you LAF partition. DO RESEARCH BEFORE TRYING AS YOU CAN IRREVERSIBLY BRICK YOUR PHONE.
[ROOT] H872 (up to and including 20g)
WARNING DO NOT LET YOUR PHONE REBOOT, OR POWER OFF UNTIL I TELL YOU THAT IS WHAT YOU NEED TO DO. If you do, I am not sure what shape your phone will be in. This should go without saying, but you MUST have your bootloader unlocked...
forum.xda-developers.com
Reserved 3
Hi there! I'm the "One of the two kernel devs" cited above, mainly developing for the LG V20.
To anyone who wants to beta test this rom on the G6: Please read the main post very carefully, and go to the linked thread's post as well. There's lots of crucial info there.
As an example: You can actually brick your phone if you flash it too much. It appears to be an issue with TWRP and SHRP not supporting 12.1 very well, so have a complete backup outside of the phone before venturing in, as the fastest way to recover is by running "fastboot erase system -w" to reformat almost the whole device, then reflashing recovery through fastboot and later restoring data.
Performance tweaks to heavily improve responsiveness (root and smartpack kernel manager required)----> https://forum.xda-developers.com/t/beta-rom-unofficial-arrowos-12-1.4488381/post-87502623
AShiningRay said:
Hi there! I'm the "One of the two kernel devs" cited above, mainly developing for the LG V20.
To anyone who wants to beta test this rom on the G6: Please read the main post very carefully, and go to the linked thread's post as well. There's lots of crucial info there.
As an example: You can actually brick your phone if you flash it too much. It appears to be an issue with TWRP and SHRP not supporting 12.1 very well, so have a complete backup outside of the phone before venturing in, as the fastest way to recover is by running "fastboot erase system -w" to reformat almost the whole device, then reflashing recovery through fastboot and later restoring data.
Click to expand...
Click to collapse
This won't work on H872 or any other device with removed fastboot commands. For those I have been using the older root method that involves flashing TWRP to you LAF partition. DO RESEARCH BEFORE TRYING AS YOU CAN IRREVERSIBLY BRICK YOUR PHONE.
[ROOT] H872 (up to and including 20g)
WARNING DO NOT LET YOUR PHONE REBOOT, OR POWER OFF UNTIL I TELL YOU THAT IS WHAT YOU NEED TO DO. If you do, I am not sure what shape your phone will be in. This should go without saying, but you MUST have your bootloader unlocked...
forum.xda-developers.com
October 7th, 2022 - Update
- Failing HALs/Services have been removed reducing log spam and improving performance (before (left) and after (right) results are attached to this post)
- Speed adjustments mentioned here have been merged into the build improving responsiveness
- "Advanced Restart" disabled by default which should help with the Recovery glitch (use the button combo to reboot into recovery)
Awesome! will give it a try. Thanks!
Does encryption work? Haven't seen it mentioned in either the "what works" and "what doesn't work" sections.
Atrate said:
Does encryption work? Haven't seen it mentioned in either the "what works" and "what doesn't work" sections.
Click to expand...
Click to collapse
Maybe, the g5,g6, and v20 used both FDE (Full-Disk Encryption) and FBE (File-Based Encryption), FDE was dropped by AOSP in 12 but FBE should work I just haven't tried.
Hello, What happen if I flash this rom on my H872 G6? what if I flash this rom without stock Download mode in laf partition?
asis9393 said:
Hello, What happen if I flash this rom on my H872 G6? what if I flash this rom without stock Download mode in laf partition?
Click to expand...
Click to collapse
It'll flash like any other rom and having TWRP in laf will allow you to reflash the recovery partition if you run into the recovery bug.
ROMSG said:
It'll flash like any other rom and having TWRP in laf will allow you to reflash the recovery partition if you run into the recovery bug.
Click to expand...
Click to collapse
What happen if it run into the recovery bug?
asis9393 said:
What happen if it run into the recovery bug?
Click to expand...
Click to collapse
One of 2 things, either it refuses to boot into the reocvery partition or when rebooting out of recovery it fails to boot into system and just keeps rebooting into reovery. Both can be fixed by reflashing the recovery partition in laf TWRP
ROMSG said:
One of 2 things, either it refuses to boot into the reocvery partition or when rebooting out of recovery it fails to boot into system and just keeps rebooting into reovery. Both can be fixed by reflashing the recovery partition in laf TWRP
Click to expand...
Click to collapse
So this is what I get. It fails to boot into TWRP using hardware buttons combination. Any tutorial to reflashing the recovery partition in laf TWRP?
asis9393 said:
So this is what I get. It fails to boot into TWRP using hardware buttons combination. Any tutorial to reflashing the recovery partition in laf TWRP?
Click to expand...
Click to collapse
boot into laf and flash a TWRP image to the recovery partition
ROMSG said:
boot into laf and flash a TWRP image to the recovery partition
Click to expand...
Click to collapse
Do you mean laf is Download mode? Seems like my G6 dont have that.
Edit : I did it. How can I flash recovery trough Download mode?
hello , when the rom flashed a Bluetooth has stopped comes up and the phone restarts keeps restarting
Jonsnow1470 said:
hello , when the rom flashed a Bluetooth has stopped comes up and the phone restarts keeps restarting
Click to expand...
Click to collapse
Hi, sorry to hear your having issues, I am aware of this issue and unfortunately haven't had time lately to look into it more