Umidigi One Pro Q&A/Discussion/Project Treble - Android Q&A, Help & Troubleshooting

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.

Related

Accidentally Wiped Everything with TWRP

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

E Signature verification failed / failed to verify whole-file signature on SM-G318H

Hi sorry if i post in bad section so i need help i downloaded an CWM ClockWorkMod Recovery for SM-G318H Samsung Galaxy Trend 2 lite i apply the update so it was almost done but an error marked in red and reboot after update failure.
Any suggestion it happens with any zip file for Temp Recovery i have here an picture :crying:
I Attached an picture with the failure so if you have any suggestion reply there.
P.S. I Don't trust changing permanent recovery and even download mode odin.
@AlinTecsan
You used phone's Stock Recovery to flash something other than the phone's signed Stock ROM. Hence you got "E: signatue verification failed" error.
Flashing CWM on stock recovery
jwoegerbauer said:
@AlinTecsan
You used phone's Stock Recovery to flash something other than the phone's signed Stock ROM. Hence you got "E: signatue verification failed" error.
Click to expand...
Click to collapse
This i know so i try flashing the CWM so this not work so to sign the custom recovery with signed stock rom so how i fix thanks for replying
@AlinTecsan
Look inside here.
Looked Here
jwoegerbauer said:
@AlinTecsan
Look inside here.
Click to expand...
Click to collapse
I Looked here so fastboot it flash and erase sorry so my phone will not support the advanced boot options and no match found for my model at all so thanks again for the link
Use TWRP instead of CWM
@AlinTecsan
It’s true that CWM Recovery is a widely used recovery, but it’s not anymore in the league, now it’s TWRP all the way up with no contender around!
Since the software company which developed CWM Recovery has stopped building its versions anymore, there are no new releases of CWM Recovery released within the last 5 years what are ready to be used on mainstream Android devices.
Take note that TWRP can get successfully flashed on A/B systems.
TWRP Will work for my device?
jwoegerbauer said:
@AlinTecsan
It’s true that CWM Recovery is a widely used recovery, but it’s not anymore in the league, now it’s TWRP all the way up with no contender around!
Since the software company which developed CWM Recovery has stopped building its versions anymore, there are no new releases of CWM Recovery released within the last 5 years what are ready to be used on mainstream Android devices.
Take note that TWRP can get successfully flashed on A/B systems.
Click to expand...
Click to collapse
Does have what have cwm?Like factory reset apply update from sdcard sideload cache wipe reboot and change theme i would like to try hope the file is compatibile with my device before to start i will backup the stock recovery :good:
AlinTecsan said:
Does have what have cwm?Like factory reset apply update from sdcard sideload cache wipe reboot and change theme i would like to try hope the file is compatibile with my device before to start i will backup the stock recovery :good:
Click to expand...
Click to collapse
{
"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"
}
I Flash an 2.8.7.0 TWRP
jwoegerbauer said:
Click to expand...
Click to collapse
It work fine so i need to change to red if possible so work good so i sent pictures soon I like to know how i restore the stock recovery i backup the whole firmware so i like to change to red .TWRP Work with all devices?
@AlinTecsan
You have to re-flash device's Stock ROM to get device's Stock Recovery back.
Stock ROM And recovery
jwoegerbauer said:
@AlinTecsan
You have to re-flash device's Stock ROM to get device's Stock Recovery back.
Click to expand...
Click to collapse
I have to say i extract from my correctly firmware code the recovery.img so i will made an tar file or i guess to restore recovery stock in case of problem so i know with .tar.md5 backups.

General [SHARED] [TWRP] [haydn] TWRP Recovery for K40 Pro +

*************************************************************
———————— 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?

So Im stuck in a soft brick....

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.

Question Pretty much confused (Need Help)

