{
"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
Related
{
"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"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface 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.
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your 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.
Supported Models:
Galaxy S10 5G G9770, G977U, G977U1 and G977W.
US/Canada bootloader unlock thread:
here
Download & Guide:
1. Unlock your bootloader.
2. Download S10 5G: beyondxq.
3. Reboot to download mode and flash vbmeta_disabled.tar in AP slot and reboot. Device will reboot to stock recovery mode prompting you to wipe data so wipe data and reboot to download mode again.
4. Put the TWRP tar for your device with Odin in the AP slot and click start.
5. Reboot to recovery via recovery key combo.
6. Disable encryption:
- Go to Advanced > Terminal, type: multidisabler.If vendor complain about free space left on device, will attempt to resize vendor. and it ask to - Run multidisabler again!.- Type: multidisabler again. will see - Finished. when done.7. Go back to Wipe > Format Data > type yes.
8. Reboot to recovery.
9. Flash magisk apk in twrp.
10. Reboot to system, Enjoy.
Note:
Code:
To disable encryption manually:
You need to replace fileencryption=ice with encryptable=ice only in userdata line (maybe rest lines) in vendor/etc/fstab.qcom
To avoid stock recovery restoration manually:
Rename system/recovery-from-boot.p to recovery-from-boot.p.bak
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram group
Bugs:
- Encryption not fully working.
Thanks:
TWRP team
@Mentalmuso for base device tree
@jesec for unlock guide
@ianmacd for multidisabler
Sources:
Kernel tree
Device tree
Changelog:
30.11.2021 - Update to TWRP 3.6.0
- Update multidisabler
27.04.2021 - Update to G977PVPU6FUBH kernel source
31.12.2020 - Update TWRP to 3.5.0
20.11.2020 - Initial Release
You can add the G977P/T to the list as working, confirmed working on my G977T.
Is this still good for android 11?
If you need to download the latest version's twrp, you can do it this link(Download TWRP for beyondx)
G977B supported? Android 11?
Yoonwoo said:
If you need to download the latest version's twrp, you can do it this link(Download TWRP for beyondx)
Click to expand...
Click to collapse
This is the wrong one, this is for exynos, we are dealing with snapdragon here.
razercortex said:
You can add the G977P/T to the list as working, confirmed working on my G977T.
Click to expand...
Click to collapse
Just got my G977P, getting info on how to root Android 11 G977PVPS5EUA4, trying not to brick my device. Any tips on how to do it the safe way? First time trying to root Snapdragon device.
Absolutely! You need to first unlock the bootloader, so go into developer options and enable OEM unlock. After you enable it, reboot to DL mode by volume down + power. Select the power keys that allow for unlock and confirm with the displayed key press. After, follow this thread's guide. Then, download Magisk from the official github, it should be from topjohnwu, it will be in apk format, just rename it to zip. Flash in TWRP and you will be good to go!
razercortex said:
Absolutely! You need to first unlock the bootloader, so go into developer options and enable OEM unlock. After you enable it, reboot to DL mode by volume down + power. Select the power keys that allow for unlock and confirm with the displayed key press. After, follow this thread's guide. Then, download Magisk from the official github, it should be from topjohnwu, it will be in apk format, just rename it to zip. Flash in TWRP and you will be good to go!
Click to expand...
Click to collapse
Thanks! Is it safe to update to latest official software update before installing TWRP?
Yes, it shouldn't matter.
razercortex said:
Yes, it shouldn't matter.
Click to expand...
Click to collapse
Confirmed working on G977P, so fast and easy, thanks for the support!
razercortex said:
You can add the G977P/T to the list as working, confirmed working on my G977T.
Click to expand...
Click to collapse
Man I'm at a loss, I've followed this guide and nothing makes sense in terms of.
I'll get twrp installed just fine but the second i reboot my device it'll either throw me back into twrp or I'll get stuck in "Android is starting" and nothing will happen for hours. I'm on G977p and my bootloader is unlocked
Nexu F said:
Man I'm at a loss, I've followed this guide and nothing makes sense in terms of.
I'll get twrp installed just fine but the second i reboot my device it'll either throw me back into twrp or I'll get stuck in "Android is starting" and nothing will happen for hours. I'm on G977p and my bootloader is unlocked
Click to expand...
Click to collapse
Did you flash vbmeta? Also, starting android for the first time takes a really long time.
razercortex said:
Did you flash vbmeta? Also, starting android for the first time takes a really long time.
Click to expand...
Click to collapse
I did yes. I'll try this doing this guide once more later tonight. Could be quite possible I'm missing a step or didn't pay close attention to one since the others with the same Device on this thread reported a success
razercortex said:
Did you flash vbmeta? Also, starting android for the first time takes a really long time.
Click to expand...
Click to collapse
Any rough idea to how long the starting Android could take before i stop it?
Is the SM-G977N korean model supported
Android 11
Do you know how to access OEM Unlock in development. There is no sign of it on this phone.
Thanks
Any updates for Android 12 G977PVPS8HVE1 for SM-G977P (Sprint)? I can see the official firmware already out, but waiting for working version of TWRP.
Yo, idiot. This guide is for Beyondx not Snapdragon. Misleader.....
{
"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:
/*
* 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 doing this to your device
* 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.
*/
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, root your device and more.
Disclaimer:
- I do not claim this work as my own, this thread was created to have an XDA thread for A71 TWRP. I will try my best to keep it up to date with Ian's work, but can't promise that will remain for ever. If you want the latest TWRP and to be notified as soon as its published, be sure to join the Telegram channel.
- I am not responsible about any damage of any kind that this custom binary may cause.
- Please read the whole main post & related ones before proceed and follow the guide as it is wrote. I will not offer support for any issues that have been already stated.
- Your Knox Warranty Bit will be blown once you flash this or others custom binaries, preventing you to use Knox Features. It can't be resetted in any way, so think twice before flashing this.
- Bugs can be reported here in XDA or via our Telegram Group. Please be more clear as possible and make sure you provide detailed info when reporting bugs (device variant and logcat).
How to Install:
First, you need to unlock the bootloader. Here's how to do it:
- Backup all media before proceeding, this will erase everything in your internal storage including music and photos
- Go to developer settings and enable [OEM Unlock]
- Reboot to download mode
- When prompted, press and hold VOL + to enter bootloader unlock mode
- Press VOL + to confirm you want to unlock bootloader, this will wipe your data
- If you think the bootloader is fully unlocked, it is actually not! Samsung introduced VaultKeeper, meaning the bootloader will still reject any unofficial partitions before VaultKeeper explicitly allows it.
- Go through the initial setup. Skip through all the steps since data will be wiped again later when we flash TWRP and magisk
- Enable developer options, and confirm that the OEM unlocking option exists and is grayed out. This means the VaultKeeper service has unleashed the bootloader. This step is MANDATORY
- Your bootloader now accepts unofficial images in download mode.
After finally unlocking the bootloader, proceed with installing TWRP (tar) with Odin:
- Boot to download mode and load TWRP tar file and VBMeta disabler tar file in AP and BL of Odin, doesn't matter which goes where
- Disable [Auto Reboot] in Odin
- Flash
- Force a reboot by pressing VOL+, VOL - and POWER buttons at the same time
- After the screen goes black, IMMEDIATELY let go of all buttons and IMMEDIATELY press and hold VOL+ and POWER button at the same time to boot to TWRP
- After booting to TWRP successfully, go to WIPE in TWRP
- At the bottom, you should see an option to FORMAT DATA. After you select it, you will be asked to type "yes" in your keyboard. If you do not see this, you probably selected the wrong option.
- After formatting data, flash the Multidisabler zip with TWRP. This is done to avoid future bootloops.
(Optional) Flash magisk.zip to root (google where to find it)
- Reboot to system
- Wait patiently for the device to boot for the first time
How to flash TWRP (img):
- Reboot to recovery
- Select Install
- Select Install Image and search for the TWRP img file
- Flash as recovery
- Reboot to recovery
- Done
Downloads:
twrp-a71-3.5.1_10-A11_2b1_ianmacd.img
twrp-a71-3.5.1_10-A11_2b1_ianmacd.tar
Multidisabler zip by Ianmacd
VBMeta disabler
Source Code: https://github.com/ianmacd/twrp_a71
Source Code: https://github.com/ianmacd/a71
Change log:
17/03/21: Release for Android 11 BL
Credits:
- Samsung for kernel source code
- TeamWin for their awesome recovery
- @ianmacd for compiling, updating, and maintaining for A71
reserved 1
reserved 2
Sorry for the delay, this TWRP should work perfectly with Android 11 BL
Thanks! However, it kept encrypting after booting to Recovery? Already format and flash Multidisabler zip by Ianmacd.
After several tries, it did not encrpt any more. It really beats me. Anyway, great job. Thanks!
@ShaDisNX255 have you came across config files for Link to Windows / Your Phone Companion, namely something to do with features enabled ?
Now that A71 got OneUI 3.1 (A11) I was wondering if there is a way to enable multi-apps in Link to Windows.
I also wonder if this "multi-apps" new feature in A11 needs to be enabled in OneUI too (or maybe there isn't a Link to Windows special toggle at all, only system one).
All I know is that only the high tier Samsung phones has multi-apps streaming to Windows, like S21, Note20, Fold and Z Flip but also last gen S20 and Note10.
Would like to hear your thoughts on this.
EDIT: the backbone of the feature is this: https://www.xda-developers.com/android-q-splitscreen-multitasking-multi-resume/
donkeyman1234 said:
Thanks! However, it kept encrypting after booting to Recovery? Already format and flash Multidisabler zip by Ianmacd.
After several tries, it did not encrpt any more. It really beats me. Anyway, great job. Thanks!
Click to expand...
Click to collapse
Very strange. Hopefully your issue is fixed, I'll try and see what could be wrong. Thanks for the input.
ban.codrut said:
@ShaDisNX255 have you came across config files for Link to Windows / Your Phone Companion, namely something to do with features enabled ?
Now that A71 got OneUI 3.1 (A11) I was wondering if there is a way to enable multi-apps in Link to Windows.
I also wonder if this "multi-apps" new feature in A11 needs to be enabled in OneUI too (or maybe there isn't a Link to Windows special toggle at all, only system one).
All I know is that only the high tier Samsung phones has multi-apps streaming to Windows, like S21, Note20, Fold and Z Flip but also last gen S20 and Note10.
Would like to hear your thoughts on this.
EDIT: the backbone of the feature is this: https://www.xda-developers.com/android-q-splitscreen-multitasking-multi-resume/
Click to expand...
Click to collapse
I haven't used the Link to Windows feature, I don't really have a good understanding of what you mean.
ShaDisNX255 said:
Very strange. Hopefully your issue is fixed, I'll try and see what could be wrong. Thanks for the input.
Click to expand...
Click to collapse
I took a shot of log.
I'm running stock Android 11 and I've tried to make a backup with TWRP but failed with this message:
Can create '/data/media/o/TWRP/ folder (required key not available).
Failed to make backup folder.
It means that I'm encrypted, right ??. If I'm correct, should I format data and flash the new multidisabler ?
EDIT: on A10 it was unencrypted, flashing A11 encrypted it again?
viktor92 said:
I'm running stock Android 11 and I've tried to make a backup with TWRP but failed with this message:
Can create '/data/media/o/TWRP/ folder (required key not available).
Failed to make backup folder.
It means that I'm encrypted, right ??. If I'm correct, should I format data and flash the new multidisabler ?
EDIT: on A10 it was unencrypted, flashing A11 encrypted it again?
Click to expand...
Click to collapse
Yes, you must format and flash multidisabler.
Question, i went though the bootloader unlock but the option don't appear grey out on the dev menu, what should i do to really unlock it?
Edit:
Ok i manage to do it but idk how to reboot in to TWRP, is it vol+ and power? it isn't working
Pupet_Master said:
Question, i went though the bootloader unlock but the option don't appear grey out on the dev menu, what should i do to really unlock it?
Edit:
Ok i manage to do it but idk how to reboot in to TWRP, is it vol+ and power? it isn't working
Click to expand...
Click to collapse
Android 11 changes the way it works
Now, it is necessary to be connected to a PC to boot to recovery with that combination of keys.
ShaDisNX255 said:
Android 11 changes the way it works
Now, it is necessary to be connected to a PC to boot to recovery with that combination of keys.
Click to expand...
Click to collapse
Thanks Friend
I have a Samsung A71 Anroid 11 and I'm also trying to root it. Everything you have written I understand, up to this point:
"- After formatting data, flash the Multidisabler zip with TWRP. This is done to avoid future bootloops."
I answer "Yes" and than at the next screen I only can choose between Back or Reboot. How must I flash at this stage the Multidisabler?
Must I go back to the TWRP main menue to the Point "install"?
Greetings from Cologne
Germany
Norbert
Nobby52 said:
I have a Samsung A71 Anroid 11 and I'm also trying to root it. Everything you have written I understand, up to this point:
"- After formatting data, flash the Multidisabler zip with TWRP. This is done to avoid future bootloops."
I answer "Yes" and than at the next screen I only can choose between Back or Reboot. How must I flash at this stage the Multidisabler?
Must I go back to the TWRP main menue to the Point "install"?
Greetings from Cologne
Germany
Norbert
Click to expand...
Click to collapse
Yes, you have to go back to the main menu
Thank you, I'll try it again.
Norbert
Unfortunately, this method doesn't work for me. I've tried rooting three times. It went through every time without any errors. The device was not rooted afterwards. The smartphone then triggered a reset every few minutes when it was operated. What can I do?
Greetings from Cologne
Norbert
Nobby52 said:
Unfortunately, this method doesn't work for me. I've tried rooting three times. It went through every time without any errors. The device was not rooted afterwards. The smartphone then triggered a reset every few minutes when it was operated. What can I do?
Greetings from Cologne
Norbert
Click to expand...
Click to collapse
What ROM are you trying to root?
Are you Rooting with Magisk or Super SU? Do you install SUper SU App or Magisk Manager after?
About the reset, did you flash the multiboot disabler after flash the root zip file?
I root the original Samsung Stock Rom. "A715FXXU3BUB5_A715FOXM3BUB6_DBT". I followed the instructions here exactly.
First unroot and debug mode
1.) download mode
2.) with Odin TWRP + VBMeta-Disabler
3.) TWRP started, wipe, then yes, then back to install, Multidisabler.zip flashed.
4.) restarted
That was it
I don't have a Super_SU or Magisk installed
greeting
Norbert
{
"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"
}
PixelExperience for OnePlus Nord N10 5G [billie]
What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 11
Code:
/* 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.
*/
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Bluetooth
Fingerprint reader
Face unlock
NFC
Lights
Sound/vibration
Known issues
DT2W
You tell me!
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
ROM: https://www.androidfilehost.com/?fid=2981970449027577418
MD5: 53C4B515DDCC722A59510C161209F916
SHA-1: CCA686001DA7959C0E953D1948FB3626CF66987F
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=2981970449027577416
MD5: CFE13188A29FD82AD8134DA706D06730
SHA-1: FC023DEC26372B2F9E8EEF054635561092DCF2EF
INSTRUCTIONS
1. Download the ROM and Recovery image
2. Boot into bootloader/fastboot mode
* adb reboot bootloader
3. Flash the Recovery image
* fastboot flash recovery recovery.img
4. Boot into Recovery
* fastboot reboot-recovery
5. Perform a Factory Reset/Wipe in Recovery
6. Go to Apply Update and choose Apply from ADB
7. Sideload the ROM
* adb sideload rom.zip
Reboot and voila!
Translation
Help with project translation
Stay tuned
Follow us on Telegram
Contributors @iamsaalim, @kronflux, @billaids
ROM source: https://github.com/PixelExperience
Device sources: https://github.com/kronflux/device_oneplus_billie
Kernel source: https://github.com/danascape/kernel_oneplus_billie
ROM OS Version: 11.x
ROM Kernel: 4.19.125
ROM Firmware Required: OxygenOS 11.x
Based On: AOSP
Version Information
Status: Community Beta
Created 22-01-2022
Last Updated 22-03-2022
Is this an update, and if so do you update through the recovery. Also does updating reset userdata
For some reason adb sideload stops at 47% and I see step 2/2 on my screen. With no indication of it's complete or not. Upon backing out it immediately says complete but doesn't boot, and instead boots into the bootloader
dieudeglace said:
For some reason adb sideload stops at 47% and I see step 2/2 on my screen. With no indication of it's complete or not. Upon backing out it immediately says complete but doesn't boot, and instead boots into the bootloader
Click to expand...
Click to collapse
If it gets to 47% it's finished. (It happens with every recovery and rom for some reason)
It goes right to the bootloader because you have to flash both slots with the rom.
You're halfway there basically.
Use fastboot to switch slots and sideload PE again.
You should be all good to go, just make sure to factory reset after sideloading.
CodeNotSoGenious said:
Is this an update, and if so do you update through the recovery. Also does updating reset userdata
Click to expand...
Click to collapse
It is not an update, you can't go from the previous version of pixel experience to this one.
Unlike the previous version which requires you being on Android 10 before installing pixel experience, you've gotta be on Android 11.
You'd lose user data by having to go back to stock for the Android 11 update (again when unlocking bootloader, and again if you choose to format your device after installing the rom)
It's a bit of time, but the effort is definitely worth it if you have somewhere to store your files momentarily.
ninjasinabag said:
If it gets to 47% it's finished. (It happens with every recovery and rom for some reason)
It goes right to the bootloader because you have to flash both slots with the rom.
You're halfway there basically.
Use fastboot to switch slots and sideload PE again.
You should be all good to go, just make sure to factory reset after sideloading.
Click to expand...
Click to collapse
you are a god send. i thought i was doing something entirely wrong lol
yeah works like a charm now. Deeply appreciate this. Im still new to all this and accidentally bricked my tcl 20 pro 5g a little while ago.
dieudeglace said:
yeah works like a charm now. Deeply appreciate this. Im still new to all this and accidentally bricked my tcl 20 pro 5g a little while ago.
Click to expand...
Click to collapse
Glad to hear you've got it up and running.
Yeah, it's always a coin toss when flashing anymore. Almost always worth it once you get those kinks out.
ninjasinabag said:
It is not an update, you can't go from the previous version of pixel experience to this one.
Unlike the previous version which requires you being on Android 10 before installing pixel experience, you've gotta be on Android 11.
You'd lose user data by having to go back to stock for the Android 11 update (again when unlocking bootloader, and again if you choose to format your device after installing the rom)
It's a bit of time, but the effort is definitely worth it if you have somewhere to store your files momentarily.
Click to expand...
Click to collapse
Thanks, I'll put in some time to flash this!
What's different from the last pixel experience ROM?
CodeNotSoGenious said:
What's different from the last pixel experience ROM?
Click to expand...
Click to collapse
Updated kernel and built officially around Android 11 instead of 10.
ninjasinabag said:
Updated kernel and built officially around Android 11 instead of 10.
Click to expand...
Click to collapse
Appreciate it
Seems I have had one issue so far. Using Android auto and receiving/making calls with people ends up with them not being able to hear me.
dieudeglace said:
Seems I have had one issue so far. Using Android auto and receiving/making calls with people ends up with them not being able to hear me.
Click to expand...
Click to collapse
I'll try and test this myself soon, I haven't been driving much lately so it's a tough thing to test
Make sure you try re-pairing your phone with the vehicle. and by that I mean, entirely delete it from your vehicle as well as delete the pairing in the phone itself. set it up as if it's a new device, and see if that makes a difference
Will try it later to see if it works, otherwise this is a very solid build so thank you for making this!
Now I may habve missed this through the pages but I am getting
"Eackage is for product OnePlusN10 but expected OnePlusNordN10" one device and on laptop cmd it says "failed to read command" is that because I need to flash both slots or is this soem other error?
brncgreen said:
Now I may habve missed this through the pages but I am getting
"Eackage is for product OnePlusN10 but expected OnePlusNordN10" one device and on laptop cmd it says "failed to read command" is that because I need to flash both slots or is this soem other error?
Click to expand...
Click to collapse
Do you happen to be using the metro version of the Nord n10? (Or TMobile since they're basically the same phone.)
ninjasinabag said:
Do you happen to be using the metro version of the Nord n10? (Or TMobile since they're basically the same phone.)
Click to expand...
Click to collapse
I am using t mobile. How ever I did figure it out.... It was ignorant for me to do this but... I didnt realize how PE was suppose to look and when it booted up for the first time I thought it was just stock oneplus OOS.... This time i flashed both a/b and when I booted it was the same thing so I was doing it right all along just failed to realize that it isnt really any different than stock at least from the cosmetic.
Trying to install this but when I get to adb sideload rom.zip (I did rename it after several failed attempts with it's original name). I keep getting
E:\Profile\Desktop>adb sideload rom.zip
loading: 'rom.zip'
* cannot read 'rom.zip' *
Any suggestions?
happened to me. I tried to install over a custom rom that had os11 on it, but it did not like it and kept giving me the same "cannot read" error. I MsM back to stock rom which for me was version 10 at which point I needed to update os to 11 twice to make sure that 11 was on both partitions. After that I unlocked, flashed recovery, reboot recovery, format data, adb sideload rom, then adb sideload partition fix, then reboot to bootloader, fastboot--set-active=a( or b depending on what partition you were on. you want to be on the other partition), boot back into recovery, adb sideload rom again for the different partition, format data again, then reboot. works fine for me.
{
"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?