Related
Update March 23, 2019: I'd like to apologize to everyone. It looks like I am not going to be able to actively keep this thread updated like I used to. I have had too much going on at home an work and it doesn't look like it's going to settle down any time soon. The thread is still usable so I will leave it open for discussion.
Team Win Recovery Project
Code:
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, fires, rigged elections,
* specks of dusk sitting on cursors, cursors that mock you--waiting for cursor
* revenge, thermonuclear war, or you getting fired because the alarms failed
* and you could not call in.
*
* Please ensure you have an advanced understanding of this device before
* flashing it! YOU are choosing to make these modifications or your own free will.
This is the first official build of TWRP for the Motorola Moto G6 (ALI)!
Notes:
Decryption is finicky: Currently only vold decryption is working. This image must be flashed to properly decrypt. Updates may cause issues with decryption.
If you format data (Not just factory reset) after decrypting you must reboot into recovery and format again.
If you are unable to unlock your phone after restoring a data backup that had a lock code on it (and TWRP is able to decrypt using default password) you'll need remove the '/data/system/locksettings.db' while in TWRP. After that you should be able to reboot into Android and set a lock code. If you cannot then please use this thread as a guide and try again. Bascially you just delete more, however I was able to boot after just deleting the one file with a pattern set (Maybe random luck, maybe not)
If you have any other issues please let me know and I'll work toward fixing them! AS ALWAYS, IT'S YOUR RESPONSIBILITY IF YOU USE THIS SOFTWARE
Known Issues:
I have just noticed some odd behaviour if you input an incorrect decryption password/pattern/etc in twrp. It can cause an issue while entering the lockscreen password/pattern/etc while booting up. Under normal circumstances these two are the same, hence why restoring can also cause a similar issue, though that one is easily fixable. The onIy way to clear the decryption pass is to format. I am unsure at the moment what is causing this, but clearly it has something to do with the decryption. At this time I'd say it'd be best to remove your current lockscreen password/pattern/etc before booting into twrp to avoid this issue. A possible work-around would be to reboot to twrp, enter the correct password, back up your data, format (reboot to twrp and format again), then restore your backup (and possibly need to delete the '/data/system/locksettings.db' file. Your data would still exist that way. I am going to work to fix this asap and maybe see if I can get another build without decryption made for official use for now.
Flashing zips that require BusyBox will not work with the official version right now. I've built an unofficial version to use until a new official build is triggered.
ALI's Changelog: Post #2
Download: twrp.me Download
Unofficial Download (updated more often): twrp-v3.2.3-unofficial-ali-20181110.img
Simple Installation Method:
1) boot to fastboot
2) fastboot flash recovery <twrp-image-name>.img
Other instructions are available on the Official download page. It's up to you to backup your factory recovery first if you wish to have a backup: Post #3
Thanks to the TWRP team and everyone who has put in effort to make these things possible!
@Jleeblanch - Wonderful advice and guidance
@Dadud - testing
@ Everyone at github
@ XDA and the people who provided TWRP compiling threads
If I've forgotten someone who you think needs mention please let me know!
* This page will continue to be edited as more information comes
XDA:DevDB Information
[RECOVERY][OFFICIAL] TWRP v3.2.3 [2018-10-20], Tool/Utility for the Moto G6
Contributors
dejello
Source Code: [url]https://github.com/TeamWin/android_device_motorola_ali[/URL]
Version Information
Status: Stable
Current Stable Version: 3.2.3-0
Stable Release Date: 2018-10-20
Current Beta Version: 3.2.3 Unofficial
Beta Release Date: 2018-11-10
Created 2018-10-21
Last Updated 2018-11-10
Changelogs
TWRP Changelog:
v3.2.3 changelog
ALI's Official Changelog:
v3.2.3-0 (Oct 20, 2018)
- N/A, first build!
ALI's Temp. Unofficial Changelog:
v3.2.3 (Oct 31, 2018) (This log will get moved to official when it gets updated with these changes)
- Stop using toybox (Use busybox!)
- Added vendor image mount point
Factory Backup Information
It's up to you to determine if you want/need a factory recovery image backup before flashing:
To boot twrp first (it will fail decryption, don't worry about it) just do the following while replacing <twrp> with the actual file name.
Code:
fastboot boot <twrp>.img
Then to back up your stock/factory recovery while booted in TWRP do the following.
Code:
adb pull /dev/block/bootdevice/by-name/recovery stockrecovery.img
First [emoji14]
For real tho, nice work and congrats [emoji41]
Woot Woot! Congrats bro?
Lockscreen after restore
Hello, this method (delete lockscreen) after restore backup works for me to ?
Decryption doesn't work for me. XT1925-6 Ali
giant22000 said:
Decryption doesn't work for me. XT1925-6 Ali
Click to expand...
Click to collapse
I'll need more details if I'm to look into it. I also have an xt1925-6. Any logs? What version software are you running? What kind of lock screen are you using (pin, password, pattern, none, etc)? What happened from booting twrp up to the point of decryption failure? The more information I have the better chance I have at rectifying the issue.
[EDIT] I just did some messing around and came across something I hadn't seen before:
I have just noticed some odd behaviour if you input an incorrect decryption password/pattern/etc in twrp. It can cause an issue while entering the lockscreen password/pattern/etc while booting up. Under normal circumstances these two are the same, hence why restoring can also cause a similar issue, though that one is easily fixable. The onIy way to clear the decryption pass is to format. I am unsure at the moment what is causing this, but clearly it has something to do with the decryption. At this time I'd say it'd be best to remove your current lockscreen password/pattern/etc before booting into twrp to avoid this issue. A possible work-around would be to reboot to twrp, enter the correct password, back up your data, format (reboot to twrp and format again), then restore your backup (and possibly need to delete the '/data/system/locksettings.db' file. Your data would still exist that way. I am going to work to fix this asap and maybe see if I can get another build without decryption made for official use for now.
I have added this to the first post.
Damn thanks !
Hi. First thank for the contribution.
I would like to know if someone has the stock twrp, modeled 1925-1. When I modified my stock twrp, I made a back up, but I lost it.
I would like to update my security patch, but I can not because it has modified the twrp.
aaleej0 said:
Hi. First thank for the contribution.
I would like to know if someone has the stock twrp, modeled 1925-1. When I modified my stock twrp, I made a back up, but I lost it.
I would like to update my security patch, but I can not because it has modified the twrp.
Click to expand...
Click to collapse
So I guess I will be the one to say it. I'm giving you one warning about this. It's against forum rules to post on multiple threads with the same subject. I've answered your question on the Ali stock firmware thread also. Please read guides and threads instead of skimming through them because it's been answered multiple times. Next time you do this and post the same thing on multiple threads I will be the one reporting you. Have a good day.
I have added an unofficial build tonight (Oct/31/2018) to fix an issue flashing zips that need busybox (Resurrected Kernel, etc) versus toybox. It also adds a 'vendor image' mount point for use in backups and flashing. Once official gets updated this unofficial build will be removed.
Hello, could you consider supporting the Moto g 6 play xt922-4 I'm welling to help out with logs or anyfile if needed.
jglm4u said:
Hello, could you consider supporting the Moto g 6 play xt922-4 I'm welling to help out with logs or anyfile if needed.
Click to expand...
Click to collapse
There are certain reasons there is no official twrp for our moto g6 play devices yet. Is there issue your having?. Dejello supports the regular g6 and for all intensive purposes I've being doing support for the g6 play.
jglm4u said:
Hello, could you consider supporting the Moto g 6 play xt922-4 I'm welling to help out with logs or anyfile if needed.
Click to expand...
Click to collapse
ninjakira said:
There are certain reasons there is no official twrp for our moto g6 play devices yet. Is there issue your having?. Dejello supports the regular g6 and for all intensive purposes I've being doing support for the g6 play.
Click to expand...
Click to collapse
I don't have access (well, sort of but not really) to a g6 play. My son has one, but it's not unlocked or anything and I won't experiment on his phone without having everything backed up.... Besides, getting the damn thing away from him for extended periods when he isn't in trouble would be something.... I thing it's glued to his face or something.
I am also not up to date on any issues or reasons why twrp isn't official for the g6 play. Be aware that even this version for the g6 has some issues (workarounds are available for everything so you won't lose anything) still.
I've been debating looking into it, but haven't yet for reasons above.
dejello said:
I don't have access (well, sort of but not really) to a g6 play. My son has one, but it's not unlocked or anything and I won't experiment on his phone without having everything backed up.... Besides, getting the damn thing away from him for extended periods when he isn't in trouble would be something.... I thing it's glued to his face or something.
I am also not up to date on any issues or reasons why twrp isn't official for the g6 play. Be aware that even this version for the g6 has some issues (workarounds are available for everything so you won't lose anything) still.
I've been debating looking into it, but haven't yet for reasons above.
Click to expand...
Click to collapse
I just had a good laugh about your son's g6 play being glued to his face ??I could definitely say I don't look at or use my phone as much as the kids now a days and I'm 27 lol I worked ina mall so I seen that alot lmao and what all would you need from someone to attempt an official twrp for it? Ill do my best to provide you with what's needed. The patched twrp for the g6 play should be a good start. I would have already started on it myself but i am not able to get it going because i don't trust my laptop (it came with Vista) and it likes to randomly reboot and all this marvelous stuff lol
ninjakira said:
I just had a good laugh about your son's g6 play being glued to his face ??I could definitely say I don't look at or use my phone as much as the kids now a days and I'm 27 lol I worked ina mall so I seen that alot lmao and what all would you need from someone to attempt an official twrp for it? Ill do my best to provide you with what's needed. The patched twrp for the g6 play should be a good start. I would have already started on it myself but i am not able to get it going because i don't trust my laptop (it came with Vista) and it likes to randomly reboot and all this marvelous stuff lol
Click to expand...
Click to collapse
When I get a chance I can take a look at some things. But looking at github I do see at least one device tree being worked on for jeter
ninjakira said:
I just had a good laugh about your son's g6 play being glued to his face [emoji23][emoji23]I could definitely say I don't look at or use my phone as much as the kids now a days and I'm 27 lol I worked ina mall so I seen that alot lmao and what all would you need from someone to attempt an official twrp for it? Ill do my best to provide you with what's needed. The patched twrp for the g6 play should be a good start. I would have already started on it myself but i am not able to get it going because i don't trust my laptop (it came with Vista) and it likes to randomly reboot and all this marvelous stuff lol
Click to expand...
Click to collapse
I wouldn't trust Windows either. Personally, I'd wipe Windows right off it and run Linux. Linux would breathe new life into a laptop that came with Vista lol.
Jleeblanch said:
I wouldn't trust Windows either. Personally, I'd wipe Windows right off it and run Linux. Linux would breathe new life into a laptop that came with Vista lol.
Click to expand...
Click to collapse
I do have it on dual boot with Ubuntu 18.10 it's Just the the random rebooting is persistent still but yeah I personally use use linux distos over Windows lol. My next paycheck I'm having our local computer store called microcenter help me out with a new laptop at least lol
dejello said:
When I get a chance I can take a look at some things. But looking at github I do see at least one device tree being worked on for jeter
Click to expand...
Click to collapse
I'm not able to send the screenshot of termux so here they are. Recovery is 16 mb
Good afternoon everyone.
I got interested in putting a custom rom on my Galaxy Note 8 I have laying around (Current Daily driver has been upgraded to a Note 20 Ultra so I have no hurry to fix this issue.)
I followed the steps from one of the forum guides and installed TWRP, the first thing I noticed was that my Note 8 had 2 System directories while this is supossed to be a A only model. (Which struck me as odd.) After installing a android 11 Rom (A Only) I was stuck on the boot screen not loading any further. I found this logical as Android 11 is not really supported as of yet on this model.
I then decided to grab Havoc OS seeing as that was a stable version that should run properly i've seen people on Youtube install it on their S8's without a hitch. After installing this the way the guide told me I got stuck in a boot loop. (Also used an A only ROM) My final attempt will be downloading an A/B ROM and see if that works (Which i genuinly doubt.) but will update this post when that's finished.
On the post I also have added a screenshot of what I see when trying to install an Image. My question to you guys is, does this phone have a A/B configuration after all or am I doing something wrong?
Edit: AB was also not the solution.
After rummaging around a bit more with the phone I found out that i was using an extremely out of date version of the Pie Vendor. I looked at download by Version number instead of by date. Reinstalled Havoc, installed pie vendor.
Now the phone reboots into downloading mode. It's been this way around 10 minutes now will post an update in about an hour or so of leaving it in that state.
QuirkyTechGuy said:
After rummaging around a bit more with the phone I found out that i was using an extremely out of date version of the Pie Vendor. I looked at download by Version number instead of by date. Reinstalled Havoc, installed pie vendor.
Now the phone reboots into downloading mode. It's been this way around 10 minutes now will post an update in about an hour or so of leaving it in that state.
Click to expand...
Click to collapse
Odd. Truly. It could be due to the first install of GSI version. Here's what I suggest.
I hope u have a back up of your old rom, if so, flash it back. If not, check your twrp version. Update it to latest. Flash a non gsi rom. Boot the phone. If it boots and you have it running, then flash a gsi rom .
maxed4901 said:
Odd. Truly. It could be due to the first install of GSI version. Here's what I suggest.
I hope u have a back up of your old rom, if so, flash it back. If not, check your twrp version. Update it to latest. Flash a non gsi rom. Boot the phone. If it boots and you have it running, then flash a gsi rom .
Click to expand...
Click to collapse
I sadly forgot to make a back up of the rom which in hindsight is stupid of me. I did check and have the latest TWRP version, and managed to get LineAge OS 17.1 working without it being Treblized .
Should i now go on with the procedure of trying to flash a GSI rom with the Treble Convert?
QuirkyTechGuy said:
I sadly forgot to make a back up of the rom which in hindsight is stupid of me. I did check and have the latest TWRP version, and managed to get LineAge OS 17.1 working without it being Treblized .
Should i now go on with the procedure of trying to flash a GSI rom with the Treble Convert?
Click to expand...
Click to collapse
Let's take a back up first and then try. Which tutorial are u following.
Install Android 11 (R) On Any Treble Device ( Detailed Guide)
This way you can install Android 11 On any device without the need of waiting for your manufacturer to push the latest update.
xtremedroid.com
And try Google or aosp gsi from here https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Here's @corsicanu thread for instructions.
But it's for android 9? M not sure though
[AOSP][Treble][G95*F/FD] hadesTreble [03.09.2019]
Disclaimer 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...
forum.xda-developers.com
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.
*
*/
Hi,
here you can find my preview version of LineageOS 19.1 for our Samsung Galaxy Note 8.0 devices.
At first I want to thank @rINanDO and @ChronoMonochrome for all your work which helped me a lot.
This is a BETA build, also on the LineageOS side, so don't install it if you want a completley stable rom and don't report my already listet bugs!
Here you can see how far everything is working for now.
Spoiler: Whats working
Boot
Bluetooth
Audio
Graphics
Cameras
Sensors
Wifi
GPS
USB
Video playback (HW/SW)
Tethering via USB, WIFI and Bluetooth
consumerir transmitter
Stylus
RIL
much more...
Spoiler: Whats not working
Random reboots
Encryption
Maybe more
SD-Card can't be formatted as internal storage, this will cause a bootloop
Spoiler: Links
TWRP
N5100 ROM
N5110 ROM
N5120 ROM
ROM Mega
Magisk zip file
Spoiler: Changelog
26.10.2021
30.11.2021
29.12.2021
09.01.2022
14.02.2022
15.02.2022
18.02.2022
07.03.2022
10.03.2022
17.03.2022
25.03.2022
03.04.2022
12.04.2022
10.05.2022
26.06.2022
23.09.2022
25.01.2023
Spoiler: Don't like my boot picture?
If you don't like it, reboot into recovery and type the following command:
adb shell (or use TWRP's terminal)
bash /data/param_restore.sh
reboot
Uploaded a prepared package to build your own boot picture
download
I would recommend to use microG (much faster experience) or open Gapps as soon they are available.
Do you like my work?
Than you can simply hit the thanks button and consider to spend me a coffee or a beer,
I'm doing this in my free time and it also costs a lot of money to buy hardware.
donate
Wanna improve your sound configs, control your charging current and more?
Now you can use my app to access all boeffla configurations, there will follow more functions.
Exynos4 Kernel Manager - Apps on Google Play
This app provides Boeffla sound control and other kernel + charging tweaks
play.google.com
Spoiler: How to install it?
Instructions
Spoiler: microG instructions
Download Magisk 24.1 and flash it via TWRP (yes, flash the APK file), reboot
Open Magisk and update the App (and do a reboot if it's asking)
Enable Zygisk in Magisk
Download and install microG installer in the Magisk manager, reboot
Download and install safetynet-fix in the Magisk manager, reboot
Check with a safetynet checker app and you should pass
XDA:DevDB Information
[ROM][12.x][N5100/N5110/N5120][BETA] LineageOS 19.1, ROM for the Samsung Galaxy Note 8.0
Contributors
html6405
Source Code: https://github.com/html6405
ROM OS Version: 12.x S
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP 3.5.2
Based On: LineageOS
Selinux: permissive, this only makes sense as soon the ROM is stable.
Version Information
Status: Beta
Created 2021-11-25
Last Updated 2023-01-25
Update 26.11.2021:
N5120: fixed deep sleep bug
fixed sw decoder issue
This update comes via OTA and don't forget, if you're using BitGapps,
reflash them manually after the flash, otherwise you will face a bootloop...
html6405 said:
Update 26.11.2021:
N5120: fixed deep sleep bug
Click to expand...
Click to collapse
Congrats on getting 19.0 up and running! I did notice the initial build had no deep sleep and I was going to report it, but I see you have resolved it now. Which commit on your github fixed the deep sleep? I want to know for learning purposes. NO RUSH for an answer. Thank you.
html6405N5100 (The firmware does not start)
retiredtab said:
Congrats on getting 19.0 up and running! I did notice the initial build had no deep sleep and I was going to report it, but I see you have resolved it now. Which commit on your github fixed the deep sleep? I want to know for learning purposes. NO RUSH for an answer. Thank you.
Click to expand...
Click to collapse
I will push the commit next week.
But it's only a temporyary solution, because of the not working ril so far, there's no deep sleep.
When we remove the radio entries in the device manifest the device will deep sleep.
The real solution will be to find a way of fixing the RIL on A12.
XdaFoxygen said:
html6405N5100 (The firmware does not start)
Click to expand...
Click to collapse
On my n5100 it run's very well, did you install the ROM clean, are you just facing a bootloop?
html6405 said:
On my n5100 it run's very well, did you install the ROM clean, are you just facing a bootloop?
Click to expand...
Click to collapse
Yes, I ran into the Samsung logo hanging on it.
Accidentally the firmware is not for the project treble?
XdaFoxygen said:
Yes, I ran into the Samsung logo hanging on it.
Accidentally the firmware is not for the project treble?
Click to expand...
Click to collapse
You could try to reboot, sometimes it could be that the device doesn't start the first try,
maybe some kind of timing issue in the mounting process.
Treble is disabled at the moment.
html6405 said:
You could try to reboot, sometimes it could be that the device start's the first boot,
maybe some kind of timing issue in the mounting process.
Treble is disabled at the moment.
Click to expand...
Click to collapse
I'm trying to hang on the logo for about 10 minutes and it doesn't go any further ...
oh yes it started although it took a long time (firmware works)
Can I use Open GApps?
Can I install the version of Open GApps from android 11?
334k said:
Can I use Open GApps?
Can I install the version of Open GApps from android 11?
Click to expand...
Click to collapse
No, you have to use gapps made for Android 12.
Update 30.11.2021:
N5100 & N5110: fixed GPS (N5120 should already work)
Enable default power hal for all
This update comes via OTA and don't forget, if you're using BitGapps,
reflash them manually after the flash, otherwise you will face a bootloop...
html6405Thanks for the update, I'm waiting for you to fix everything else.
I watched the app zoom video backwards through the browser. Can't view, message video media player back aborted
Can I edit it to play?
(N5100,Excellent, Rom is very beautiful)
html6405 said:
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.
*
*/
Hi,
here you can find my preview version of LineageOS 19.0 for our Samsung Galaxy Note 8.0 devices.
At first I want to thank @rINanDO and @ChronoMonochrome for all your work which helped me a lot.
This is a early ALPHA build, also on the LineageOS side, so don't install it if you want a completley stable rom and don't report my already listet bugs!
When you have BitGapps installed, you have to reflash them after every update!
Here you can see how far everything is working for now.
Spoiler: Whats working
Boot
Bluetooth
Audio
Graphics
Cameras
Sensors
Wifi
GPS on N5120
USB
Video playback (HW/SW)
Tethering via USB, WIFI and Bluetooth
consumerir transmitter
Stylus with gestures and hovering icon
sec keyboard dock
RIL on N8000 (mobile connection)
much more...
Spoiler: Whats not working
Video recording with both cameras
GPS
N5120: RIL
Random reboots
Maybe more
SD-Card can't be formatted as internal storage, this will cause a bootloop
Spoiler: Links
TWRP
N5100 ROM
N5110 ROM
N5120 ROM
Magisk zip file
Spoiler: Changelog
26.10.2021
30.11.2021
Spoiler: Don't like my boot picture?
If you don't like it, reboot into recovery and type the following command:
adb shell (or use TWRP's terminal)
bash /data/param_restore.sh
reboot
Uploaded a prepared package to build your own boot picture
download
If you are going to use BitGapps,
here you can download them:
BitGapps, arm, 12
For the others, you can use microG in future.
If you plan to use a sim card in your device, I would recommend to disable the pin code before with another device.
In some cases the sim card becomes unusable while typing in the code.
Do you like my work?
Than you can simply hit the thanks button and consider to spend me a coffee or a beer,
I'm doing this in my free time and it also costs a lot of money to buy hardware.
donate
Spoiler: How to install it?
Instructions
XDA:DevDB Information
[ROM][12.x][N5100/N5110/N5120][BETA] LineageOS 19.0, ROM for the Samsung Galaxy Note 8.0
Contributors
html6405
Source Code: https://github.com/html6405
ROM OS Version: 12.x R
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP 3.5.2
Based On: LineageOS
Selinux: permissive, this only makes sense as soon the ROM is stable.
Version Information
Status: Alpha
Created 2021-11-25
Last Updated 2021-11-30
Click to expand...
Click to collapse
Is it a good idea trying to flash the device firmware with your costume ROM
Update 29.12.2021:
Synched with latest LineageOS sources
Signed with dev keys (removes the "signed with public keys" warning)
N5120: Fixed RIL, untested by me, because I don't have my device here, would be great if someone could test and report
N5120: It could be that gps crashes with this version, I would recommend to disable it until next build
Made some fixes for encryption ( but still not finished )
Created workaround to fix shutdown / reboot behaviour with Magisk
Fixed video recording with camera's
Fixed Torch (flashlight)
Fixed hardware button gestures control
Fixed GPS week rollover issue
Set swappiness to 60
Can I run it on a GT-N5105?
ertuncb said:
Can I run it on a GT-N5105?
Click to expand...
Click to collapse
Yes, the n5100 version should be compatible.
html6405 said:
Yes, the n5100 version should be compatible.
Click to expand...
Click to collapse
Flashed the lineage-19.0-20211229-HTML6405-n5100.zip. I've been waiting for 30 minutes with the text 'Samsung GALAXY Note 8.0 GT-N5105' on my screen. Any guesses on how long the first boot might take?
ertuncb said:
Flashed the lineage-19.0-20211229-HTML6405-n5100.zip. I've been waiting for 30 minutes with the text 'Samsung GALAXY Note 8.0 GT-N5105' on my screen. Any guesses on how long the first boot might take?
Click to expand...
Click to collapse
Tired of waiting and restarted by holding down the power button. The animation of LineageOS on initial setup appeared for a short while, then the system booted up. However, while trying to enter the settings and adjust the wireless network settings, the system shut down by itself and booted to TWRP. I've rebooted again and now the see the same boot screen text but with "xdadeveloper html640" in the last two lines. Still waiting, nothing happens. Any suggestions? (In between, I also cleaned dalvik cache and data)
Hello everybody! They brought me the OnePlus Nord 2 with the problem that it can't flash. According to the man, he first set himself Arrow 12.1 via TWRP and everything worked fine. Then he decided to install PixelOS via fastboot. First, he cleared the memory via Fastboot and after that, when he started flashing, his phone restarted at 40 percent. And now the smartphone is trying to start a system that does not exist and the computer does not see the phone in fastboot mode. What to do? Is there any way to restore the device?
Yes. Use mtkclient to flash the original firmware.
[STOCK][FULL-ROM] OxygenOS_11.3_A.20 EU DN2103 | Unbrick guide
/* * Your warranty is... still valid! * 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 yourself before asking or use anything on this...
forum.xda-developers.com
Downgrade from oos 12 beta 2 or stable to oos 11: The MTK client tutorial
All of us knows that we upgraded to OxygenOS 12 stable or beta but OnePlus didn't given roll back package so who are stucked on OOS 12 can now downgrade using this process. This is downgrade process by using relive dvd based MTK client Tutorial...
forum.xda-developers.com
maliczech said:
Yes. Use mtkclient to flash the original firmware.
[STOCK][FULL-ROM] OxygenOS_11.3_A.20 EU DN2103 | Unbrick guide
/* * Your warranty is... still valid! * 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 yourself before asking or use anything on this...
forum.xda-developers.com
Downgrade from oos 12 beta 2 or stable to oos 11: The MTK client tutorial
All of us knows that we upgraded to OxygenOS 12 stable or beta but OnePlus didn't given roll back package so who are stucked on OOS 12 can now downgrade using this process. This is downgrade process by using relive dvd based MTK client Tutorial...
forum.xda-developers.com
Click to expand...
Click to collapse
And what instructions to use? 1 or 2?
So if I were to install a rom on an hdx,
Would the correct procedure be sideload the rom zip wiping dalvik/cache? Then sideloading gapps zip or whatever for apks?
Or would pushing the rom and gapps to sdcard and installing the 2 zips with twrp be alright?
Am I missing anything important? I read people talk about safestrap but oblivious as to what it is or if it matters.
I tried searching for a guide on the correct way to flash custom rom but didnt find anything.
Is there only 1 rom option these years for hdx? I only found 2 lineage options.
I read of AEX, aospextended, etc. but couldnt find them or links 404d. since those files are absent now I guess they are discontinued or deleted by their creator?
Any advice is appreciated.
AstralA said:
So if I were to install a rom on an hdx,
Would the correct procedure be sideload the rom zip wiping dalvik/cache? Then sideloading gapps zip or whatever for apks?
Or would pushing the rom and gapps to sdcard and installing the 2 zips with twrp be alright?
Am I missing anything important? I read people talk about safestrap but oblivious as to what it is or if it matters.
I tried searching for a guide on the correct way to flash custom rom but didnt find anything.
Is there only 1 rom option these years for hdx? I only found 2 lineage options.
I read of AEX, aospextended, etc. but couldnt find them or links 404d. since those files are absent now I guess they are discontinued or deleted by their creator?
Any advice is appreciated.
Click to expand...
Click to collapse
Hi, flashing ROMs usually will come device specific instructions. It can depend on the generation of your device. I searched flash custom ROM on HDX and got this. I hope it helps or at least gets the ball rolling for you.
flash custom rom on hdx - Google Search
[ROM][apollo, thor] Lineage-14.1 [17 MAR 2022]
Disclaimer /* * 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 the products you find...
forum.xda-developers.com
Does seem like theres directions but the directions seem to presume I know enough before hand. Lol
I dont know how to wipe data, it doesnt say much specifically.
Guess I can just go for it and see what happens.
But id rather know exactly so I know my ignorance wont end in a brick or faulty rom install.
I did read ggow say dirty flash was alright. But im not even sure what constitutes dirty flash.
Total green noob here. The only thing im not a noob at is bricking phones by modifying root files. Lol
Thanks for the quick response jonpjingleheimler. Awesome name btw.
Well if I ever figure out the proper way to do this I will write a guide with every possible specific I can muster.
AstralA said:
[ROM][apollo, thor] Lineage-14.1 [17 MAR 2022]
Disclaimer /* * 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 the products you find...
forum.xda-developers.com
Does seem like theres directions but the directions seem to presume I know enough before hand. Lol
I dont know how to wipe data, it doesnt say much specifically.
Guess I can just go for it and see what happens.
But id rather know exactly so I know my ignorance wont end in a brick or faulty rom install.
I did read ggow say dirty flash was alright. But im not even sure what constitutes dirty flash.
Total green noob here. The only thing im not a noob at is bricking phones by modifying root files. Lol
Thanks for the quick response jonpjingleheimler. Awesome name btw.
Well if I ever figure out the proper way to do this I will write a guide with every possible specific I can muster.
Click to expand...
Click to collapse
a lot of us started out not knowing a dirty flash from a clean flash. I think if you are serious about installing a custom ROM it would wise to locate the stock ROM for your device first. Most if not all stock roms for amazon tablets are available for download by Amazon. This way you can at least get back to stock usually without much hassle. YouTube is also a great resource for device specific instructions and sometimes a bit easier to follow. just keep that stock rom on hand. If you get into a bootloop or other crappy situation it's usually possible to get into the stock recovery perform a factory reset or use ADB sideload to flash the stock ROM.
Good to know. Thanks for the advice. I will definitely do that.
I look forward to getting to use apps that are from more recent years that actually work alongside website development.
Its rough finding functional apps when relegated to android kitkat.