Hi guys, after coming from Xiaomi Mi6 I have now Pixel 6, I m aware of flashing running adb and unlock Bootloader, but here I see three threads and m so confused what to do, Regarding unlock bootloader and root twrp safety net etc, so the real question is why there are so many files? And does Pixel Flash Tool resolve all this problem by automatically doing its job?
Here is the confusion
Wow what all this? What is initial root /create master root image >> ok if this is an basic root and problem can be solved then what is this update and root automatic ? Root ota sideload?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP is not available for the Pixel 6 series, so forget about TWRP.
The one and only page you should need to do whatever you need to is at https://forum.xda-developers.com/t/...ootloader-update-root-pass-safetynet.4356233/ . You literally only need ADB, Magisk, and a copy of the boot image to be able to root your device. The Displax variant of the safetynet fix is optional, but if you intend on using your device for tap-to-pay you'll need to install it.
Flashing tools like the Pixel Flash Tool may simplify the process, but you would be best served learning to do it manually first so you can see and understand what is happening in real time. After you see how an update processes you can, if comfortable, go ahead and use a flashing tool.
What is update and Root Automatic OTA??
Further I see Update and Root Factory Image??
Do I need to do all those Steps mentioned? Are they necessary? Except the safety net part which u have already told...
Strephon Alkhalikoi said:
TWRP is not available for the Pixel 6 series, so forget about TWRP.
The one and only page you should need to do whatever you need to is at https://forum.xda-developers.com/t/...ootloader-update-root-pass-safetynet.4356233/ . You literally only need ADB, Magisk, and a copy of the boot image to be able to root your device. The Displax variant of the safetynet fix is optional, but if you intend on using your device for tap-to-pay you'll need to install it.
Flashing tools like the Pixel Flash Tool may simplify the process, but you would be best served learning to do it manually first so you can see and understand what is happening in real time. After you see how an update processes you can, if comfortable, go ahead and use a flashing tool.
Click to expand...
Click to collapse
[email protected] said:
What is update and Root Automatic OTA??
Further I see Update and Root Factory Image??
Do I need to do all those Steps mentioned? Are they necessary? Except the safety net part which u have already told...
Click to expand...
Click to collapse
Update and root factory / OTA images only applies if you have already rooted, thus the word "update". And yes, all the steps given are required. Read them, digest them, and read them again. That thread will save you a lot of headaches.
Strephon Alkhalikoi said:
Update and root factory / OTA images only applies if you have already rooted, thus the word "update". And yes, all the steps given are required. Read them, digest them, and read them again. That thread will save you a lot of headaches.
Click to expand...
Click to collapse
Yes I will try... Many devices have simple steps tp follow... I guess... Although there is no twrp then how come roms are flashing via adb if there no recovery..
@[email protected], please excuse pholdemulpti; it is fairly obvious the reply is an A.I. generated reply and involves/includes wrong and/or incomplete information -- so please be wary of taking the advice in the post and proceed being aware of the risk.
pholdemulpti said:
As for the Pixel Flash Tool, it is a tool developed by Google to simplify the process of flashing firmware and images on Pixel devices. It can be used to install stock firmware, unlock the bootloader, and flash custom images like TWRP. However, it's important to note that using the Pixel Flash Tool may still require some knowledge and experience with Android modding, and it may not work for all devices or scenarios.
Click to expand...
Click to collapse
First, if you really are speaking on the tool Google develops, it is called Android Flash Tool, not "Pixel" -- no such thing; a simple Google search shows it. And it does not flash "custom images like TWRP", and requires just the basic "knowledge and experience with Android modding".
Second, there is a tool called PixelFlasher developed by badabing2003 (not Google), which does flash custom images (ROMs, patched [Magisk] boot images, both slots, etc.), and has further checks & protocols (using the version of platform-tools that does not have fatal bugs for Pixel 6+) which works on all Pixels.
I'm fairly certain whatever A.I. generated tool/service being used is simply combining the two "tools" as they are similar and apply/relate to similar devices....
pholdemulpti said:
In terms of the "initial root" and "master root image" files you mentioned, it's possible that these are custom rooting packages designed for your specific device or software version. However, it's difficult to say without more information or context. Similarly, the "update and root automatic" file may be an automated rooting package, but it's important to research and verify the source and compatibility of any files before using them.
Click to expand...
Click to collapse
Orange text is pretty clear showing this is an A.I. generated response; "more information or context"? The rest of us that has read this thread got what OP meant....

Categories

Resources