Question Pretty much confused (Need Help) - Google Pixel 6

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....

Related

SCH-i500 Bricked

Hello everyone; I've been desperately attempting to get CM7 installed on my Samsung Fascinate since its release, and I have been unable to do so despite it being 'so very easy'. Today I had installed CM10 on my HP touchpad with zero issues, so I decided to attempt to install CM7 on my Fascinate again.
While following this tutorial (http://forum.cyanogenmod.org/topic/32474-cyanogenmod-7-for-the-samsung-fascinate-v710-9-oct-2011/) I came across a step that 'bricked' my phone. Below are the steps that I was required by the tutorial to take:
Root the device and install ClockworkMod Recovery. Instructions are available here.
My phone had been previously rooted; I purchased, downloaded and flashed ClockworkMod Recovery onto my phone successfully.
Perform a NANDroid backup of your current ROM.
I elected NOT to do a NANDroid backup; my phone was cluttered and I decided that if things wen't wrong, I'd like to reboot into a factory reset phone and re-root from scratch (where inlies my issues).
Format the system, data & cache partitions of your device.
I did, successfully.
Perform a factory reset.
This is the last step in which I was able to complete (for obvious reasons) after the factory reset was complete, however, I was UNABLE to get into download mode to be able to finish the ClockworkMod Recovery (all files for CM7 are still on my SD card ready to go). However, upon rebooting my phone I've noticed that my home screen manager does NOT function, and I am unable to navigate within my phone. It does NOT launch when I hit my home button, and I've been unable to do anything else with my phone.
Flash CyanogenMod.
I was unable to get to this step.
Optional: Install the Google Apps addon package.
I was unable to get to this step.
Being a tech geek, I would not open a thread unless I've exhausted all options at my disposal; A quick Google search resulted in this thread (http://forum.xda-developers.com/showthread.php?t=1026746) in which I was sure I'd be able to get my phone working again. However, the files associated with it (EB01All in 1) are no longer hosted at the links provided. An extensive Google search yielded no results.
What I'd like to be able to do is to get my phone operational to the point where I can continue with the installation of CM7. Any and all help that you can provide would be greatly appreciated.
Thanks!
I would use section 4 of that guide by droidstyle
And flash a jelly bean 4.2.x Rom
.
hhp_211 said:
I would use section 4 of that guide by droidstyle
And flash a jelly bean 4.2.x Rom
.
Click to expand...
Click to collapse
From what I can gather by your post, you're suggesting that I use section 4 of this tutorial: http://forum.xda-developers.com/showpost.php?p=17050028
In which I would not be able too, considering almost all of the pertinent files that were uploaded for use cannot be found, and are no longer hosted. Anything else?
=========================
Update:
By some sort of miracle I was able to get my phone into download mode by using the SDK command; as of now I'm loading up CI500_VZW_EH03_GB_CM.tar.md5 as you've suggested. I'll update this post again once the process is complete.
zQueal said:
From what I can gather by your post, you're suggesting that I use section 4 of this tutorial: http://forum.xda-developers.com/showpost.php?p=17050028
In which I would not be able too, considering almost all of the pertinent files that were uploaded for use cannot be found, and are no longer hosted. Anything else?
Click to expand...
Click to collapse
okay so, why did you root the phone? that was an extra step that was unneeded. you just had to flash cwm_fix_cm7 or whatever and then boot into cwm and flash cm7. also, I'd flash EH03, that's gingerbread, you don't have to go back all the way to EB01 or whatever, no need to. and lastly, you shouldn't of factory reset it. it sounds to me like you have soft bricked it, does it boot up, even with errors? if you can bout it, try powering it off and then take out the battery and the SD card, then hit the vol - and power and it should boot into download mode. (also put the usb into the port and phone before) but like hhp said I'd go read droidstyles guide
What I don't get is why you'd want to use CM7 when there's a ton of great 4.2 roms available for the Fascinate (including CM10.1) that run very nicely
Crawshayi said:
What I don't get is why you'd want to use CM7 when there's a ton of great 4.2 roms available for the Fascinate (including CM10.1) that run very nicely
Click to expand...
Click to collapse
So far I've been unable to find any, which is why I was under the impression that I would be required to use CM7; if possible, could you link me to the files necessary?
zQueal said:
So far I've been unable to find any, which is why I was under the impression that I would be required to use CM7; if possible, could you link me to the files necessary?
Click to expand...
Click to collapse
Come on now ,, section 4 has all the info you need...
{
"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"
}
When you are done there look in the development section
.
The only rom you won't find here is CM10.1 which can be found over at rootzwiki
Thread closed
Situation has been resolved per the OP.

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

Umidigi One Pro Q&A/Discussion/Project Treble

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.

Updating firmware while unlocked/rooted/TWRP

SM-T860 that is unlocked, rooted with Magisk, TWRP recovery installed, WETA Kernel installed, running ASK1 November security update firmware.
I'm not new to rooting and all, but am fairly new to Samsung devices and am still learning all the tricks and tips.
I know that OTA updates are not possible in my current state, but Is it possible to some way manually update the firmware to the ASL3 version without having to just reflash stock and loose everything, starting from scratch to reroot, TWRP, reinstall all my apps etc?
I already have Odin installed and have downloaded the full ASL3 firmware package.
You don't have to lose everything - just flash ASL3 on top of ASK1, then install the rest of the mods (WETA kernel, TWRP, Magisk). In the downloaded zip of ASL3, you should have five files: mostly the same file names, except for the beginning few characters, similar to this:
{
"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"
}
So the five images you'll most likely have are AP (the main system + boot.img), BL (bootloader, modem, other low level stuff), CP (other small tidbits), CSC (carrier-specific customizations, also contains country-specific stuff, basically the layer above system that makes the OS specific to a country, with apps, configurations for WiFi, 4G/5G, Bluetooth, and even things like Samsung Pay), and HOME_CSC (same as CSC, but doesn't flip the "wipe device" flag).
What you need to do is do the update via ODIN using the default files, then for the CSC field, select HOME_CSC instead of the regular CSC file. The only difference between the two is just this, HOME_CSC won't wipe the device, CSC will.
Same applies if you want to go back to complete stock, just flash the phone using ODIN, and use the regular CSC image instead of HOME_CSC.
Thank you for the detailed explanation of what to try and what all of the different parts of the big firmware packages are. I've had this Tab S6 just about a month now and have been doing my best to get used to how Samsung does things. Lots of reading various posts, lots of experimenting. I've gotten the basics down on flashing firmware using Odin, but don't yet have a solid grasp on what all is really going on. I've just been very carefully following directions, and praying to the Android/Samsung gods I don't end up with a brick when I hit "start." LOL So far so good!
I'll give it a go doing what you described. If it works, Yay! If not, no big deal and I'll start over from fresh/stock. I've grown used to that being "just the way it is" when you want to run modified/custom stuff. As long as I don't permanently brick the thing I do enjoy the experimenting and learning process.
Thanks again.
ragtop429 said:
Thank you for the detailed explanation of what to try and what all of the different parts of the big firmware packages are. I've had this Tab S6 just about a month now and have been doing my best to get used to how Samsung does things. Lots of reading various posts, lots of experimenting. I've gotten the basics down on flashing firmware using Odin, but don't yet have a solid grasp on what all is really going on. I've just been very carefully following directions, and praying to the Android/Samsung gods I don't end up with a brick when I hit "start." LOL So far so good!
I'll give it a go doing what you described. If it works, Yay! If not, no big deal and I'll start over from fresh/stock. I've grown used to that being "just the way it is" when you want to run modified/custom stuff. As long as I don't permanently brick the thing I do enjoy the experimenting and learning process.
Thanks again.
Click to expand...
Click to collapse
Please tell me how it goes!
Daniel Hjelvik said:
Please tell me how it goes!
Click to expand...
Click to collapse
Well, it worked... sort of. The system booted and ran, but I started to get random reboots for no apparent reason. I wiped cache and such but nothing helped.
Ultimately I decided to completely wipe the tablet, flash back to stock, and then reroot and just reinstall everything "clean."
Did you apply TWRP and the WETA kernel again? If so, my gut is that the old kernel is not compatible with the updates. Just my thoughts, nothing to support this but an update should work. This is one of the reasons I am waiting till the updated TWRP is released with the new SL3 kernel.

