I've been trying to install Kali Nethunter on my spare Nord N10 5g.
Ive unlocked the bootloader and I know how to do Magisk, the issue is once I do Magisk I get in a reboot loop with my TWRP recovery.
Installation
The Magic Mask for Android
topjohnwu.github.io
I follow all the steps posted in this link except when I reboot, I get stuck in TWRP and cant get the phone to boot to an OS.
I might be blind but has anyone had a similar issue, and know how to fix me? Thank you, sorry if this has been posted before. I couldnt find it if it was. Feel free to ask questions.
Edit: Just saw on TWRP that I have no OS installed... OK. So shouldnt that not be the case if Im trying to install NetHunter? Because thats only able to be installed through Magisks modules in their app? Am confuzzled.
{
"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"
}
Did you disable verity on vbmeta and vbmeta_system?
You can also try patching the boot image and install it using fastboot.
DavidxxxD said:
Did you disable verity on vbmeta and vbmeta_system?
You can also try patching the boot image and install it using fastboot.
Click to expand...
Click to collapse
Let me check and get back to you. Edit: Yes I did.
And no, I'll have to try that. Be right back.
DavidxxxD said:
Did you disable verity on vbmeta and vbmeta_system?
You can also try patching the boot image and install it using fastboot.
Click to expand...
Click to collapse
Alright after checking, I cannot install custom ROMs through fastboot, hence the custom recovery (TWRP) but then to install Nethunter it wants me to use Magisk... and thats where I run into the issue discribed in my first message.
That issue being: after flashing the twrp recovery image with magisk it deletes my OS so I cant use magisk without installing another custom ROM... getting rid of the progress made with Magisk.
@reesespieces909
But is verity disabled? Phone does not like it when verity is enabled and it's part of the process to install twrp. Also, it is A/B. What's inside the zip file? What exactly needs to get installed? I believe the phone is breaking because of the dynamic partition but it could be taken care of by the installer. Is it a generic build or specialised for this device?
I am pretty sure it was, I just went back through all the steps and now am geting a screen that says "Qualcomm CrashDump mode... attempted to kill init"
Might be a big oopsie?
Im able to fix that though, gonna try one more time before I just shoot the phone.
@reesespieces909
That doesn't sound very fun. Can you get it to fastboot and fastbootd? You might have to reinstall the firmware. I recommend unpacking the zip and checking what needs to be installed, could be done manually. The partition layout on newer phone can be a lot painful. Huaweis with 60-80 partitions exist and I prefer not to think about them.
DavidxxxD said:
@reesespieces909
That doesn't sound very fun. Can you get it to fastboot and fastbootd? You might have to reinstall the firmware. I recommend unpacking the zip and checking what needs to be installed, could be done manually. The partition layout on newer phone can be a lot painful. Huaweis with 60-80 partitions exist and I prefer not to think about them.
Click to expand...
Click to collapse
I can, I did, currently working to understand how to mitigate the issues Im having. Im nearing the end of my patience today, and might try this another time. Thanks for working with me.
@reesespieces909
Inside the nethunter zip could be the answer to what is happening. Has been a pleasure and good luck with your endeavour!
DavidxxxD said:
@reesespieces909
That doesn't sound very fun. Can you get it to fastboot and fastbootd? You might have to reinstall the firmware. I recommend unpacking the zip and checking what needs to be installed, could be done manually. The partition layout on newer phone can be a lot painful. Huaweis with 60-80 partitions exist and I prefer not to think about them.
Click to expand...
Click to collapse
Alright, Im currently at the part where i need to disable verity but the command isnt working thats on Magisk.
Installation
The Magic Mask for Android
topjohnwu.github.io
Im following these instruction and at "fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img"
DavidxxxD said:
@reesespieces909
Inside the nethunter zip could be the answer to what is happening. Has been a pleasure and good luck with your endeavour!
Click to expand...
Click to collapse
Ill give it a look! Edit: Didnt find anything.
Edit 2: https://www.kali.org/docs/nethunter/installing-nethunter/
Going to try step 6, I imagine Im flashing that to boot, not recovery?
@reesespieces909
Do you have the vbmeta image in your current directory? If not, paste it into the command line.
Does the boot image have a ramdisk? Should be displayed in Magisk.
DavidxxxD said:
@reesespieces909
Do you have the vbmeta image in your current directory? If not, paste it into the command line.
Click to expand...
Click to collapse
Honestly I feel kinda stupid, but I dont have an image. Is that included in the magisk apk and Im missing it or is it already in my phone?
Sorry for the dumb question. I dont see the answer on the documentation Magisk supplies.
Ah shucks...
I think Im calling it quits for now, if you have any ideas please post them here and Ill get back to you.
Thanks for your help
@reesespieces909
You can get it from the official firmware. Download from their website and extract using this tool. You should also reinstall everything to fix the os before trying again.
Always use fastbootd when working with dynamic partition, sometimes twrp cannot handle it.
Related
Hello xdadevelopers,
I recently bought myself the Poco F1 and tried to follow LTT's guide on how to make the Poco F1 like a Pixel, but I accidentally wiped everything (by going into additional settings and clicking every box). I can still access TWRP, but can't seem to install the custom rom (errors).
Is there anything I can do to continue with the process of making my phone like a pixel? I'm still a major novice in this so if possible, please use layman terms.
Thanks a lot,
Sirsitu
Hi,
I recently did the same but on purpose. This was advised in the Syberia OS ROM installation instructions. https://forum.xda-developers.com/poco-f1/development/rom-syberia-project-t3862622
You might want to try that(format data, install newest vendor+firmware etc) and then try to install a custom ROM.
SirSitu said:
Hello xdadevelopers,
I recently bought myself the Poco F1 and tried to follow LTT's guide on how to make the Poco F1 like a Pixel, but I accidentally wiped everything (by going into additional settings and clicking every box). I can still access TWRP, but can't seem to install the custom rom (errors).
Is there anything I can do to continue with the process of making my phone like a pixel? I'm still a major novice in this so if possible, please use layman terms.
Thanks a lot,
Sirsitu
Click to expand...
Click to collapse
If you're stuck you can back to stock with fastboot rom
Boot to fastboot and launch Xiaomi Flash on your pc.
SirSitu said:
Hello xdadevelopers,
I recently bought myself the Poco F1 and tried to follow LTT's guide on how to make the Poco F1 like a Pixel, but I accidentally wiped everything (by going into additional settings and clicking every box). I can still access TWRP, but can't seem to install the custom rom (errors).
Is there anything I can do to continue with the process of making my phone like a pixel? I'm still a major novice in this so if possible, please use layman terms.
Thanks a lot,
Sirsitu
Click to expand...
Click to collapse
The best thing that you can do is flash the latest fastboot stock ROM available. It'll reset the phone to as if it was new and also lock the bootloader. But you can unlock it back without the waiting time this time.
FieryAura said:
If you're stuck you can back to stock with fastboot rom
Boot to fastboot and launch Xiaomi Flash on your pc.
Click to expand...
Click to collapse
I've downloaded Xiaomi Flash and the stock rom, but when I try to flash it in, I get an error saying "can not find file flash_all_lock.bat" I think I've bricked my 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"
}
SirSitu said:
I've downloaded Xiaomi Flash and the stock rom, but when I try to flash it in, I get an error saying "can not find file flash_all_lock.bat" I think I've bricked my phone
Click to expand...
Click to collapse
Use the latest unofficial twrp, format data, wipe everything and install beta from 24/12 EU (xiaomi.eu)
Share your results afterwards
SirSitu said:
I've downloaded Xiaomi Flash and the stock rom, but when I try to flash it in, I get an error saying "can not find file flash_all_lock.bat" I think I've bricked my phone
Click to expand...
Click to collapse
Try this version its older but compatible with miflash:
http://bigota.d.miui.com/V10.0.6.0....FH_20181113.0000.00_8.1_global_ad6e716a76.tgz
SirSitu said:
I've downloaded Xiaomi Flash and the stock rom, but when I try to flash it in, I get an error saying "can not find file flash_all_lock.bat" I think I've bricked my phone
Click to expand...
Click to collapse
That't not fastboot flashable file, genius. You are trying to flash the full ROM file. Download the fastboot file which comes in .tgz format. Extract it twice and you will get the main file. Once you extract the file, you would see the file name has a lot of "underscore" (_) marks See the attached screenshot). Moreover, you didn't mention what errors are you getting on TWRP while trying to flash the custom ROM. When creating a thread, try to include as much information possible, i you want someone to understand your problem and help you accordingly. Or else, you are just adding up thread counts.
---------- Post added at 14:24 ---------- Previous post was at 14:23 ----------
123Opie said:
Try this version its older but compatible with miflash:
http://bigota.d.miui.com/V10.0.6.0....FH_20181113.0000.00_8.1_global_ad6e716a76.tgz
Click to expand...
Click to collapse
LOL! All stock fastboot ROMs are compatible on MiFlash tool. It doesn't matter which version it is as long as it is fastboot flashable and you know how to extract and place it in the correct place.
"LOL! All stock fastboot ROMs are compatible on MiFlash tool. It doesn't matter which version it is as long as it is fastboot flashable and you know how to extract and place it in the correct place."
Yeah but from what I can see on this is just a normal firmware and has to be updated thru twrp or settings.
But that older version has a fastboot version to flash idk though.
https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-unlock-bootloader-custom-t3839405
Ok I started this thread in hopes that I could get some answers from someone more knowledgeable than me on these MTK phones.
I've been reading online about flashing these GSI roms but I've seen multiple different methods. Some say use TWRP others say fastboot, or should I use SP flash tools...? And what are the proper wipes to prep for GSI flash? I've seen some say wipe everything except internal and others say just wipe dalvik/cache, and still others that say you must wipe in stock recovery then flash and boot twrp to flash system image...? Can any Umidigi Pros enlighten us a little? I'm sure google will bring more people to this page in time...or not?
I have flashed some GSI ROMs but everyone I've tried I cant seem to get root with Magisk. Magisk shows to be installed but when root apps call for root it just sits there and times out and I never get the prompt to grant root. This means I can't edit the APN which means no data which is not an option.
PS I've tried posting over in Umidigi community but it seems like a ghost town over there and I don't want to hijack any of the other threads here for our device as none of them are related to this issue.
Here also seems to be a ghost town unfortunately.....
ogeid79 said:
Here also seems to be a ghost town unfortunately.....
Click to expand...
Click to collapse
Yeah unfortunately... It's a shame such a good phone is going to waste. I blame Umidigi
razen_kain said:
Ok I started this thread in hopes that I could get some answers from someone more knowledgeable than me on these MTK phones.
I've been reading online about flashing these GSI roms but I've seen multiple different methods. Some say use TWRP others say fastboot, or should I use SP flash tools...? And what are the proper wipes to prep for GSI flash? I've seen some say wipe everything except internal and others say just wipe dalvik/cache, and still others that say you must wipe in stock recovery then flash and boot twrp to flash system image...? Can any Umidigi Pros enlighten us a little? I'm sure google will bring more people to this page in time...or not?
I have flashed some GSI ROMs but everyone I've tried I cant seem to get root with Magisk. Magisk shows to be installed but when root apps call for root it just sits there and times out and I never get the prompt to grant root. This means I can't edit the APN which means no data which is not an option.
PS I've tried posting over in Umidigi community but it seems like a ghost town over there and I don't want to hijack any of the other threads here for our device as none of them are related to this issue.
Click to expand...
Click to collapse
There are several methods to flash the GSI:
1.- BY FASTBOOT
2.- FOR A PERSONALIZED RECOVERY (TWRP)
3.- FOR FLASH TOOL.
But looks like you've already flashed them.
But you have problems with the root, this is because the libdirect-coredump.so file was installed in the vendor folder and not in the system folder.
What you have to do is the following:
/vendor/lib/libdirect-coredump.so
COPIED TO
/system/lib/libdirect-coredump.so
and
*
/vendor/lib64/libdirect-coredump.so
COPIED TO
Code:
/system/lib64/libdirect-coredump.so
drkiro said:
There are several methods to flash the GSI:
1.- BY FASTBOOT
2.- FOR A PERSONALIZED RECOVERY (TWRP)
3.- FOR FLASH TOOL.
But looks like you've already flashed them.
But you have problems with the root, this is because the libdirect-coredump.so file was installed in the vendor folder and not in the system folder.
What you have to do is the following:
/vendor/lib/libdirect-coredump.so
COPIED TO
/system/lib/libdirect-coredump.so
and
*
/vendor/lib64/libdirect-coredump.so
COPIED TO
Code:
/system/lib64/libdirect-coredump.so
Click to expand...
Click to collapse
Wow! I can't believe someone finally responded. So was this an error in the build or is there something I can do with the system image to correct it?
I still have this phone but I don't use it as my dd but I'd still like to know.
razen_kain said:
Wow! I can't believe someone finally responded. So was this an error in the build or is there something I can do with the system image to correct it?
I still have this phone but I don't use it as my dd but I'd still like to know.
Click to expand...
Click to collapse
If you have TWRP, ENTER MOUNT and mount the System partition and the vendor partition, with the TWRP file manager copy the files that I put before
I'm never able to mount anything in TWRP 3.2.3 or 3.2.3v2 on the OnePro, what am I doing wrong ?
targa said:
I'm never able to mount anything in TWRP 3.2.3 or 3.2.3v2 on the OnePro, what am I doing wrong ?
Click to expand...
Click to collapse
Are you getting errors when you attempt to mount them? They should be like "invalid argument" or something like that. In this case, you should use SP Flash Tools to flash the entire Eragon v2.5 OS with it's scatter file to your device, it -should- disable the encryption stopping you from tampering with /system and /data, and other partitions.
Also, I've been seeing people saying that you can't pass safetynet checks on the Umidigi One Pro, you can.
- Running Havoc OS 2.0
- Using Magisk v23 with modules: MagiskHide, MagiskHidePropsConfig
- Force BASIC key attestation spoofed to OnePlus 6
- Device Fingerprint spoofed to OnePlus 6
{
"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"
}
Something to note, I was not able to get the module Universal SafetyNet Fix working on the One Pro.
To be claim, i am NOT the maintianer.
Today, i want to share a GSI for every use of this phone and try to give everyone the lightest feeling of system to match the weight of this phone. So after hunders of fastboot flash, i succeesfully boot in system after flash, hope everyone can try and if any issue, you can commit this thread or pull a issue to this gsi github.
CLICK Guthub TO DOWNLOAD the "PixelExperience_Plus_arm-ab-11.0-xxxxxxxx-UNOFFICIAL.img.xz"
Three steps to flash:
1,Backup all your data and unzip the file you downloaded from github BTW.
2,If you want to get Magisk, flash Magisk before you flash PE. Without flash new bootimg, Magisk will be permanent.(option)
2,connect to computer and use command <adb reboot fastboot> or press vol- and power to rebbot to the fastboot mode.
3,use command<fastboot flash system xxx.img> to flash PEPlus, <fastboot reboot> to boot into system.
BTW, I am the people who are not native speakers of English, so if i use some wrong word, just let it go if didn't confuse you.
Hope you success.
If feedback of this rom is good, i will base on it to maintain the ROM that only for Mi11 Lite.
Thanks!
Do you mean Mi 11 Lite or Mi 11 Lite 5G??
vanpopel said:
Thanks!
Do you mean Mi 11 Lite or Mi 11 Lite 5G??
Click to expand...
Click to collapse
I flash it on my Mi 11 Lite 5G and it work.
Hi, which version to download, a only or ab??? Is there a way to debloat it before flashing??? Does it wipe data???
Thanks
So i need to download all the available img(or which one spesific) and flash them in fastboot mode and reboot system?
No need anything else right?
After boot i assume i can install magisk 23.0 apk and flash boot img created before throught fastboot right?
Is thats correct?
@ZeroSherd
rayman95 said:
Hi, which version to download, a only or ab??? Is there a way to debloat it before flashing??? Does it wipe data???
Thanks
Click to expand...
Click to collapse
Download ab version.
I don't think we con debolat it before flash
And yes it will wipe all your data.
paatha13 said:
So i need to download all the available img(or which one spesific) and flash them in fastboot mode and reboot system?
No need anything else right?
After boot i assume i can install magisk 23.0 apk and flash boot img created before throught fastboot right?
Is thats correct?
@ZeroSherd
Click to expand...
Click to collapse
You just need to download the ab verison and flash it by the command that i provide. If you need to flash magisk, i sugguest you patch the boot.img before you flash, and after the first boot you go to fastboot again to flash boot_ab that patched boot.img.
ZeroSherd said:
Download ab version.
I don't think we con debolat it before flash
And yes it will wipe all your data.
Click to expand...
Click to collapse
Thanks for your answer...what's the vndklite and is there advantage...I would like the more debloat, or with R/W....
rayman95 said:
Thanks for your answer...what's the vndklite and is there advantage...I would like the more debloat, or with R/W....
Click to expand...
Click to collapse
I did finding a way to get R/W according to patch the ROM without TWRP
ZeroSherd said:
You just need to download the ab verison and flash it by the command that i provide. If you need to flash magisk, i sugguest you patch the boot.img before you flash, and after the first boot you go to fastboot again to flash boot_ab that patched boot.img.
Click to expand...
Click to collapse
Thanks but where can i found boot.img of pe plus?
Can you provide it.
@rayman95 did you flash it ,all ok ,can provide some screenshot of the rom.
paatha13 said:
Thanks but where can i found boot.img of pe plus?
Can you provide it.
@rayman95 did you flash it ,all ok ,can provide some screenshot of the rom.
Click to expand...
Click to collapse
Of course, i will upload it to NETDISK after i finish my OT work that i may need half or A day to done it.
no, not yet....not sure to flash it right now, because I don't want to wipe my phone now....and I don't like gapps...I would love to have a recovery to flash nogoolag ur ULNP only and to do light rom
rayman95 said:
no, not yet....not sure to flash it right now, because I don't want to wipe my phone now....and I don't like gapps...I would love to have a recovery to flash nogoolag ur ULNP only and to do light rom
Click to expand...
Click to collapse
I think you can use ADB command or software to disable those GAPPS.
How do I backup the data if there is no custom recovery available?
In_a_state said:
How do I backup the data if there is no custom recovery available?
Click to expand...
Click to collapse
I highly recommand the TitaniumBackup if you got ROOT, or use MIUI backup which inside the settings.
Screenshot,feedback from the rom??
I would expect more interest for the first custom rom on this device
What's the way to go back to stock if got issues on PE???
Thanks
paatha13 said:
Screenshot,feedback from the rom??
I would expect more interest for the first custom rom on this device
Click to expand...
Click to collapse
Think most people are waiting on a working twrp recovery.
rayman95 said:
What's the way to go back to stock if got issues on PE???
Thanks
Click to expand...
Click to collapse
i didn't try, but i think just need to flash Xiaomi.eu ROM. By the "windows_fastboot_xxx" which in the ROM.
{
"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"
}
ZeroSherd said:
i didn't try, but i think just need to flash Xiaomi.eu ROM. By the "windows_fastboot_xxx" which in the ROM.View attachment 5323491
Click to expand...
Click to collapse
where do you get this???
here what I have from last EU fastboot rom...
*************************************************************
———————— TWRP for K40 Pro + ——————————-
*************************************************************
WARNING : I do not know who made this TWRP and i am NOT taking credit for it. Someone in my group chat found it. It's apparently from China. If you are the creator , PM 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"
}
INSTRUCTIONS
1) Download TWRP for K40 Pro + , and put it in your fastboot folder.
2) Put your phone into fastboot mode.
3) Do the following command : fastboot boot twrp-recovery-venus. It will automatically boot into TWRP.
4) Change language to English (press the 6th option).
5) Go to "Advanced" and select "Onekey inject TWRP".
6) Swipe to inject the TWRP. It might take a few minutes, so don't worry.
_____________________________________________________________________
Note: Don't change the boot slot (Slot A) or maybe will not boot at all.
Tested by @mslezak
______________________________________________________________________
Bugs: ADB Sideload is broken.
_______________________________________________________________
If you find any bug, feel free to report it down below.
Credits to @Cozzmy13 for decrypting the TWRP image! Here's the summary of events :
1) Chinese TWRP gets leaked onto my Telegram chat.
2) The recovery image is encoded and requires a dodgy chinese tool to decode it.
3) @Cozzmy13 finds a way to decode the image and make it bootable .
4) Me and Augustin El Metralleta try flashing the image, and we find out it works.
Does it suitable for K40 Pro? Did anyone try? Thanks!
K40 Pro has the same guts except the camera main and 12gb RAM so it should work
I verified a backup up image today restored worked although there wasn't much data on it. i always boot it. One time the injection made me have to use a fastboot ROM (always try deleting data first).
Have only one doubt can this twrp able to flash official china beta recovery rom for mi 11X pro?
#Update
I have flashed this twrp and it successfully booted without any issues and i have dirty flashed china beta recovery rom over chi a stable rom amd rom got flashed successfully without any issues.
But we need to flash the twrp every time when we reboot device.
cherri said:
How to make the twrp permanent then?
Click to expand...
Click to collapse
You can try to flash magisk after flashing the twrp, i'm still waiting the 7 days to unlock the bootloader so i can't try right now. If i remember correctly magisk has something that blocks "recovery-from-boot" and prevents twrp from being overwritten.
I think for now it is not possible are els he would have mentioned flashing process here instead of twrp temporary boot process, so we need to wait few more days unless someone does some miracle.
cherri said:
I think for now it is not possible are els he would have mentioned flashing process here instead of twrp temporary boot process, so we need to wait few more days unless someone does some miracle.
Click to expand...
Click to collapse
What do you mean. After flashing, TWRP was persistedm. I was also able to flash Magisk with this TWRP.
Go to "Advanced" and select "Onekey inject TWRP".
I wonder why there isn't any available tutorial on flashing twrp for this device on google, YouTube. What do you think guys?
thanks for the dev xinkid520 a chinese dev
It is indeed effective after testing, very good!
bouyhy01 said:
thanks for the dev xinkid520 a chinese dev
Click to expand...
Click to collapse
yeah he made it, but encrypted it and sold it for money.
so people from telegram decrypted it
zls8635878 said:
It is indeed effective after testing, very good!
Click to expand...
Click to collapse
So can we use this twrp permanently?
Can you tell me the steps if so?
DestroYerr said:
So can we use this twrp permanently?
Can you tell me the steps if so?
Click to expand...
Click to collapse
Go to "Advanced" and select "Onekey inject TWRP".
cherri said:
#Update
I have flashed this twrp and it successfully booted without any issues and i have dirty flashed china beta recovery rom over chi a stable rom amd rom got flashed successfully without any issues.
But we need to flash the twrp every time when we reboot device.
View attachment 5330171
Click to expand...
Click to collapse
I flashed this twrp into my phone. But when i try to install rom,recovery just flash and return to recovery again and ROM files got deleted. Could u tell me how u install this ROM?(PS my rom is (xiaomi.eu_multi_HMK40Pro_MI11i_V12.5.4.0.RKKCNXM_v12-11-fastboot)
Armstchi said:
I flashed this twrp into my phone. But when i try to install rom,recovery just flash and return to recovery again and ROM files got deleted. Could u tell me how u install this ROM?(PS my rom is (xiaomi.eu_multi_HMK40Pro_MI11i_V12.5.4.0.RKKCNXM_v12-11-fastboot)
Click to expand...
Click to collapse
Your rom version is for Fastboot, not Recovery.
k40 pro
majisk was installed.
I have a USB Memory Stick connected via an OTG cable, but I cannot mount it.
The usb format is FAT32. Please help someone.
cyaochai said:
k40 pro
majisk was installed.
I have a USB Memory Stick connected via an OTG cable, but I cannot mount it.
The usb format is FAT32. Please help someone.
Click to expand...
Click to collapse
Bro after flashing magisk, is safetynet okay?
Ok, so I have been experimenting and torturing this device for months now and I still love it. I have learned sooo much using this as my test bunny for all the cool custom ROMS and extra bells and whistles that it can possibly throw at it and in it. I owe it all to everyone that posts in this forum and XDA. I learned all this stuff from you,
and it has become a passion of mine now. I have experimented with other devices as well using knowledge and tools acquired here. And now here I am today.
This is my current set up:
Nord N10 5G T-mobile US Variant
I used MSM tools and some file manipulation to kill the T-mobile issue {evil grin} thanks to "some random username: and "Kronflux"
* =sorry fellas if I goofed up your nicks
I installed a stable working release of Android 12 running on a Pixel 5 GSI from ErfanGSI.Tools
I am rooted thru Magisk 23 using a *PE boot image and flashed patch thru Platform tools (the old school method)
I use Nova Prime Beta as a launcher
*does not pass safety net but can run and use most all mods work
It runs very smooth, however Chrome does *not work yet all other Google crap seems to be fine.
5G LTE works. and there is a hardware error on bootup, but it doesn't flake out.
Battery life is terrific, and it doesn't get hot.
No camera app with this GSI but I have an app I prefer, and it performs perfect.
90hz refresh has to be forced in dev options.
No SD access from PC only access thru device
All the sudzie powers of Hell and Android 12 work perfectly.
Overall this build is great, and it's running Android 12!! A12 is not going to be awarded the chance to run officially on this device so it makes me happy to run it "our way"!
All software install and mods were performed using the newest Platform tools with ADB and fastboot. Also, I used the latest lineage recovery during the setup.
No TWRP, no sideloads. This is a GSI not a ROM.
Again, big thanks to you all for making these things available.
#XDA rocks!
{
"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"
}
Please post installation method and link to GSI
umaga2012 said:
Please post installation method and link to GSI
Click to expand...
Click to collapse
Simple method
MSM tools device reset to A10
flash unlock token/ oem unlock/ unlock bootloader
**CLEAN FLASH!!!!!!
fastboot -w erase userdata and erase system_a/b
flash lineage recovery (can be found by searching in XDA recovery_a and recovery_b
download and extract GSI **see op about what GSI was used and searches I can't provide links
flash system_a and system_b
factory reset in lineage recovery
reboot
done
If for some reason it doesn't work you can pull the vendor.img and perhaps boot.img from stock OS, erase/and flash them. Retry booting GSI after that.
You can root with Magisk 23 by using boot.img from PE A11 version and flash patched image
Spidermonkeyj75 said:
Simple method
MSM tools device reset to A10
flash unlock token/ oem unlock/ unlock bootloader
**CLEAN FLASH!!!!!!
fastboot -w erase userdata and erase system_a/b
flash lineage recovery (can be found by searching in XDA recovery_a and recovery_b
download and extract GSI **see op about what GSI was used and searches I can't provide links
flash system_a and system_b
factory reset in lineage recovery
reboot
done
If for some reason it doesn't work you can pull the vendor.img and perhaps boot.img from stock OS, erase/and flash them. Retry booting GSI after that.
You can root with Magisk 23 by using boot.img from PE A11 version and flash patched image
Click to expand...
Click to collapse
Do you know how exactly you could update once you do get the GSI installed? Sorry I'm new to this whole GSI and Treble thing...
JazzieBoi said:
Do you know how exactly you could update once you do get the GSI installed? Sorry I'm new to this whole GSI and Treble thing...
Click to expand...
Click to collapse
Gsi don't update, you have to flash a new version of it through the same method if an update is available.
ninjasinabag said:
Gsi don't update, you have to flash a new version of it through the same method if an update is available.
Click to expand...
Click to collapse
So far as I can tell you have to flash a new OS/GSI every time a new update is released. It's a bit of a pain in the ass , but it's worth the effort once you have the main GSI established it's easy to build off that.
Spidermonkeyj75 said:
So far as I can tell you have to flash a new OS/GSI every time a new update is released. It's a bit of a pain in the ass , but it's worth the effort once you have the main GSI established it's easy to build off that.
Click to expand...
Click to collapse
Okay well wouldn't that mean you'd have to wipe userdata (internal storage) everytime you want to update it?
JazzieBoi said:
Okay well wouldn't that mean you'd have to wipe userdata (internal storage) everytime you want to update it?
Click to expand...
Click to collapse
No, you can skip the formatting phase from what I've gathered.
ninjasinabag said:
No, you can skip the formatting phase from what I've gathered.
Click to expand...
Click to collapse
Oh that doesn't so bad, I was thinking of giving it a shot when I get some downtime. Is it very difficult to go back to OxygenOS? Im assuming if I get stuck I could just flash back to stock using MSMtool?
JazzieBoi said:
Oh that doesn't so bad, I was thinking of giving it a shot when I get some downtime. Is it very difficult to go back to OxygenOS? Im assuming if I get stuck I could just flash back to stock using MSMtool?
Click to expand...
Click to collapse
Not difficult at all using the msmtool. Just takes time.
Running tiramisu A13 dev preview on the same OPN105G
Spidermonkeyj75 said:
Running tiramisu A13 dev preview on the same OPN105G
Click to expand...
Click to collapse
Could you share which A13 dev preview? Pixel 4, 5,etc. I would love to give it a try. Thanks.
sure