{
"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"
}
Note - Iam Not Responsible for bricked devices
About Team win recovery project
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
Installation procedure
1 . Download twrp-3.4.0-0-PL2_sprout.img & twrp-installer-3.4.0-0-PL2_sprout.zip copy in one folder
2. connect phone to pc boot your phone to download mode
3. open cmd in that folder
4. type fastboot devices
5. type fastboot boot twrp-3.4.0-0-PL2_sprout.img
6. now your phone will boot in to twrp
7. now copy twrp installer.zip in to your phone from pc using type c usb cable
8. now flash twrp installer zip ( this will make your twrp permanent )
10. now flash magisk or what ever your wish and press reboot system
11. now if you people want to boot in to twrp? power off your phone connect to pc or charger
& wait for battery logo and press volume up and power button for 8 seconds now you will boot in to twrp
Download Android 11 Twrp-3.4.0-0 From Here
Download Android 10 Twrp-3.4.0-0 From Here
XDA:DevDB Information
TWRP 3.4.0-0 , for the Nokia 6.1
Contributors
Raghu varma
Source Code: https://github.com/Nokia-SDM660/android_device_nokia_PL2_sprout-TWRP
My build script https://github.com/RaghuVarma331/scripts
Version Information
Status: Stable
Current Stable Version: 3.x
Stable Release Date 2020-06-25
Created 2020-06-25
Last Updated 2020-06-25
Changelog - Thu Jun 25 12:41:03 UTC 2020
================================
* https://twrp.me/site/update/2020/06/24/twrp-3.4.0-0-released.html
Great work bro
This can work with locked bootloader ?
Is it compatible with android 9?
When you first start TWRP can you allow changes in the system ?
ativi said:
Is it compatible with android 9?
Click to expand...
Click to collapse
i think yes, cause it booted right away! and installation was successful. I am curently using aosp extended 9.0 official and it works
---------- Post added at 03:53 PM ---------- Previous post was at 03:52 PM ----------
hizaoui said:
Great work bro
This can work with locked bootloader ?
Click to expand...
Click to collapse
No! You need to unlock your bootloader before using this.
Hi,
First thanks for your great work.
But I have a problem.
After doing a full backup and doing some testing, I restored my whole backup. The process succeeded. But I am stuck in a bootloop,my phone boots to the point, where I can see the LOS 17.1 Logo, But does not continue. Have waited for 30 minutes a few times now.
I tried the built in bootloop fix, But it does not fix my problem.
Thanks in advance
Good day every one
Well, yesterday Google released android 11 for pixel handsets.
Soon you people can expect custom roms from my hand mean while i released android 11 twrp builds and with the help of my builds we will go forward accordingly on time for future releases towards custom roms and ports.
Soon I will release road map towards beta program make sure to keep an eye on my xda profile , threads and project updates & don't forget to donate if you love my work and also make sure to hit thanks button.
TWRP Changelog
* initial android 11.0 twrp builds released
Thank you
Thanks, finally a permanent TWRP for the device. (sticking to 10, as a game I play can't handle 11 correctly)
After fastboot boot twrp-3.4.0-0-PL2_sprout.img
Sending 'boot.img' (42412 KB) OKAY [ 1.206s]
Booting OKAY [ 5.049s]
Finished. Total time: 6.466s
Im stuck on android one screen any idea why ?
Hi! I'd like to install TWRP on my Nokia6.1 2018 however whenever I reboot to download mode for whatever reason the device isn't found anymore through ADB and because of that I can't do fastboot devices as it yields nothing and when I skipped it, it just waited for a device forever. What's weird is that it is connected, even windows says that.
KappaTheCapper said:
Hi! I'd like to install TWRP on my Nokia6.1 2018 however whenever I reboot to download mode for whatever reason the device isn't found anymore through ADB and because of that I can't do fastboot devices as it yields nothing and when I skipped it, it just waited for a device forever. What's weird is that it is connected, even windows says that.
Click to expand...
Click to collapse
While phone is in fastboot mode, open device manager. Locate the unknown device and update its driver. Choose fastboot driver from existing drivers. It will install the driver and will work
KappaTheCapper said:
Hi! I'd like to install TWRP on my Nokia6.1 2018 however whenever I reboot to download mode for whatever reason the device isn't found anymore through ADB and because of that I can't do fastboot devices as it yields nothing and when I skipped it, it just waited for a device forever. What's weird is that it is connected, even windows says that.
Click to expand...
Click to collapse
While phone is in fastboot mode, open device manager. Locate the unknown device and update its driver. Choose fastboot driver from existing drivers. It will install the driver and will work
Follow this,
fastboot flash recovery (drag recovery here or insert path)
press enter, it will fail saying something about a-b slots
Then finallay do,
fastboot boot (drag recovery here or insert path)
press enter
should boot your TWRP now
dmilz said:
fastboot flash recovery (drag recovery here or insert path)
press enter, it will fail saying something about a-b slots
Then finallay do,
fastboot boot (drag recovery here or insert path)
press enter
should boot your TWRP now
Click to expand...
Click to collapse
Thanks, I had same problem and this is working. Anyway the problem is, I have to do this every time I want to TWRP. Is there any way how to fix this and be able to avoid `flash recovery` part?
edit: removed
Looks like can't decrypt with Android 11. I'm 100 % sure that password is correct. With Android 10 it worked fine.
Are there any plans for updates? Thanks.
Hello people,
I accidently flashed the twrp-3.4.0-0-PL2_sprout.img file and now I am stuck in the androidone loading screen anytime I try to boot to that file in order to flash the twrp-installer-3.4.0-0-PL2_sprout.zip file.
Also when I try to boot the recocery I am stuck in the loading screen of TWRP.
any suggestion to fix that ?
maxischr said:
Hello people,
I accidently flashed the twrp-3.4.0-0-PL2_sprout.img file and now I am stuck in the androidone loading screen anytime I try to boot to that file in order to flash the twrp-installer-3.4.0-0-PL2_sprout.zip file.
Also when I try to boot the recocery I am stuck in the loading screen of TWRP.
any suggestion to fix that ?
Click to expand...
Click to collapse
The device has 2 boot slots. Try switching with fastboot --set-active: https://www.techmesto.com/possible-fix-nokia-smartphone-stuck-on-download-mode-after-ota-update/
I cannot file the download link for the twrp installer.zip file. I have the image file but cannot find the zip file on the github download site.
Related
Alright, I don't really want to do this, since the rom is not finished yet but I need help and I thought that releasing it would attract developers, so here it is, the first rom for our P8 Lite (ALE-L21)
Current Status: Developer Preview
The rom is at an early development stage, since I don't have enough time to figure out how to make RIL work.
Just flash the rom if you know what you are doing, it isn't stable or functional, it's just a preview, and a waste of time if you don't know how to do things properly.
What works:
Audio
Camera
Wifi
Most apps
Some other things
What DOESN'T work:
NFC
Bluetooth (It used to work, however it's not my priority)
RIL (3G , 2G, GPRS...)
GPS (I haven't tested it but I guess it isn't working)
Playing some kind of media files
How to install it:
Wipe data/cache (factory reset) after installation
Flash boot and system.img via fastboot.
Download
Remember to backup everything before flashing, I am not responsible of Data loss, phone bricking, or whatever.
Device Source: https://github.com/XePeleato/android_device_huawei_p8lite_alel21
Kernel source: https://github.com/XePeleato/android_ALE-L21_kernel
We need some help over there, so if you want to help and are skilled in Java, drop a message.
I also want to thank everyone who helped me on Github.
I guess that's it, if anyone could move this to the development section it would be really nice.
Have a nice day!
info
any screenshots maybe? im happy that someone is working on rom for this phone
Hello...
This ROM is also compatible with model ALE-L02 and L23?
Thank y!
Hello @XePeleato that compilation must be to install?
Enviado desde mi hi6210sft mediante Tapatalk
Awesome, I've been following your development on GitHub. Very happy with your progress!
Keep it going, as soon as you get RIL working, I'll get it on my phone. Can't stand this EMUI thing.
Either way, thank you for your great work and best of luck!
I do not know exactly how I installed . Can you explain in detail ?
Did you see this HiKey board? (Google for it I still can't post links to external pages :\ ) There is full documentation about Kirin 620 and even a Android port with USB OTG support (of course source is open). May be you try to enable USB OTG?
Install ROM
Xpredator 20 said:
I do not know exactly how I installed . Can you explain in detail ?
Click to expand...
Click to collapse
For install:
1. You must be unlocked bootloader
2. Enable ADB debugging in advanced options (tapping serveral times on about phone > compilation and you'll get that option in settings) and connect the phone to the PC
3. Download android studio SDK and then go to C:\Users\Yourusersname\AppData\Local\Android\sdk\platform-tools
4. Open a cmd terminal (shift + right click)
5. Download the TWRP recovery 3.0 that XePeleato made from his github (sorry I can't post links yet)
6. Now in cmd write: adb reboot bootloader and the adb drivers will be installed in your PC (if not, download ADB Driver Install)
7. Place the recovery.img from the recovery zip to the folder where you opened the terminal (platform-tools)
8. Now write in cmd: fastboot flash recovery recovery.img
9. Write in cmd: fastboot reboot recovery
10. DO A COMPLETE BACKUP (that's important)
11. Now download the ROM and place the system.img and the boot.img of the .zip in the same folder as before.
12. Write in cmd: fastboot flash boot boot.img
13. Write in cmd: fastboot flash system system.img
14. Write in cmd: fastboot reboot recovery
15. Now in recovery select wipe > advanced wipe and select data and cache
16. Install Gapps for 5.1.1 if you want.
That's it, hope it works.
If you share screenshots to see the pre-appearance, I'm totally interested in this project.
Enviado desde mi ALE-L21 mediante Tapatalk
Screenshots
C'mon guys, haven't you already seen AOSP? Well... Here you got the screenshots:
{
"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"
}
Last screenshot is from the 5.0.1 release, but anyway.
I love AOSP, I just needed to see that it was not disguised EMUI
Enviado desde mi ALE-L21 mediante Tapatalk
wilburyh said:
For install:
1. You must be unlocked bootloader
2. Enable ADB debugging in advanced options (tapping serveral times on about phone > compilation and you'll get that option in settings) and connect the phone to the PC
3. Download android studio SDK and then go to C:\Users\Yourusersname\AppData\Local\Android\sdk\platform-tools
4. Open a cmd terminal (shift + right click)
5. Download the TWRP recovery 3.0 that XePeleato made from his github (sorry I can't post links yet)
6. Now in cmd write: adb reboot bootloader and the adb drivers will be installed in your PC (if not, download ADB Driver Install)
7. Place the recovery.img from the recovery zip to the folder where you opened the terminal (platform-tools)
8. Now write in cmd: fastboot flash recovery recovery.img
9. Write in cmd: fastboot reboot recovery
10. DO A COMPLETE BACKUP (that's important)
11. Now download the ROM and place the system.img and the boot.img of the .zip in the same folder as before.
12. Write in cmd: fastboot flash boot boot.img
13. Write in cmd: fastboot flash system system.img
14. Write in cmd: fastboot reboot recovery
15. Now in recovery select wipe > advanced wipe and select data and cache
16. Install Gapps for 5.1.1 if you want.
That's it, hope it works.
Click to expand...
Click to collapse
I installed mine. I wonder if the problem is corrected when the sim card?
This ROM is also compatible with model ALE-L02 and L23?
SkopiX said:
perfect work man but this rom belongs to DEVELOPMENT section, not general
and this is not 1st custom rom, there is already 1 custom rom and 1 flashable via TWRP
still perfect work
Click to expand...
Click to collapse
Since I needed 10 posts to post it there.
Is there any other rom ? I'd love to know what rom is that, maybe RIL is fixed there.
but these 2 roms are modified emui. They aren't based on pure AOSP
Your work it's on facebook, without your name...
Enviado desde mi ALE-L21 mediante Tapatalk
dominj97 said:
but these 2 roms are modified emui. They aren't based on pure AOSP
Click to expand...
Click to collapse
thats true didnt realize diferences, I just saw "rom" not aosp
@XePeleato I guess RIL can be fixed by some dirty hacks on binaries.
I worked before on Xperia devices (CMs, AOSPs, ports) but maybe I can help a bit.
Hi all,
I have this device since saturday and i noticed that there is a sririous lack of aosp roms.
Since i'm not very far with my Java skills i wanted to know if there are peoople willing to join up and develope a custom ROM flashable tru twrp.
Those are my ideas, anybody in ?
Greetings,
Justin.
Its kernel can oc ?
{
"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"
}
A Mobile Version of the Ubuntu Operating System
Ubuntu Touch is made and maintained by the UBports Community. A group of volunteers and passionate people across the world. With Ubuntu Touch we offer a truly unique mobile experience - an alternative to the current most popular operating systems on the market. We believe that everyone is free to use, study, share and improve all software created by the foundation without restrictions. Whenever possible, everything is distributed under free and open source licenses endorsed by the Free Software Foundation, the Open Source Initiative.
For more information check out the UBports website.
Known issues:
Recording video doesn't work
Changing volume in-call doesn't work
Contribute:
As not everything is working fully yet helping hands are welcome!
Follow the project management issue over at the Halium GitHub page:
https://github.com/Halium/projectmanagement/issues/98
Instructions (tested on Ubuntu 18.04):
First make sure to wipe /system & /data from within TWRP. The partitions must be ext4.
Make sure to upgrade your device to the latest stock Android 8.0 before continuing: https://developer.sony.com/develop/open-devices/get-started/flash-tool/
Download and install the UBports installer: https://github.com/ubports/ubports-installer/releases
OEM unlock your device: https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/
Boot your device into fastboot mode by shutting it down and keeping the Volume Up button pressed while plugging in a USB cable between your phone and PC. The LED should be on and blue.
Flash the OEM binaries from: https://developer.sony.com/file/download/software-binaries-for-aosp-nougat-android-7-1-kernel-4-4-loire/ using:
Code:
fastboot flash oem SW_binaries_for_Xperia_AOSP_N_MR1_5.7_r1_v08_loire.img
Run the UBports installer and follow the on-screen instructions
Reserved for future use
wtf bro i never expected to see ubuntu touch on any device again great news and good work! keep it up!
Too bad my device broke......gotta fix fast lol
I've updated download links and the instructions to enable call functionality. Testers welcome!
Ready for tests! Just need to install Ubuntu with current manual
Have I need to flash stock rom with android 7 or just flash binaries on stock android 8?
New tests to be done, we've recently gotten video decoding to work and I enabled basic camera support.
OP has been updated with the link to the newest images.
Feel free to post issues here if you are not feeling well with GitHub.
Regarding stock ROM or not:
Any system image should work, you can even wipe system as it's not used.
As long as the ODM partition is flashed everything should be good.
I'm trying this for the 2nd time and both times I can't get any audio in calls. I ran the commands in the first post. Any tips on what else to try? I'd really like to try this, test some more and help out, but it's the only phone I've got right now.
samijam said:
I'm trying this for the 2nd time and both times I can't get any audio in calls. I ran the commands in the first post. Any tips on what else to try? I'd really like to try this, test some more and help out, but it's the only phone I've got right now.
Click to expand...
Click to collapse
Did you run the commands through ssh or via the Terminal app? Mind doing a "select all" and copy-paste the output to some paste service?
EDIT: Also, did you reboot after issuing the commands?
Thanks for the work on this.
I need a little bit more explanation on how to install this. I gave it a try, but I end up in getting a white boot screen with the sony logo. Installing SailfishOS with the flash.sh script works perfectly.
Questions:
- When do you need to use twrp? When running adb?
- Running the halium install script only works when booted into twrp. Is this correct?
- Do you need to manually boot into fastboot mode (volume up, blue led)?
- The sailfish installation uses oem for android 6, here 7 is used. Can this make the difference?
Thanks for any support.
beidl said:
Did you run the commands through ssh or via the Terminal app? Mind doing a "select all" and copy-paste the output to some paste service?
EDIT: Also, did you reboot after issuing the commands?
Click to expand...
Click to collapse
Sorry for the late reply. I got it to work now. My problem was using an outdated system.img and boot.img. (oops, sorry, my bad!) I had downloaded the newer versions, but had them in the wrong directory. Once I deleted the old and installed the correct versions, I was able to get audio in calls and had the basic camera functionality.
---------- Post added at 16:43 ---------- Previous post was at 16:37 ----------
matiz098 said:
Thanks for the work on this.
I need a little bit more explanation on how to install this. I gave it a try, but I end up in getting a white boot screen with the sony logo. Installing SailfishOS with the flash.sh script works perfectly.
Questions:
- When do you need to use twrp? When running adb?
- Running the halium install script only works when booted into twrp. Is this correct?
- Do you need to manually boot into fastboot mode (volume up, blue led)?
- The sailfish installation uses oem for android 6, here 7 is used. Can this make the difference?
Thanks for any support.
Click to expand...
Click to collapse
boot into fastboot and flash the oem:
fastboot flash oem SW_binaries_for_Xperia_AOSP_N_MR1_5.7_r1_v08_loire.img
then boot into twrp recovery and wipe /system and /data
while in twrp, run the halium-install.sh script (because the computer needs to connect to phone in adb mode, which twrp provides)
following from there, as you see in the first post, you will run "adb reboot bootloader" (but I think I did have to do it manually) which should put you back into fastboot mode where you'll "fastboot flash boot halium-boot.img"
then you should be able to reboot into ubuntu. The first boot takes a little longer.
Are there any screenshots available?
Fajormein said:
Are there any screenshots available?
Click to expand...
Click to collapse
No but you can find some videos on YouTube, just search for "Ubuntu Touch 2019".
The videos might feature different phones but it's the same on the Xperia X.
Is there any way to install it using a windows pc?
Fardin Rehman said:
Is there any way to install it using a windows pc?
Click to expand...
Click to collapse
Not currently.
please make a porting for kugo (x compact) sir
rizky_zulfikar said:
please make a porting for kugo (x compact) sir
Click to expand...
Click to collapse
Someone else is working on that already, but this port is only for the Xperia X (F5121).
In other news:
Installation instructions have been updated, the Xperia X port is now available from the UBports community channel!
Can you make port for XA 2 (H3113)
As I get the question very often: To support the F5122 variant of the Xperia X (or other devices in general) for Ubuntu Touch I need donations to buy the device.
Use the "Donate To Me" button on XDA or head over to https://fredl.me/donate/ for info on how to do so.
In other news: The Xperia X F5121 has gained support for the official UBports installer. You can now flash the device using a fancy GUI.
I hit 2 problems. For some reason neither Emma nor flashtool wants to flash stock rom correctly. Tried to flash ubuntu through stock 8.0 custom rom, phone reboots and black screen. Also there is was an error with something that the file couldn't be sent to the phone
Click to expand...
Click to collapse
Ok, so I did install the stock rom through EMMA fine. I did enable the usb debugging, installed twrp, wiped system & data, made sure they are EXT4. Rebooted to fastboot, installed SW binaries. Opened UBports Installer & proceeded with instructions. I got this error
Code:
Error: systemimage: Error: Error: {"error":{"killed":false,"code":1,"signal":null,"cmd":"C:\\Users\\domin\\AppData\\Local\\Temp\\1Uo4H80AYPnCivmpnC8M9LLWxLb\\resources\\app.asar.unpacked\\platform-tools\\win\\adb -P 5037 shell mount -a"},"stdout":"","stderr":"mount: mounting /dev/block/bootdevice/by-name/userdata on /data failed: Invalid argument"}
Any solutions, did I miss something? I gonna retry without the twrp step, as I am pretty sure the partition format will be EXT4
{
"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"
}
Notes:
These are built with kernels from the latest Beelink GT-King (Amlogic S922X w/ w400 reference board) and Beelink GT1mini (Amlogic S905X2 w/ u212 reference board) firmware, but will probably work on any device based on the same reference boards.
The signed .ZIP files are suitable for installation with stock OEM recovery, but they use platform test keys and so might not work on builds requiring release keys.
If your device uses Android Verified Boot, there are additional measures you must take to successfully boot with a custom recovery partition.
Some OEM firmware have a stock recovery auto-restoration "feature" that will immediately replace TWRP after you reboot to system. The easiest workaround is simply to reboot to recovery immediately after the flash by holding the reset button. You can also try renaming /system/recovery-from-boot.p.
This is unofficial and unsupported, so the usual caveats apply. Since we don't flash the bootloader, you should be able recover from any problems...but nothing is guaranteed.
Not working:
MTP & ADB
Downloads:
S922X (Amlogic w400 reference board):
twrp-9.0-w400-3.7.0-0.img
twrp-9.0-w400-3.7.0-0-signed.zip
S905X2 & S905X3 (Amlogic u212 reference board):
twrp-9.0-u212-3.7.0-0.img
twrp-9.0-u212-3.7.0-0-signed.zip
Change Log:
v3.7.0-0: (20221204)
Updated to TWRP 3.7.0 release built from OMNI branch.
Updated to 007P0 LPDDR4 (u212) and 921P0 (w400) kernels.
v3.3.1-0: (20191111)
Switched from KM9 to GT1mini kernel
v3.2.3-0: (20190929)
Initial release
Instructions:
From OEM update app:
Copy .ZIP file to flash drive or microSD card
Open the UPDATE app and select Local Update
Select the .ZIP file and confirm
Note: No need to wipe data or cache
From OEM stock firmware (with root):
Open terminal window (e.g. Terminal Emulator for Android by Jack Palevich)
Navigate to location of .IMG file
Type the following:
Code:
su
dd if=twrp.img of=/dev/block/recovery
reboot recovery
From existing TWRP install:
Copy .IMG file to flash drive or microSD card
Click Install->Select Storage and pick the external drive
Click Install Image and select the .IMG file
Select Recovery partition and swipe to install
Reboot to Recovery
Source:
android_device_amlogic
Donations:
Your support is always appreciated! Just click here.
Hi!
I put your recovery using the UPDATE app method and I am unable to boot to it using "adb reboot recovery". Got a black screen
knuxxx said:
I put your recovery using the UPDATE app method and I am unable to boot to it using "adb reboot recovery". Got a black screen
Click to expand...
Click to collapse
Sounds like your box is using AVB 2.0.
Can someone please assist with how to root the U211 devices? TWRP works great, SuperSu 2.82 installs successfully via TWRP but when the system boots, it's still not rooted.
Any help is greatly appreciated here
Hey I'm stuck on bootloop, any hElp please? Gtking (S922X)
Vee89 said:
Hey I'm stuck on bootloop, any hElp please? Gtking (S922X)
Click to expand...
Click to collapse
Do you perhaps have the DDR4 (S/N: B922X) version of the GT-King? This one was build for the LPDDR4 (S/N:922X) hardware revision.
Magendanz said:
Do you perhaps have the DDR4 (S/N: B922X) version of the GT-King? This one was build for the LPDDR4 (S/N:922X) hardware revision.
Click to expand...
Click to collapse
I have : S/N:922XHQHE00129
Do you know a way to boot in recovery?
Vee89 said:
I have : S/N:922XHQHE00129
Click to expand...
Click to collapse
That *should* work then.
Vee89 said:
Do you know a way to boot in recovery?
Click to expand...
Click to collapse
Just hold the reset switch in for about 20 seconds while connecting power.
Fastboot mode is more of a challenge on the GT-King, since it can't get enough power from the USB cable by itself. You've got to hold the reset switch while simultaneously connecting both power and the USB cable to the back port.
Magendanz said:
That *should* work then.
Just hold the reset switch in for about 20 seconds while connecting power.
Fastboot mode is more of a challenge on the GT-King, since it can't get enough power from the USB cable by itself. You've got to hold the reset switch while simultaneously connecting both power and the USB cable to the back port.
Click to expand...
Click to collapse
Ok thank you, I tryed recovery mode.. still stuck in bootloop, I ordered a usb cable from gearbest so I will try fastboot wen mail knocks
Thank You TWRP work well
Magisk installation
And what to do to install Magisk correctly. The root is already on the Android 9 device. Unfortunately, the Magisk installation by TWRP has failed so far. Have any ideas? (applies to device and Amlogic S905X2 HK1 Play)
Can this be used on the Ugoos AM6 pro 4 gb / 32 gb s922x?
I guess so?
Duvel999 said:
Can this be used on the Ugoos AM6 pro 4 gb / 32 gb s922x?
Click to expand...
Click to collapse
My understanding is that Ugoos doesn't use the platform keys, and so the .zip file won't work with the OEM stock recovery. You should be able to flash the .img file, though, from TWRP or dd with root. (Yes, I know that's a bit of a chicken-or-egg scenario, so you might need to use Amlogic's USB Burning Tool or update.exe.) Also, look to see if they've implemented AVB 2.0, which can also be a PITA to work around.
Hi
I've got my eyes on a Beelink GT king Pro. Does this work with a s922x-h board @Magendanz ?
MAMATDZ said:
I've got my eyes on a Beelink GT king Pro. Does this work with a s922x-h board @Magendanz ?
Click to expand...
Click to collapse
I'd be surprised if it didn't. It's based on the same reference board as the GT King.
Ok great !
Thanks for the quick answer ^^
have someone a way to put TWRP on Amlogic S905X3?
Hi.
Can this be used on the S905X3? (Wechip v9 4GB/32GB)
Hello. When I try "Apply update from EXT", I got:
Code:
Found: Amlogic/p281:8.10/OPM1.171019.011/root:userdebug/test-keys
E3003: This update package is intended only for Android Pie builds (SDK 28)
Does it mean I cannot install it in Oreo Android?
romkeris said:
Hello. When I try "Apply update from EXT", I got:
Code:
Found: Amlogic/p281:8.10/OPM1.171019.011/root:userdebug/test-keys
E3003: This update package is intended only for Android Pie builds (SDK 28)
Does it mean I cannot install it in Oreo Android?
Click to expand...
Click to collapse
Yes that is what it means, I think his REF to TWRP-9.0 pretty much explains its for android 9 aka Pie only.
But there are many other recoverys that do work for Oreo...
Source: https://unofficialtwrp.com/xiaomi-redmi-9-root-twrp-3-4-1/ The author wrote this: all issues fixed!
Thanks to the developer for the energy and time. Developer: wzsx150.
This is a working unofficial TWRP recovery for Redmi 9 for Miui 11. Tested on android 10, Miui Global 11.0.6 rom.
Miui 12 is work? I do not know. Everyone doesn't know. It probably won't work.
Original file: https://www.mediafire.com/file/auj2wh2lh8lzp47/3.4.2+Redmi+9+CN+EN.rar/file I modified this a bit.
What is required for installation:
Twrp img (blue) (recovery.img): Download
vbmeta_redmi9.img Download
1: Unlock bootloader
2: installed adb & fastboot drivers Download
3: Optional: Mtk usb driver Download
3a: Let the phone battery be charged to more than 50% !!!
(4: Everyone is at their own risk)
(5: Backup all data, recommended. Save idea 1, Save idea 2
6: Turn off the phone
7: Then press the volume down button + power on button to enter fastboot succes fastboot screen
8: Now connect your phone to your computer (windows emits a connection sound)
9: Open one a cmd/command line, where you downloaded the files cmd
10: Issue the two commands one after the other
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta_redmi9.img
11: You ready. Restart the phone in recovery mode
fastboot reboot recovery
12: If you did everything right, this picture will welcome you
12.a: If recovery asks you for a security pattern, enter what you use on your phone.
{
"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"
}
12: If you messed up something, don't worry. Someone here will help. (It can usually be restored with Adb or fastboot, which is broken)
13: A few pictures of the program
14: Four colors are available: blue, red, brown, purple.
Blue TWRP Recovery: Download
Red TWRP Recovery: Download
Braun TWRP Recovery: Download
Purple TWRP Recovery: Download
For now, only Chinese and English language are available! The other languages are being prepared. Soon. As there will be time for it.
It doesn't hurt to have these:
Qualcomm HS-USB QDLoader 9008 Driver 64-bit [Windows] Qualcomm driver
MediaTek MT65xx Preloader VCOM USB Driver [32-bit & 64-bit] Mediatek Vcom driver
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 Adb & fastboot drivers
MTK usb driver Download
SDK Platform tools Download
Google usb driver Download
Thanks for watching. If you liked my job, you can invite me for a beer.
Paypal: [email protected]
Crypto: 3FJuZGaw98oefj45AiypytaJzyATuRn7dE
Reserved
I saw this at telegram yesterday
Is this updated version?
SunuWijaya said:
I saw this at telegram yesterday
Is this updated version?
Click to expand...
Click to collapse
Where did you see that? (I don't understand) Two versions of this have been made. This is the second.
short question,what have you modified and how did you testet which things,we have no custom rom,what about backup and restore,did you testet,what about flashing zips in general and are all partitions rw?Thanx!!!!
-CALIBAN666- said:
short question,what have you modified and how did you testet which things,we have no custom rom,what about backup and restore,did you testet,what about flashing zips in general and are all partitions rw?Thanx!!!!
Click to expand...
Click to collapse
Hello. Well ... there weren't many tests available yet.
What I modified:
1: Skins / colors
2: Spelling mistakes
3: Syntax errors 2-3 pieces
What I was able to test in recovery:
1: Install zip / img: works
2: Backup and restore partition / data: works
3: Mount partitions: works
4: Wipe / advanced wipe: works
5: Reboot "all: works
6: Terminal: works
7: ADB Sideload: works
8: File manager: works
9: Settings "all works, except multilanguage.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Other. For everyone. It also became a fifth skin. Orange / black. Download
------------------------------------------------------------------------------------------------------------------------------------------------------------------------It's different again. For everyone. I noticed a mistake yet. I haven’t used recovery in a long time, so I didn’t notice the error. After a while, twrp recovery disappears. And the original recovery will be again. I don't understand why .... If you twrp recovery in flash fastboot mode again, you have twrp again. For a while.
Can dis twrp flash kernel?
Meggyi said:
Hello. Well ... there weren't many tests available yet.
What I modified:
1: Skins / colors
2: Spelling mistakes
3: Syntax errors 2-3 pieces
What I was able to test in recovery:
1: Install zip / img: works
2: Backup and restore partition / data: works
3: Mount partitions: works
4: Wipe / advanced wipe: works
5: Reboot "all: works
6: Terminal: works
7: ADB Sideload: works
8: File manager: works
9: Settings "all works, except multilanguage.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Other. For everyone. It also became a fifth skin. Orange / black. Download
View attachment 5164259
------------------------------------------------------------------------------------------------------------------------------------------------------------------------It's different again. For everyone. I noticed a mistake yet. I haven’t used recovery in a long time, so I didn’t notice the error. After a while, twrp recovery disappears. And the original recovery will be again. I don't understand why .... If you twrp recovery in flash fastboot mode again, you have twrp again. For a while.
Click to expand...
Click to collapse
Ok,big thanx for info.Cheers!!!
SunuWijaya said:
Can dis twrp flash kernel?
Click to expand...
Click to collapse
Does it have a custom kernel? Modified kernel? Has anyone tried kernel flash? I don't think so. (Zip and img flash, it knows) Do you know of a modified kernel?
Meggyi said:
Does it have a custom kernel? Modified kernel? Has anyone tried kernel flash? I don't think so. (Zip and img flash, it knows) Do you know of a modified kernel?
Click to expand...
Click to collapse
Just try to flash stock kernel
Afaik the issue with the missing twrp recovery is normal and only on miui based rom,on custom roms there is no issue like that.Most Xiaomi/Redmi devices do that.
Meggyi said:
Does it have a custom kernel? Modified kernel? Has anyone tried kernel flash? I don't think so. (Zip and img flash, it knows) Do you know of a modified kernel?
Click to expand...
Click to collapse
Yes it is have custom kernel named Minati-Xenodrome
How to use twrp to flash GSI ?
-CALIBAN666- said:
Afaik the issue with the missing twrp recovery is normal and only on miui based rom,on custom roms there is no issue like that.Most Xiaomi/Redmi devices do that.
Click to expand...
Click to collapse
Yeah, I get it. I didn’t have many phones that miui had. That makes sense. Stupid miui
Good job....I flash custom kernal...and it successful...but can this twrp able to go fastbootd as you mentioned and flash gsi like stock recovery?
Have you flashed a rom?
The solution for the issue that twrp is gone after some times is to flash the no-verity-opt-encrypt file for the device directly after flash of recovery,after this twrp is permanent,for the file check source link in first post.Cheers!!!!
Thank you very much, but my Redmi 9 China version cannot boot after flashing into twrp.
On Redmi 9 China version, I sorted out this version to be available.It seems that it can only be used for MIUI11
zhihuiyuze channel
论坛附件，Redmi9 twrp且可以在中国版使用
t.me
Google Drive Education Edition cannot share files (so use Telegram
There is another problem. It seems that if I use your modified version, /cust fails.
What we can do with this TWRP on lancelot?
I have the Redmi 9 (lancelot) with MIUI 11 installed. My bootloader is unlocked, I've the adb & fastboot drivers installed. I would really like to install that TWRP. While I'm flashing both files, cmd gives no errors, everything is fine. But at the end, I can not boot into recovery with "fastboot reboot recovery" from the cmd, it gives me an error. If I leave fastboot mode and try to enter TWRP manually by holding the volume and power key, it doesn't work. My device will get stuck inside a bootloop.
I'm able to fix the bootloop with disabling DAA & SLA protection in the MTK mode and flashing back the stock firmware with SP Flashtool. I tried it 3 times, every time the same issue and having to flash back the stock firmware. Do you have any tips to fix that? Or is there another or updated version I could try?
Edit: Nvm, got it working
Hi All,
I'm trying to install ArrowOS13.1 on my Mipad 5 Pro without sucess and wondered if anyone had been sucessful?
I tried some stesp I found here https://forum.xda-developers.com/t/arrowos-v13-1-mi-pad-5-pro-12-4-dagu-step-to-install.4579335/ but just up to the flashing the payload file as I don't think the vendor boot etc are required since I think those steps were to get the elish rom working on a dagu device.
From the start it didn't go well. I had the Lynnrin rom on originally. When I went to flash 13.1 it worked, but although I had the vanlla version the tablet had gapps on it, Doh, I need to wipe the data partition. So I did that with XiaomiToolv2 (i think it was a few days ago), but after that no booting at all. Damn, ok lets recover with XiaominToolv2, i've done that before sucessfully. That failed becuase because no matter what I could not get into fastbootd mode. But i eventually got the machine flashed by using the flash_all.bat file in the stock rom from XiaomiToolv2 by using an updated fastboot and shortening the file path to the rom. What I didn't realise at the time was thatit was now a different version of the rom (MIUI 14 now)
So great I've got stock back. Now I try to flash the payload filefor 13.1 which flashes, but won't boot. I tried swapping slots for booting but that didn't help.
Has getting it on MIUI 14 locked me out?
I don't want to flash back to MIUI 13 stock as I've heard XIAOMI has an anti rollback thing in place that bricks devices (but I think but not willing to bet, that this doesn't have anti rollback)
Thanks
Hey crass00,
If you're still wondering on how to install Arrow 13.1 on elish, I think you can just follow Lynnrin's past instructions on installing Arrow 12. Copy-pasted below (credit to Lynnrin, modified for clarity, link replaced with the new one you posted in another thread):
Spoiler: Install Custom ROM on Mi Pad 5 Pro (elish)
1. Unlock bootloader
2. Reboot to fastboot
3. Flash MIUI Recovery by this command fastboot flash boot miui_recovery.img
4. Reboot to recovery by this command fastboot reboot recovery, and format data on MIUI Recovery
5. Hold power button + volume down, when screen off, release power button, release all button when it get in bootloader.
6. Flash AOSP recovery by this command fastboot flash boot aosp_recovery.img
7. Reboot to recovery by this command fastboot reboot recovery
8. Enter to sideload mode by this command adb reboot sideload-auto-reboot
9. Sideload zip by this command adb sideload ***.zip (change ***.zip to the Arrow13.1 ROM zip file, in my case I used Arrow-v13.1-elish-OFFICIAL-20230426-GAPPS.zip)
10. Once that custom ROM installed on your Pad.
p.s. on number 9, when sideloading the ROM, the percentage progress seems to be stuck at 47% for a long time for me, don't panic and just leave it for a few minutes, it will magically finish the process and reboot the tab automatically.
I don't think there's any need to flash back to MIUI 13 as I've also made the mistake of flashing it to MIUI 14 first, and there doesn't seem to be any problems so far.
{
"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"
}
Super that worked. Many thanks.
I actually tried this way last night but failed at the step to delete data. I don't read chinese so couldn't delete data, figured I'd just wiped the device fully with a MIUI restore anyway so whats the need and moved on. That was a mistake With the confirmation it works i installed google translate on my phone to find my way though the menu.
I hope now once an update comes out the data delete step isn't required. That could get annoying if it is
Yeah, I'm wondering about that too actually.
My assumption is that the aosp_recovery.img is already installed as the recovery, so maybe we could just start from step 7?
I'm completely unsure though.
For other devices that I used usually there's a working TWRP recovery and I could just do flashing/updating through TWRP.
At least there doesn't seem to be any major bugs for this Arrow 13.1 build for elish (dagu in the other thread has camera problem).
What's wrong with the official instructions from the maintainer?
Instructions thread for (elish) MiPad 5 Pro on ArrowOS - HackMD
# Instructions thread for (elish) MiPad 5 Pro on ArrowOS This blog post is dedicated to [Xiaomi Pad
hackmd.io
Didn't notice it
i can verify this device does not have anti-rollback
I once went from android 12 to android 11
and from android 13 to android 12
so it should be just fine
it's just that sometimes miflash showed an error after flashing
I succesfully flashed this on enuma after 2 attempts using Lynnrin's past instructions but with the newer build
first attempt was with miui 13 (Android 12) but it automatically stopped at 47% and rebooted so it didn't fully flash arrow
for my second attempt I first flashed miui 14 (android 13) and then did the same process again but this time it worked just fine
I guess the logic is that you have to be on the android version you want to flash
camera works (on dagu it doesn't for some reason)
and the xiaomi smart pen also works
edit: is it just me or does the wifi feel slower?
niveZz said:
I succesfully flashed this on enuma after 2 attempts using Lynnrin's past instructions but with the newer build
first attempt was with miui 13 (Android 12) but it automatically stopped at 47% and rebooted so it didn't fully flash arrow
for my second attempt I first flashed miui 14 (android 13) and then did the same process again but this time it worked just fine
I guess the logic is that you have to be on the android version you want to flash
camera works (on dagu it doesn't for some reason)
and the xiaomi smart pen also works
edit: is it just me or does the wifi feel slower?
Click to expand...
Click to collapse
All process being run by AOSP recovery will stop at 47%. But you will be noticed by a line of message saying successfully or not.
In my case, I flashed MIUI Android 12 and using A13 GSI ROM. Everything works fine except the GSI ROMs do not support Xiaomi peripherals.
How do I install Magisk using this rom?
I tried following this but then devices wont boot up again