Need complete updated guide to root and update Asus z580ca to newer Android version

Hello! Im new to XDA. I am needing a complete guide(s) so I can root my Asus z580ca table. I have been looking for weeks on various forums (including this one) and I have found some old guides that are very confusing. I am not new to rooting, jailbreaking or installing CFW on gaming units but trying to find a cohesive guide on this topic has been daunting. I have tried to root my Asus using KingRoot.apk but no luck. I get stuck on 1% when trying to root. My Asus is on Android 5.0. My goal is to root and update the Android firmware to a more recent version like Android 9 or 10. I appreciate any assistance I can get on this!!
To update Android it's not needed to get it rooted, but to find a
1. Custom Recovery suitable to your Asus device
2. Custom ROM suitable to device, what is to be flashed via Custom Recovery you found
Thanks for the reply! So how do I go about finding a custom recover suitable to my Asus device? How do I go about finding a custom ROM suitable for my Asus Device. Again I'm Looking for a guide on how to do this.
{
"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"
}
ok so I go to Google and find a Custom Recovery and Rom File....what next? Again Im needing a guide on this please or to be pointed in the direction of a guide.
Well I Googled and look it has XDA at the top of the list. So thank you for the answer or lack there of lol Insert dog chasing his own tail here . The thread dated from 2016 does not have a working link for the ROM that I MAY need. Any other suggestions?
FosterThePeople said:
Hello! Im new to XDA. I am needing a complete guide(s) so I can root my Asus z580ca table. I have been looking for weeks on various forums (including this one) and I have found some old guides that are very confusing. I am not new to rooting, jailbreaking or installing CFW on gaming units but trying to find a cohesive guide on this topic has been daunting. I have tried to root my Asus using KingRoot.apk but no luck. I get stuck on 1% when trying to root. My Asus is on Android 5.0. My goal is to root and update the Android firmware to a more recent version like Android 9 or 10. I appreciate any assistance I can get on this!!
Click to expand...
Click to collapse
First, welcome here.
Second, I'm not sure why you have to bring all those statements "I'm not new to rooting, bla, bla" while to me, you're completely clueless, not even remotely can differentiate between rooting and updating your device. If you are really new to some area, take my advice, just don't try to show off. It's not a shame to confess that you don't know anything about it nor have any experience nor expertise in that area yet. Just be honest.
And now, for the answer to your question:
At this point I would just rather advice you to sell your device and move to another new one. Why? There's several reasons.
First reason is, unfortunately your device isn't popular enough to have a community to share knowledge or the works they've been working on. Why? Because a lot depends on that.
Before doing anything else, you'll need to unlock the bootloader of your device. If there's no official manual to do so from Asus, usually you'll be dependent on the community for help, unless you can find it the way yourself. Now, even if you have somewhat find a way to do it, there's second part.
The second part is: the device was released before so called "treble" mechanism implemented, thus giving you another hurdle. "Treble" allow you at least override just the system partition without messing with anything else. Newer devices that were released with Android 8 or above, cmiiw, naturally has it implemented. Why is this important? In case you can't any specific custom roms tailored for your device, "treble" accepts GSI which allows you to try another OS without other heavy duty stuff. Without treble support, literally you'll have to build a complete custom rom. I see Asus has provided the device kernel, so technically it's very possible to do so (although it might lack techpack, etc).
That's all covers about installing roms. Recovery isn't mandatory to install rom, unless your device lacks of fastboot (Samsung) or their fastboot borked (Oppo, Vivo).
Upgrading to another version is different topic. Rooting is also a very different topic.
FosterThePeople said:
ok so I go to Google and find a Custom Recovery and Rom File....what next? Again Im needing a guide on this please or to be pointed in the direction of a guide.
Click to expand...
Click to collapse
A Custom Recovery ( TWRP ) obviously not available
Asus
This is the Team Win website and the official home of TWRP! Here you will find the list of officially supported devices and instructions for installing TWRP on those devices.
twrp.me

Categories

Resources