Related
Hello,
First of all I'm glad that finally joined this forum. Been browsing it for a while and checking for roms for my phone. Anyway there's one problem that i can't solve it. Tried searching information about it online but haven't found anything.
Recently i bought a chinese tablet, and seller gave me also newest rom for it so I can install it (didn't had any problems installing roms before). The thing is the format of a file is "tar.gz". The seller tells me there's a "tool" which he would send me (waiting for a month already) to install this rom. Is there any real tool or a guide how to install tar.gz rom?
I will put screen of what contains inside
Hope anyone can help me with it.
Kind regards
Normally you would use Odin to install a tar.gz, but Odin is a tool for Samsung. Probably this thing has some proprietary flashing tool.
You might be able to extract the file and manually flash the IMG files using fastboot, but you better be 100% sure this ROM is legit for your device or you risk brick when flashing certain elements.
you need to use sp flash tool. make a backup of your rom first! i know those chinese chipsets, for further informations just pm me.
Chrizzly92 said:
you need to use sp flash tool. make a backup of your rom first! i know those chinese chipsets, for further informations just pm me.
Click to expand...
Click to collapse
Yeah those Chinese chipsets can get pretty confusing sometimes.
Good thing someone knows about them..
Sent from my Nexus 5 using Tapatalk
nah, they are not that complicated. basically, they are partitioned in basic parts: preloader, uboot, dsp_bl and other specific stuff. for a firmware update, you basically need to lash android partition and boot.img partition. this can be done via flashtool, fastboot, metamode, recovery o you can dd from sdcard, of you are already rooted. also, these devices are unbrickable i you do not touch preloader . if you do, mostly they can set into download mode shortening 2 pins on motherboard. flashing my galaxy s is harsee in my oppineon.
Chrizzly92 said:
nah, they are not that complicated. basically, they are partitioned in basic parts: preloader, uboot, dsp_bl and other specific stuff. for a firmware update, you basically need to lash android partition and boot.img partition. this can be done via flashtool, fastboot, metamode, recovery o you can dd from sdcard, of you are already rooted. also, these devices are unbrickable i you do not touch preloader . if you do, mostly they can set into download mode shortening 2 pins on motherboard. flashing my galaxy s is harsee in my oppineon.
Click to expand...
Click to collapse
Yeah flashing the img files via fastboot isn't hard, it's knowing which tool they expect you to use for which device / chipset.
Either way, hope he got his situation sorted.
Thank you for your answers hope to solve this problem. I tried to rename tar.gz to zip and install it that way. And somehow i managed to install it (somehow) with some errors, but still there's missing something haha
Ok so i finally managed to install rom. That Chinese guy gave me Sp flash tool. Choosed scatter pressed download and vuala. Works great! If anyone need guide or that tool just pm me
dear i m looking for flash tool for chinese tablet please send me or put for download
---------- Post added at 05:50 AM ---------- Previous post was at 05:44 AM ----------
orangekid said:
Yeah flashing the img files via fastboot isn't hard, it's knowing which tool they expect you to use for which device / chipset.
Either way, hope he got his situation sorted.
Click to expand...
Click to collapse
if you have please send me flash tool for chinese mobile
I've got the same problems too,,,
I'll try some, from this thread. hope it works. thanks...
SoC? Device? ROM? more informations needed to help you out guys!
only because its chinese doesn't mean every flashtool will work.
I was curious as to any difference between flashing a Kernel via ADB using a boot.img or flashing it as a .zip via recovery. Is there a benefit of one over the other. I've always done it via ADB, but I recently tried via a zip file through TWRP but didn't notice any difference, but wasn't sure if I was just being oblivious or not lol
I heard someone mention that when flashing it via ADB you don't get the Modules that come with the Kernel. Which I don't know if that was BS or not, cause as I stated, after trying it both ways, I didn't notice any features taken away i.e. flashed bricked kernel via ADB and then restored stock kernel and then flashed bricked via TWRP, and I was able to activate DT2W/S2W regardless of the method of flashing, as well as OC capabilities, Fast Charge, etc etc.
Just been curious about this for awhile, and there doesn't seem to be much discussion about it, so was unable to find an answer. Dev's always seem to give you the option to download a boot.img or .zip file, and wasn't sure if htat was just due to giving peopel the choice of preferred flashing method, or because of inherit benefits between the two.
Its simply 2 different options of installation. The final result is the same: a boot.img gets extracted and written onto the appropriate partition of your device.
When you use fastboot to flash the img. the executable on your computer does this directly.
When you use a recovery to flash the zip (which also contains the boot.img), the edify script within the zip gives instructions to the recovery on how and where to write the image to.
There isnt really any advantage to doing one over the other.
Silicon Knight said:
I was curious as to any difference between flashing a Kernel via ADB using a boot.img or flashing it as a .zip via recovery. Is there a benefit of one over the other. I've always done it via ADB, but I recently tried via a zip file through TWRP but didn't notice any difference, but wasn't sure if I was just being oblivious or not lol
I heard someone mention that when flashing it via ADB you don't get the Modules that come with the Kernel. Which I don't know if that was BS or not, cause as I stated, after trying it both ways, I didn't notice any features taken away i.e. flashed bricked kernel via ADB and then restored stock kernel and then flashed bricked via TWRP, and I was able to activate DT2W/S2W regardless of the method of flashing, as well as OC capabilities, Fast Charge, etc etc.
Just been curious about this for awhile, and there doesn't seem to be much discussion about it, so was unable to find an answer. Dev's always seem to give you the option to download a boot.img or .zip file, and wasn't sure if htat was just due to giving peopel the choice of preferred flashing method, or because of inherit benefits between the two.
Click to expand...
Click to collapse
Fastboot is the tool to which you are referring to, not ADB. You use fastboot to flash image files to partitions directly through the bootloader. That being said, there's no difference which method you use, the end result is the same. Using fastboot requires an unlocked bootloader, flashing through the recovery does not. When you flash a zip through the recovery, the proper destination partition is automatically overwritten whereas when you flash an image in fastboot, you have to specify the proper partition. That's the only real difference.
Excuse me, Fastboot is what I meant yes. My bad lol.
Thanks for the info, I figured as much. Im experienced with both methods and understand how they work. Just wasn't sure if there was a benefit over one or the other when it comes to flashing custom kernels. Thanks bro I appreciate the help. I will stick to flashing via fastboot then. I just prefer to do it that way.
I also use flashify sometimes as well. Seems to work pretty good.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Chromium_ said:
Its simply 2 different options of installation. The final result is the same: a boot.img gets extracted and written onto the appropriate partition of your device.
When you use fastboot to flash the img. the executable on your computer does this directly.
When you use a recovery to flash the zip (which also contains the boot.img), the edify script within the zip gives instructions to the recovery on how and where to write the image to.
There isnt really any advantage to doing one over the other.
Click to expand...
Click to collapse
i have a locked bootloader but i have root, can i "flash" throught root explorer overwriting boot.img file?
and reboot?
AXD96 said:
i have a locked bootloader but i have root, can i "flash" throught root explorer overwriting boot.img file?
and reboot?
Click to expand...
Click to collapse
Root explorer is not a flashing tool and no, it cannot modify the kernel
Sent from my Nexus 5 using Tapatalk
rootSU said:
Root explorer is not a flashing tool and no, it cannot modify the kernel
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
maybe a stupid question, but the kernel is all saved in boot.img?
AXD96 said:
maybe a stupid question, but the kernel is all saved in boot.img?
Click to expand...
Click to collapse
Yep Indeed. What you can browse is /sys, which are the "files" the kernel manipulates to do what it wants...
..but browsing here is of no benefit to changing a kernel
Sent from my Nexus 5 using Tapatalk
Unlock your device and just use the a custom recovery.
Sent from my Nexus 5 using Tapatalk
can we change kernel alone
i am using SENSONIC with stock kernel can i change kernel alone.
I want to change to franco kernel . Is it enough installing zip using recovery or i have to do fresh install of the ROM.........
Thanks in advance.
Links attached for those interested from Essential Web Site, and source.android.
https://support.essential.com/hc/en-us
https://source.android.com/source/running
The real question is kernel source. Not much reason to unlock the bootloader without that.
Goronok said:
The real question is kernel source. Not much reason to unlock the bootloader without that.
Click to expand...
Click to collapse
Exactly.
I'm not holding my breath.
I think I'm jumping ship.
thought Magisk works now with just an unlocked bootloader... or was it the other way around... lol
*edit*
Via Magisk Manager (Only support v14.0+):
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and also be able to flash the patched boot image, either through fastboot/download mode or ODIN
Guess we'll need some patched boot image... which I'm assuming no one has yet... lol
gqukyo said:
thought Magisk works now with just an unlocked bootloader... or was it the other way around... lol
*edit*
Via Magisk Manager (Only support v14.0+):
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and also be able to flash the patched boot image, either through fastboot/download mode or ODIN
Guess we'll need some patched boot image... which I'm assuming no one has yet... lol
Click to expand...
Click to collapse
Magisk manager will patch the boot image when installing magisk 14.0
We just need the boot.img from the rom or the OTA before it installs.
drocny87 said:
Magisk manager will patch the boot image when installing magisk 14.0
We just need the boot.img from the rom or the OTA before it installs.
Click to expand...
Click to collapse
That's IF You can access the OTA zip. A lot of times it's downloaded to /cache which is not accessible without root. Some OEM's have it downloaded to the SD card but most bigger OEM's have it downloaded to the cache partition
graffixnyc said:
That's IF You can access the OTA zip. A lot of times it's downloaded to /cache which is not accessible without root. Some OEM's have it downloaded to the SD card but most bigger OEM's have it downloaded to the cache partition
Click to expand...
Click to collapse
Some people got the update today. If you happen to get it can you try to pull the boot?
I have the update waiting to be installed.
graffixnyc said:
That's IF You can access the OTA zip. A lot of times it's downloaded to /cache which is not accessible without root. Some OEM's have it downloaded to the SD card but most bigger OEM's have it downloaded to the cache partition
Click to expand...
Click to collapse
in the build thread, a user was able to capture the OTA url. the only issue, the boot.img is stored in the payload.bin file. Are you familiar with this file and how to extract it?
So is this phone rootable?
Sent from my SM-G950U using XDA-Developers Legacy app
canynballa said:
So is this phone rootable?
Click to expand...
Click to collapse
At this time no. Hopefully soon that will change.
In the Andy Rubin AMA, the official Essential reddit account posted that the kernel and factory images would be released to the public "in the next few days". That probably means next week, business days and all, but it looks like they fully intend to support external development of this phone, and soon. Makes sense--why else would they allow a bootloader unlock from the get-go?
In adb I can find my phone but once I adb reboot bootloader and fastboot devices it doesn't display. Plz help
Sarzeck said:
In adb I can find my phone but once I adb reboot bootloader and fastboot devices it doesn't display. Plz help
Click to expand...
Click to collapse
You need to select correct driver in device manager, maybe even install different drivers
See
https://forum.xda-developers.com/es...nofficial-usb-drivers-essential-ph-1-t3678231
Sent from my PH-1 using Tapatalk
Thanks buddy! It worked
i love unlocking bootloader on mine but for now until no ROM's mod i will stay locked mode. im a Android Pay dude lol
Does anyone have any advice for getting the phone recognized. I installed android studio and google usb drivers. I've unlocked bootloaders on onepluses before but nothing happens when I type fastboot devices, and it stays at "waiting for any device" when I try the unlock command.
Yeah, try another computer. Seriously, my main PC just didn't want to work with the phone. Used my laptop, worked fine. Can't think of anything different, both are Win10, both have the same drivers and sdks. Both work for my other phones, just not this one. Didn't hurt to try. Of course you'll need access to another computer but if you have one or more extras, worth a try. Worked for me.
oowaymike said:
Does anyone have any advice for getting the phone recognized. I installed android studio and google usb drivers. I've unlocked bootloaders on onepluses before but nothing happens when I type fastboot devices, and it stays at "waiting for any device" when I try the unlock command.
Click to expand...
Click to collapse
Did you reboot the computer? I've seen that help alot when device is not recognize
I'm having same issue, flashing unlock command do not work. I am on the oreo beta version. Someone help please.
I know that I probably won't get any help since this is a budget phone from a random company, but has anyone figured out how to get Android 10 on the phone? If not, does anyone know how to install Magisk or root this phone? I've read threads on how to install it, but they don't list this phone as supported. TWRP doesn't support Hot Pepper Ghost so how can I install Magisk? Kingoroot doesn't let me root the phone, so what is another way?
Because this phone is based on MediaTek MTK6762 chipset watch this video:
jwoegerbauer said:
Because this phone is based on MediaTek MTK6762 chipset watch this video:
Click to expand...
Click to collapse
Sadly, Shuame is not working. The website is down and every time I try to install it using a download from another website it says that windows UAC won't allow me to.
To download RootGenius Shuame here you go:
Root Genius
Root Genius 3.1.7 (Android rooting software) for Windows ✔ free download with 3 mirrors. Safe, secure and tested for viruses and malware.
root-genius.en.lo4d.com
jwoegerbauer said:
To download RootGenius Shuame here you go:
Root Genius
Root Genius 3.1.7 (Android rooting software) for Windows ✔ free download with 3 mirrors. Safe, secure and tested for viruses and malware.
root-genius.en.lo4d.com
Click to expand...
Click to collapse
When I tried to root, it says "Such a tough phone! Root...failed" :/
Did you ever get a custom ROM working on this phone? The default Android ROM is pretty annoying (blocks push notifications).
luckydliu010 said:
Did you ever get a custom ROM working on this phone? The default Android ROM is pretty annoying (blocks push notifications).
Click to expand...
Click to collapse
Try Project Treble. That's what I learned today from Reddit, but there isn't a way to install it since there is no TWRP file thingy for this phone. Do you know if I could install it using ADB or?!??
[email protected] said:
Try Project Treble. That's what I learned today from Reddit, but there isn't a way to install it since there is no TWRP file thingy for this phone. Do you know if I could install it using ADB or?!??
Click to expand...
Click to collapse
Wait are you Nightcore? LOL that's my thread . I am going to **** around with a Moto E5 (similar CPU, but has lots more documentation) and see if I can figure a way to load via ADB.
luckydliu010 said:
Wait are you Nightcore? LOL that's my thread . I am going to **** around with a Moto E5 (similar CPU, but has lots more documentation) and see if I can figure a way to load via ADB.
Click to expand...
Click to collapse
HUH??! LMAO! Yea, thats me. I'm also trying to get project tremble to work on a ZTE Blade X1 5G, but no luck. Wanna chat on reddit?
[email protected] said:
HUH??! LMAO! Yea, thats me. I'm also trying to get project tremble to work on a ZTE Blade X1 5G, but no luck. Wanna chat on reddit?
Click to expand...
Click to collapse
Yeah man, let's chat.
[email protected] said:
I know that I probably won't get any help since this is a budget phone from a random company, but has anyone figured out how to get Android 10 on the phone? If not, does anyone know how to install Magisk or root this phone? I've read threads on how to install it, but they don't list this phone as supported. TWRP doesn't support Hot Pepper Ghost so how can I install Magisk? Kingoroot doesn't let me root the phone, so what is another way?
Click to expand...
Click to collapse
Did you figure out how to unlock the bootloader? It fails everytime I try.
GitHub - bkerler/mtkclient: MTK reverse engineering and flash tool
MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.
github.com
SR_72_Blackbird said:
Did you figure out how to unlock the bootloader? It fails everytime I try.
Click to expand...
Click to collapse
I unlocked mine as soon as it came in today..
adb reboot bootloader
fastboot devices
fastboot flashing unlock_critical
then, if that doesn't unlock it, then do the age old "fastboot oem unlock"
DrScrad said:
I unlocked mine as soon as it came in today..
adb reboot bootloader
fastboot devices
fastboot flashing unlock_critical
then, if that doesn't unlock it, then do the age old "fastboot oem unlock"
Click to expand...
Click to collapse
Do you know how to root after unlocking bootloader?
How can we pull the boot.img from the os?
There is no firmware available for download.
I managed to unlock the phone using MTK Client on Ubuntu and plan on rooting the phone and installing a GSI. However, I accidentally bootlooped the phone and I think it has to do with dm-verity. I managed to extract some of the important firmware like boot.img and system.img. However, I didn't patch the boot.img with Magisk before the bootloop happen. Would anyone who has a Hot Pepper Ghost (HPP GS1) be able to install Magisk Manager and patch the boot.img attached for me? It would be very appreciated as I think it would solve my bootloop.
googlephoneFKLenAsh said:
Do you know how to root after unlocking bootloader?
How can we pull the boot.img from the os?
There is no firmware available for download.
Click to expand...
Click to collapse
I was able to get the boot.img and system.img using MTK Client after unlocking the bootloader. The post above has the boot.img and I would greatly appreciate if you could help me out with my problem.
SR_72_Blackbird said:
I was able to get the boot.img and system.img using MTK Client after unlocking the bootloader. The post above has the boot.img and I would greatly appreciate if you could help me out with my problem.
Click to expand...
Click to collapse
Mind to share how you bootlooped, so that others can avoid it?
Patched with magisk 24312:
googlephoneFKLenAsh said:
Mind to share how you bootlooped, so that others can avoid it?
Patched with magisk 24312:
Click to expand...
Click to collapse
Unfortunately, the patched boot.img still didn't fix the bootloop.
Currently, I am attempting to build TWRP for the device to see if that can fix anything. I used the twrptgen command to make a device tree for the Ghost with the boot.img and am trying to build TWRP, but I am running into an error.
I have posted on this forum (page 240) if anyone could help with that.
In terms of bootlooping, the process of unlocking the bootloader with MTK Client as documented in the GitHub went fine. After booting, it did show a dm-verity error and orange state saying the bootloader had been unlocked, but all was still fine. Proceeding, I decided to try to flash a GSI and this is where I ran into problems. I attempted to flash the original system.img again, but that didn't work. Also for some reason it wouldn't boot into recovery, even though it should be tied into the boot.img not system.img because of the A/B partitioning. However, I still have access to BROM mode for MTK Client and fastboot mode. I think the bootloop has something to do with dm-verity and vbmeta.img, but I have tried a lot on those lines with no prevail.
I think there are two fixes to this problem. One being TWRP, if I can successfully build it, and the second flashing the entire stock firmware with a flash.bin file and starting over. I didn't realize until it was too late that I should have backed up everything into a flash.bin file using MTK Client, and instead only backed up specific partitions.
It would be awesome if you could help me and post a flash.bin file to this forum of the stock firmware for the Ghost. The instructions on how to do that are here, but in specific are as follows (on a Linux distribution, preferably Ubuntu):
Code:
sudo apt install python3 git libusb-1.0-0 python3-pip
git clone https://github.com/bkerler/mtkclient
cd mtkclient
pip3 install -r requirements.txt
python3 setup.py build
python3 setup.py install
sudo usermod -a -G plugdev $USER
sudo usermod -a -G dialout $USER
sudo cp Setup/Linux/*.rules /etc/udev/rules.d
sudo udevadm control -R
**Make sure to reboot now before proceeding**
**To put the Ghost into BROM mode (which is how you will read the partitions) make sure it is powered off. Then run this command:**
python3 mtk rf flash.bin
**Then, press and hold VOLUME UP, VOLUME DOWN, AND POWER, all at the same time, and at the same time, plug the phone into the computer with a USB cable.**
**The phone should start reading all the partitions and once it is done, it will have outputed a flash.bin file for the Ghost**
Any update on this project? I've had two of these phones for years, would love to be able to load a different OS onto one of them.
One of mine appears to have already been flashed with a basic android 9. It has strange problems, like not detecting the fingerprint reader and a few other things I can't think of offhand. Anyway, you can tell it isn't the same as the other one.
The normal one I bought new, the odd one came from ebay.
Anyway, just wanted to check on this topic. I don't use either of them at this point. I like messing with these types of things for fun.
I'm going to try and get a TWRP working on this Hot Pepper today, I'll let you guys know...
I signed up for a beta test on centernode and received a smartphone to test. The phone is so new that I cannot find any information about it on the internet. The bootloader is unlocked on it. I was reading that you can use magisk to root any device with an unlocked bootloader and system image. Since the phone is so new I cannot find a system image. Is it still possible to root the device? Is there a way I can backup the stock ROM and create a system image that way? Is there something else that will work? I really want to root the device because it came with a preinstalled app which is a system booster type app. It will not let me uninstall it, disable it, or force stop it. When I install my app for my alarm clock it keeps killing the app and the alarm will not go off. I have went through all of the app settings and cannot get it to stop. It also keeps interfering with my VPN. I would also like to root th device to remove some of the bloatware and to have access to the HOST file. Could someone please help me this? I would greatly appreciate it. Thanks guys!
I'm not known for giving good advice but if I was in your situation I would try to install the lastest version of Magisk and hope for the best. Knowing how I am it would be driving me nuts wondering if it would work.
That booster app, have you tried uninstalling it with adb?
Gregbmil1 said:
I'm not known for giving good advice but if I was in your situation I would try to install the lastest version of Magisk and hope for the best. Knowing how I am it would be driving me nuts wondering if it would work.
That booster app, have you tried uninstalling it with adb?
Click to expand...
Click to collapse
Hey, thanks for your reply. I am really eager to root it. I almost just went for it. However, then I thought about it. If something went wrong I would not have any way to recover the phone since there is not a system image available yet. I have not given adb removal a try yet as I figure it would just be easier to go with rooting since it will help me with everything I am trying to achieve. If I cannot root it then I will go the adb route. Hopefully someone will come along and help me out. Fingers crossed
Let us know what you end up doing. Are you expected to send the phone back after the beta testing? If you are responsible for any damages done to it, I would not try it.
You could send it back bricked and say you have no idea what happened to it, lol. That or say you were "testing" the security of the device and that it passes
bigroc2223 said:
I signed up for a beta test on centernode and received a smartphone to test. The phone is so new that I cannot find any information about it on the internet. The bootloader is unlocked on it. I was reading that you can use magisk to root any device with an unlocked bootloader and system image. Since the phone is so new I cannot find a system image. Is it still possible to root the device? Is there a way I can backup the stock ROM and create a system image that way? Is there something else that will work? I really want to root the device because it came with a preinstalled app which is a system booster type app. It will not let me uninstall it, disable it, or force stop it. When I install my app for my alarm clock it keeps killing the app and the alarm will not go off. I have went through all of the app settings and cannot get it to stop. It also keeps interfering with my VPN. I would also like to root th device to remove some of the bloatware and to have access to the HOST file. Could someone please help me this? I would greatly appreciate it. Thanks guys!
Click to expand...
Click to collapse
If you have the firmware then you're in luck (especially if it's the full one)
Download a program for windows called "Payload Dumper"
Open the zip (firmware) and copy out the payload.bin file.
Copy this to the input folder from payload dumper.
Run the exe for payload dumper
It'll output a bunch of files to output folder
You'll see a boot.img file this is essentially the file you use to boot your phone and also where magisk would reside too.
Copy this to your phone.
Install the latest Magisk then open it
Click install and then patch a file, navigate to the boot.img
Click the boot.img and it'll output a file to "SDcard\Downloads" usually called magisk_patched.img
Copy this to your fastboot folder on your computer and open a CMD / Powershell command to that location.
Then boot to fastboot / bootloader mode
Then type:
fastboot boot "name of patched boot.img"
eg:
fastboot boot magisk_patched.img
The phone will boot
From this point you are rooted but you need to make it permanent as you haven't flashed the boot sector at this point, you're only booting an image, if you were to reboot you'd lose it.
Open Magisk again then click install again.
Now instead of just seeing patch a file you'll see "Install Directly" + "Install after an OTA"
Click Install directly, allow it to finish, then reboot.
You're now fully rooted.
Heres my guides for the oneplus 8 pro, don't use the images there as they're for the 8 pro, you also can download payload dumper from there too.
(ROOT) Android 11 / Latest stock and patched img's / payload dumper / magisk_patched guides
Hi all, Have seen a lot of requests for patched boot images on these threads so thought i'd share a guide on how to get it yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it...
forum.xda-developers.com
IT's easy.
Good luck
dladz said:
If you have the firmware then you're in luck (especially if it's the full one)
Download a program for windows called "Payload Dumper"
Open the zip (firmware) and copy out the payload.bin file.
Copy this to the input folder from payload dumper.
Run the exe for payload dumper
It'll output a bunch of files to output folder
You'll see a boot.img file this is essentially the file you use to boot your phone and also where magisk would reside too.
Copy this to your phone.
Install the latest Magisk then open it
Click install and then patch a file, navigate to the boot.img
Click the boot.img and it'll output a file to "SDcard\Downloads" usually called magisk_patched.img
Copy this to your fastboot folder on your computer and open a CMD / Powershell command to that location.
Then boot to fastboot / bootloader mode
Then type:
fastboot boot "name of patched boot.img"
eg:
fastboot boot magisk_patched.img
The phone will boot
From this point you are rooted but you need to make it permanent as you haven't flashed the boot sector at this point, you're only booting an image, if you were to reboot you'd lose it.
Open Magisk again then click install again.
Now instead of just seeing patch a file you'll see "Install Directly" + "Install after an OTA"
Click Install directly, allow it to finish, then reboot.
You're now fully rooted.
Heres my guides for the oneplus 8 pro, don't use the images there as they're for the 8 pro, you also can download payload dumper from there too.
(ROOT) Android 11 / Latest stock and patched img's / payload dumper / magisk_patched guides
Hi all, Have seen a lot of requests for patched boot images on these threads so thought i'd share a guide on how to get it yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it...
forum.xda-developers.com
IT's easy.
Good luck
Click to expand...
Click to collapse
So it sounds like since this is a beta device and I cannot find a firmware image in out of luck?
I guess the only other option I have is finding someone who can port twrp for my device. Then I can just root via TWRP. However, from what I have read that might not even be an option as Android 11 mostly has to be rooted the hard way which you have gave instructions on above.
Can anyone think of anything else I can try?
bigroc2223 said:
So it sounds like since this is a beta device and I cannot find a firmware image in out of luck?
I guess the only other option I have is finding someone who can port twrp for my device. Then I can just root via TWRP. However, from what I have read that might not even be an option as Android 11 mostly has to be rooted the hard way which you have gave instructions on above.
Can anyone think of anything else I can try?
Click to expand...
Click to collapse
You can also extract the boot image... Can't remember the commands for this via ADB, Google ADB extract boot.img
dladz said:
You can also extract the boot image... Can't remember the commands for this via ADB, Google ADB extract boot.img
Click to expand...
Click to collapse
Awesome this is exactly what I was trying to figure out in my original post. Since there is no stock firmware available yet (beta unit) what is the best way to backup the device so I do not get a brick in the process? Thanks again for your help.
bigroc2223 said:
Awesome this is exactly what I was trying to figure out in my original post. Since there is no stock firmware available yet (beta unit) what is the best way to backup the device so I do not get a brick in the process? Thanks again for your help.
Click to expand...
Click to collapse
An actual back up? Probably twrp if available.
If not then you'd need a recovery method.
So providing you have a recovery solution you should be fine.
dladz said:
An actual back up? Probably twrp if available.
If not then you'd need a recovery method.
So providing you have a recovery solution you should be fine.
Click to expand...
Click to collapse
Ahhh okay since it is a beta device no one has made TWRP for it yet. What do you think the risk is of manually pulling the boot img, patching, and flashing is? If I can get that to work I will try to port twrp to the device. Thanks again for the help.
bigroc2223 said:
Ahhh okay since it is a beta device no one has made TWRP for it yet. What do you think the risk is of manually pulling the boot img, patching, and flashing is? If I can get that to work I will try to port twrp to the device. Thanks again for the help.
Click to expand...
Click to collapse
You're very welcome.
Chances of it not booting after doing that? Absolutely zero.
It's a copy not a cut, so you're fine.
The only problem you may encounter is the ability to access the device on that level.
Just turn on usb debugging and make sure ADB works as it should be checking on ADB devices.
Then go ahead with the pull.
You'll be fine.
Also once you have the boot.img if the patched one doesn't work then just reboot and you're back to normal.
I would advise against flashing it, just boot it.
dladz said:
Just turn on usb debugging and make sure ADB works as it should be checking on ADB devices.
Then go ahead with the pull.
You'll be fine.
Also once you have the boot.img if the patched one doesn't work then just reboot and you're back to normal.
Click to expand...
Click to collapse
You can't simply run
Code:
adb devices
adb pull boot.img > C:\boot.img
to clone phone's boot.img to PC.
The correct way is described here
Extract Boot.img Directly from Device Without Downloading Firmware
In this tutorial, we will show you the steps to extract the boot.img file directly from your device without downloading the firmware.
www.droidwin.com
jwoegerbauer said:
You can't simply run
Code:
adb devices
adb pull boot.img > C:\boot.img
to clone phone's boot.img to PC.
The correct way is described here
Extract Boot.img Directly from Device Without Downloading Firmware
In this tutorial, we will show you the steps to extract the boot.img file directly from your device without downloading the firmware.
www.droidwin.com
Click to expand...
Click to collapse
I did not say that you could?? I said pull it.
Before that I said look it up / Google it
Thanks for your help guys I appreciate it greatly. I am going to give this a try today. I will report back and let you guys know how it goes.
One last question. Since this beta unit I got is a tracfone branded unit with an unlocked bootloader is it possible that they could push a firmware which will lock the bootloader at some point? If so is there any way to prevent that from happening? Thanks again for all your help.
bigroc2223 said:
Thanks for your help guys I appreciate it greatly. I am going to give this a try today. I will report back and let you guys know how it goes.
One last question. Since this beta unit I got is a tracfone branded unit with an unlocked bootloader is it possible that they could push a firmware which will lock the bootloader at some point? If so is there any way to prevent that from happening? Thanks again for all your help.
Click to expand...
Click to collapse
Possible yes, but I doubt they would do that.
Is it an ambassador phone? Or for testing?
Locking the bootloader wipes the phone so I wouldn't imagine they'd do that without forewarning.
Plus locking a bootloader comes with its risks too, so you could say that it broke from the update.
But it won't come to that, I've had several ambassador phones myself and honestly they're fire and forget for the most part, I wouldn't worry about it
dladz said:
Possible yes, but I doubt they would do that.
Is it an ambassador phone? Or for testing?
Locking the bootloader wipes the phone so I wouldn't imagine they'd do that without forewarning.
Plus locking a bootloader comes with its risks too, so you could say that it broke from the update.
But it won't come to that, I've had several ambassador phones myself and honestly they're fire and forget for the most part, I wouldn't worry about it
Click to expand...
Click to collapse
It's a phone for testing which I am allowed to keep.
dladz said:
Possible yes, but I doubt they would do that.
Is it an ambassador phone? Or for testing?
Locking the bootloader wipes the phone so I wouldn't imagine they'd do that without forewarning.
Plus locking a bootloader comes with its risks too, so you could say that it broke from the update.
But it won't come to that, I've had several ambassador phones myself and honestly they're fire and forget for the most part, I wouldn't worry about it
Click to expand...
Click to collapse
It is a phone for testing which I am allowed to keep. Specs are Snapdragon 750g, Adreno 619, and 4gb of ram. Not too shabby for a free phone. It is a lot snappier than the moto e6 I was previously using.
dladz said:
I did not say that you could?? I said pull it.
Before that I said look it up / Google it
Click to expand...
Click to collapse
This method requires TWRP. So this will not work.
bigroc2223 said:
Nvm
Click to expand...
Click to collapse
dladz said:
Again!!!? What's your problem??
You're just trying to (for whatever reason) prove me wrong and yet again I wasn't being descriptive of an ADB pull!!!
You're pulling the boot.img off the device by whatever means.
To be clear for the final time, I'm not stating to use twrp, a script or anything else I said look it up / Google it!
Now if you've helped the chap then that's great, looking at what I said and attempting to put me straight when you clearly don't have to, is no help to you or the chap needing help it's just making you look like you're on a power trip.
Click to expand...
Click to collapse
I'm just trying to get some help here guys that's it. I appreciate everyone's efforts and opinions. Let's all try to work together and try to find a solution peacefully please.
So far I have adb installed and working. I have tried to use the commands I was able to locate via google. So far nothing works. I have also tried uninstalling some programs using adb which did not work. I think I am going to have to find someone who could port twrp for me
bigroc2223 said:
I'm just trying to get some help here guys that's it. I appreciate everyone's efforts and opinions. Let's all try to work together and try to find a solution peacefully please.
So far I have adb installed and working. I have tried to use the commands I was able to locate via google. So far nothing works. I have also tried uninstalling some programs using adb which did not work. I think I am going to have to find someone who could port twrp for me
Click to expand...
Click to collapse
Sorry I got the wrong end of the stick, I thought you was a second person posting..
Forget what I said