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...
Related
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.
This is mainly a temporary repost of @rakomancha's TWRP announcement in a new thread. He is the maintainer of this TWRP but has not signed into XDA for a while. There is an updated TWRP that I wanted to share. When he comes back and creates his own thread, I will replace this post with a link to his.
-------------------------------------------------------------------------------------------------------------------------------------------------------
[TWRP][RECOVERY] Asus ZenPad 3S 10 Z500M
The next big step forward for Z500M development is here!
This is the first working custom TWRP recovery for the Asus ZenPad 3S 10 Z500M [P027], based from TWRP v3.2.1.
diplomatic and I had both been working on a port separately, and I offered to test his version. In a few hours we worked out a functional and install-friendly version.
Please NOTE that this is NOT an official TWRP. After this post, I'll be working on making the port official and update here.
ACKNOWLEDGEMENTS
This project, and my own motivation, would not have been possible without the incredible work and input of:
diplomatic, who has been instrumental in propelling Z500M development forward. He worked on the issue of perm root and discovered and revealed important intricacies of the Z500M restrictive bootloader. By the end of Dec 2017, he developed a method to unlock the Z500M bootloader based on his amazing work with the Z380M. With amartolos as his testing assistant, the Z500M bootloader unlocking tool was quickly developed and released Jan 5th 2018.
overkillZ, who in Sept 2017 introduced us all to rooting the Z500M
toineh, who did legwork of establishing temp root by manipulating system permissions & redirecting files through adb. Then he took the boot.img posted by LGiki, explained how to patch it through Magisk and posted the first patched boot image. He also served as a guiding voice on this front.
amartolos, who first attempted perm flashing the patched boot image of toineh's method and worked with diplomatic on the developments afterward, which led us to today. Also has served as a guiding voice.
LGiki, who was the first to post an extracted WW_27 boot image that got things rolling forward
DISCLAIMER
This image has only been successfully tested by me at this point.
Please exercise caution and care when attempting to flash anything to your device.
You are completely responsible for any possible issues or damages resultant from undertaking the following procedures.
That being said, this image and method should be safe.
REQUIREMENTS
ZenPad Z500M tablet, upgraded to Android N
Bootloader Unlocked, using Diplomatic's tool. Tablet should be showing Orange State during initial bootup.
Root with Magisk installed, Permanent Root preferable
BACK UP YOUR INTERNAL USER DATA, in case you need to factory reset
TWRP for Z500M recovery image file [twrp-3.2.1-0-z500m.img]
Knowledge of adb/fastboot and basic Linux shell
INSTRUCTIONS
Ensure REQUIREMENTS are all met
Ensure to RE-READ all instructions and understand them before starting
Reboot into fastboot mode
do fastboot boot twrp-3.2.1-0-z500m.img, TWRP should boot up in a few seconds. The theme should be blue.
In TWRP, go to BACKUP and back up Boot, Recovery, Data, System and SystemImage. Full backup took me about 10GB of space.
Copy the created TWRP Backup to your PC or an external location for safekeeping
Copy the TWRP twrp-3.2.1-0-z500m.img to tablet storage if not done already.
In TWRP, go to INSTALL, select Install Image and choose the twrp-3.2.1-0-z500m.img. Installation should only take a few seconds.
Unplug from USB and Reboot back into Recovery through the REBOOT menu
If installation went well, TWRP should boot up in a YELLOW theme. From my testing, I'm confident it is functionally the same.
RESOURCES
In this shared folder are
TWRP for Z500M recovery image file [twrp-3.2.1-0-z500m.img]
version 0.5 of Diplomatic's Unlock Tool
diplomatic's Z500M device source
hxxps://mega.nz/#F!SQlyDapC!XbbW0fftZWFfVx2lmL_JUQ [down, get the file below]
GOING FORWARD
I successfully tested replacement of Magisk with SuperSU. My steps taken were:
"Completely Uninstall" Magisk through the Magisk Manager
reboot directly into Recovery
INSTALL a previously downloaded official SuperSU zip file & REBOOT
I very much enjoyed this process of developing for uncharted regions of Android technologies and I owe all of that to the existence of this forum and the people in it. Next, I am reading up on porting a custom ROM, LineageOS looked very nice. I'll update here with significant progress until I get capability to start new forum threads. Thank you all and enjoy delicious functional TWRP custom recovery on your Z500M for the first time in history. Here's to looking forward to development exploding on this device.
-------------------------------------------------------------------------------------------------------------------------------------------------------
NEW DOWNLOAD
Updated February, 2018
Fixes the yellow color rendering in installed mode
twrp-3.2.1-0-z500m.zip
ADDITIONAL WARNING: At first boot of TWRP, it will ask you if you want to keep system read-only. Touch the Keep Read Only button at this screen and only mount system in read-only mode if you need (rarely needed). This is necessary because of dm-verity and is no different than most Android 6+ devices. Unless you have unlocked your bootloader and installed permanent root with dm-verity disabled, mounting the system partition in r/w mode will make changes to it and your tablet will instantly become unbootable.
This is great. Tempted to try this. thanks for the effort!
Thank you very much, I did this and also switched to SuperSU with no problems!
Hi guys,
I have followed all the steps until 8 but I'm stuck at the install : TWRP ask me what partition to flash
boot, recovery or system image
Which one to choose ? I think it's boot but I don't want to make any mistake
Thanks
ratus69 said:
Hi guys,
I have followed all the steps until 8 but I'm stuck at the install : TWRP ask me what partition to flash
boot, recovery or system image
Which one to choose ? I think it's boot but I don't want to make any mistake
Thanks
Click to expand...
Click to collapse
Well, recovery of course. ...because it's a custom recovery.
Hey guys I hope you can help me I had my Z500m partially rooted using the patched Magisk boot method and accidentally erased some stuff before I could permanently root it. Everything snowballed and all I have now is my firmware stored on pc I can get to fastboot mode but I have stock recovery still. can i flash my firmware through fastboot? I’ve been researching and it seems with Mediatek it’s different or at least not as simple. All searches keep coming up for Zenfone and I’m lost. Apologies if Im in wrong area.
diplomatic said:
Well, recovery of course. ...because it's a custom recovery.
Click to expand...
Click to collapse
Well I'm glad having nothing done until I get a reply from the Master himself
Thanks a lot diplomatic !
Sorry for stupid query. I have my Asus in Fastboot mode and connot reboot it. Have tried to hold power longer than 1 minute but nothing happen.
What I have to do
mirek54 said:
Sorry for stupid query. I have my Asus in Fastboot mode and connot reboot it. Have tried to hold power longer than 1 minute but nothing happen.
What I have to do
Click to expand...
Click to collapse
hold volume + and - together for 10s
There was a time that it was unthinkable development. I appreciate the time that cames after. Nice tutorial!
Nice work! I've got the Z500KL version of this tablet, so I'm hoping to port twrp to it at some point as well; if you have any tips or advice that might help it would be much appreciated! Although I'm fairly experienced with Linux this would be my first time working with Android, so I'm not sure if I'll succeed, but I thought I'd give it a shot anyway.
Hi, soleera,
To install TWRP, you must have some way to flash it and a bootloader that's either unlocked or doesn't care about unofficial images. I'm not sure that's possible in Z500KL. Look into that first. The Z500KL is about as much a version of this tablet as a Lenovo Tab4 is a version of this tablet. They are completely different platforms, just with a similar model name.
I've already managed to unlock the bootloader of my Z500KL and I've got fastboot working with it too, what I'm stuck on now is actually compiling twrp - I've already had a look at the guide here, but it's not very useful considering there are no .mk files for this model yet. If I had some idea about where to start I'd at least be able to start experimenting with the kernel / twrp source files and see where that leads me.
soleera said:
I've already managed to unlock the bootloader of my Z500KL and I've got fastboot working with it too, what I'm stuck on now is actually compiling twrp - I've already had a look at the guide here, but it's not very useful considering there are no .mk files for this model yet. If I had some idea about where to start I'd at least be able to start experimenting with the kernel / twrp source files and see where that leads me.
Click to expand...
Click to collapse
Oh, cool. How did you unlock it, btw? I know Asus makes you jump through hoops or doesn't allow unlocking altogether...
In case there is no device tree source (almost always), you start with an existing source tree for a phone with a similar platform. Then you adapt it for your device. Usually it's just a few changes, like the model numbers and importing your kernel. A quick search showed that the Xiaomi Redmi Note 3 might fit the bill. Check out this thread for a TWRP build that someone has made for it...
diplomatic said:
Oh, cool. How did you unlock it, btw? I know Asus makes you jump through hoops or doesn't allow unlocking altogether...
In case there is no device tree source (almost always), you start with an existing source tree for a phone with a similar platform. Then you adapt it for your device. Usually it's just a few changes, like the model numbers and importing your kernel. A quick search showed that the Xiaomi Redmi Note 3 might fit the bill. Check out this thread for a TWRP build that someone has made for it...
Click to expand...
Click to collapse
Sounds good, I'll see what I can do when I get the time.
For some reason one of the official unlock tools for a different model worked on my tablet - I believe it was for the ZE552KL, although I could be wrong since I can't seem to install it any more ("the package conflicts with an existing package by the same name"). I'm definitely unlocked though since I can flash using fastboot without any errors...
Since we now have official unlock. Any chance at custom roms for this device? I would love to see it get some oreo love.
soleera said:
Nice work! I've got the Z500KL version of this tablet, so I'm hoping to port twrp to it at some point as well; if you have any tips or advice that might help it would be much appreciated! Although I'm fairly experienced with Linux this would be my first time working with Android, so I'm not sure if I'll succeed, but I thought I'd give it a shot anyway.
Click to expand...
Click to collapse
Hello soleera
Have you succeeded to port twrp to Z500KL?
Do you know of any custom recovery for Z500KL?
Do you know how to root it?
Dr.Ghobar said:
Do you know how to root it?
Click to expand...
Click to collapse
Since it seems to be possible to unlock the bootloader, you can always try the offline patching method of Magisk Manager. Just get your boot.img from the stock firmware and run it through MM to make a rooted patched boot img. Then using this patched image from your PC, do either 'fastboot flash boot' or 'fastboot boot' (for tethered boot) to obtain root. Done.
diplomatic said:
Since it seems to be possible to unlock the bootloader, you can always try the offline patching method of Magisk Manager. Just get your boot.img from the stock firmware and run it through MM to make a rooted patched boot img. Then using this patched image from your PC, do either 'fastboot flash boot' or 'fastboot boot' (for tethered boot) to obtain root. Done.
Click to expand...
Click to collapse
Thank you for your answer.
But I am not familiar with what you said and with the expressions you used. Can you explain in plain language or point me to a tutorial?
Dr.Ghobar said:
Thank you for your answer.
But I am not familiar with what you said and with the expressions you used. Can you explain in plain language or point me to a tutorial?
Click to expand...
Click to collapse
Basically, just do the procedure in this post. It's not that complicated. Reading through that thread may also help. Oh, and you have to unlock your bootloader first with an Asus unlock tool, as soleera has mentioned. I think the tool for the Z500M may work. It's essentially the same app for every device.
Moto G7 river xt1962-1 firmware 29.114-16-5
firmware_moto-g7_river_xt1962-1_29.114-16-5_copyparts
will be needed for custom roms
firmware_moto-g7_river_xt1962-1_29.114-16-5_full
is all partitions, not required for custom roms, just for curious developers
windows users will need to make their own .bat files I don't use windows
two things:
1. working on twrp for river
2. working on lineageos 16 for river based on payton... errors with some vendor files
actually errors all over
please help I have two newborns and only get a few minutes to myself each night
good luck on building lineage, the g6 never had any development so i dont anticipate the g7 will get much either. if i was you id concentrate on twrp so we can at least flash gsi based roms.
Is this the original factory signed rom? (I.e. is it possible to fully flash and relock bootloader?)
Also wondering if anyone has the latest full rom (29.114-16-7).
Thanks in advance!
ptn107 said:
Moto G7 river xt1962-1 firmware 29.114-16-5
firmware_moto-g7_river_xt1962-1_29.114-16-5_copyparts
will be needed for custom roms
firmware_moto-g7_river_xt1962-1_29.114-16-5_full
is all partitions, not required for custom roms, just for curious developers
windows users will need to make their own .bat files I don't use windows
two things:
1. working on twrp for river
2. working on lineageos 16 for river based on payton... errors with some vendor files
actually errors all over
please help I have two newborns and only get a few minutes to myself each night
Click to expand...
Click to collapse
Confirmed that at least boot.img is correctly signed. You rock ptn107!! However I did confirm (from the version number displayed in recovery) that this is 29.114.16 and not 29.114.16-5.
How were you able to extract the partitions? Specifically boot.img. If I can learn that, then it would be easy to unroot, take OTA updates, copy and save boot.img, and patch with Magisk. Thanks in advance!!!
smokinu said:
Confirmed that at least boot.img is correctly signed. You rock ptn107!! However I did confirm (from the version number displayed in recovery) that this is 29.114.16 and not 29.114.16-5.
How were you able to extract the partitions? Specifically boot.img. If I can learn that, then it would be easy to unroot, take OTA updates, copy and save boot.img, and patch with Magisk. Thanks in advance!!!
Click to expand...
Click to collapse
The boot image version does not change with every little update. For every version of 29.114.16-* released it will be the same boot.img. 29.114.16-7 is getting around and most likely uses the exact same boot.img as ours.
As for extracting the .img files I use a linux shell script I wrote here. Makes doing this quick with each new firmware image.
It needs to be placed in /sdcard on your device (root is required to work):
Code:
adb push mkimg.sh /sdcard/
adb shell
cd /sdcard/
su -c sh ./mkimg.sh
I do this in Linux. Not much of a Windows user anymore.
Output files go into /sdcard/firmware-images but you can change that with the 'outfolder' variable if you wish.
Long story short it takes the list of partitions from /dev/block/bootdevice/by-name/ and uses 'dd' to create the .img.
If you are looking to just get a boot.img from our device and nothing else the command would be as follows (needs root):
Code:
su dd if=/dev/block/mmcblk0p41 of=/sdcard/boot.img > /dev/null 2>&1
ptn107,
Thanks for the write-up. I'm familiar with a similar approach using TWRP (booted, but not installed) and dd copying the individual partitions. I will give your script a try. Should save a lot of time!
Is there a way to copy partitions without root? My biggest concern is taking on an OTA update (currently 16-7), without having the original signed images to revert back to stock and relock the bootloader. Motorola has historically been bad at providing factory roms. If there is a clever way to unroot, take an OTA, save original, and re-root....I'd be a happy camper!
/dev is user root and group root so root is necessary.
Is there a clever way to take an OTA update and get a copy of the new boot.img? From what i understand, you have to unroot to take an OTA update.
BTW...good luck with the newborns!! Mine is now 3 and is still as much of a handful as when he was a newborn.
ptn107 said:
The boot image version does not change with every little update. For every version of 29.114.16-* released it will be the same boot.img. 29.114.16-7 is getting around and most likely uses the exact same boot.img as ours.
As for extracting the .img files I use a linux shell script I wrote here. Makes doing this quick with each new firmware image.
It needs to be placed in /sdcard on your device (root is required to work):
Code:
adb push mkimg.sh /sdcard/
adb shell
cd /sdcard/
su -c sh ./mkimg.sh
I do this in Linux. Not much of a Windows user anymore.
Output files go into /sdcard/firmware-images but you can change that with the 'outfolder' variable if you wish.
Long story short it takes the list of partitions from /dev/block/bootdevice/by-name/ and uses 'dd' to create the .img.
If you are looking to just get a boot.img from our device and nothing else the command would be as follows (needs root):
Code:
su dd if=/dev/block/mmcblk0p41 of=/sdcard/boot.img > /dev/null 2>&1
Click to expand...
Click to collapse
Boot img sometimes changes, you never know. I bricked a g6 by flashing a boot img that the last number in the version was 2 instead of 4. Flashed, and got stuck in a bootloop. Had to completely reflash stock firmware, then took an OTA that bricked it.
clcombs262 said:
Boot img sometimes changes, you never know. I bricked a g6 by flashing a boot img that the last number in the version was 2 instead of 4. Flashed, and got stuck in a bootloop. Had to completely reflash stock firmware, then took an OTA that bricked it.
Click to expand...
Click to collapse
I did confirm that the boot.img between 16 and 16-5 is different. The recovery mode displays the correct version for each of the boot.imgs, and MD5 checksums are different, although same file size.
That being said, flashing a 16 boot.img on a 16-5 device will mearly result in bootloop until the correct version is flashed. People should keep track of which slot they loaded the boot.img into (A/B).
smokinu said:
I did confirm that the boot.img between 16 and 16-5 is different. The recovery mode displays the correct version for each of the boot.imgs, and MD5 checksums are different, although same file size.
That being said, flashing a 16 boot.img on a 16-5 device will mearly result in bootloop until the correct version is flashed. People should keep track of which slot they loaded the boot.img into (A/B).
Click to expand...
Click to collapse
Code:
fastboot oem lock
doesn't work with PPO29.114-16-5
says boot.img is not signed
update: same for PPO29.114-16 and PPO29.80-61
ptn107 said:
Code:
fastboot oem lock
doesn't work with PPO29.114-16-5
says boot.img is not signed
update: same for PPO29.114-16 and PPO29.80-61
Click to expand...
Click to collapse
I saw the same thing on my end at first. Found this to work repeatedly....
fastboot oem lock (enter this a few times until i says something to the effect of...."you still need to flash a signed boot.img")
fastboot flash boot boot.img (this will now flash fine without saying the image is not signed)
fastboot oem lock (if you prefer to re-lock. You'll need the unlock key again if you plan to unlock).
smokinu said:
I saw the same thing on my end at first. Found this to work repeatedly....
fastboot oem lock (enter this a few times until i says something to the effect of...."you still need to flash a signed boot.img")
fastboot flash boot boot.img (this will now flash fine without saying the image is not signed)
fastboot oem lock (if you prefer to re-lock. You'll need the unlock key again if you plan to unlock).
Click to expand...
Click to collapse
Wow. That actually worked. I had to do both commands like 6 times one after the other but it worked.
Thank you!
No problem! Glad I could help. Found that one by accident.
smokinu said:
No problem! Glad I could help. Found that one by accident.
Click to expand...
Click to collapse
I would have never found that out.
fastboot without root
I have been foolish and used twrp to wipe my G7. I am trying to use twrp to flash or fastboot update provided in this thread but neither approach works.
error is invalid zip file.
I was running -7 not -5
as in my title, there is no root. and because of my stupidity, no OS either! I am happy to give any details
Any help would be amazing. Thanks in advance!
Mr_navillus said:
I have been foolish and used twrp to wipe my G7. I am trying to use twrp to flash or fastboot update provided in this thread but neither approach works.
error is invalid zip file.
I was running -7 not -5
as in my title, there is no root. and because of my stupidity, no OS either! I am happy to give any details
Any help would be amazing. Thanks in advance!
Click to expand...
Click to collapse
The zip file itself cannot be flashed as it's not in proper update format. You'll have to extract and flash the contents via fastboot. To get to fastboot, power off the device then hold power and volume down until you see the bootloader screen, and then connect it via USB to a pc
Follow the instructions here to get back to stock
Mr_navillus said:
I have been foolish and used twrp to wipe my G7. I am trying to use twrp to flash or fastboot update provided in this thread but neither approach works.
error is invalid zip file.
I was running -7 not -5
as in my title, there is no root. and because of my stupidity, no OS either! I am happy to give any details
Any help would be amazing. Thanks in advance!
Click to expand...
Click to collapse
Sounds like you wiped the system partition then tried to flash the unflashable zip file (hence, no system)
First, always make backups.
Second, you can still get into fastboot and manually update/restore
You can also use the moto software to recover the device.
Get it into fastboot, start from there. It is 100% an easy recovery process
warBeard_actual said:
You can also use the moto software to recover the device.
Click to expand...
Click to collapse
This fixed it in a jiffy. Making backups from now on!
Question to the experts:
Unlocking the bootloader and rooting a phone is stressful times for those of us who (like me) only do this once every few years when we buy a new phone. On some phones, after attempts at routing, I've been stuck for days without a phone till some distant helpful person helped me back to a working rooted phone. Other times it was very simple. But the experience leaves you scared.
Yes I know it's my own (and similar other uneducated) fault because we did something wrong that would be obvious to any expert. But it happens to the rest of us no matter how many threads we read.
So my question is, if the phone becomes non functional following erroneous commands or files (my own unintentional error), will this same 'moto recovery' restore things?
Where do I find out more 'how' to use this Moto software and where this 'Moto software recovery' is to be found?
Thank you.
Edit
Just to clarify things, this is my first Moto phone which is why I don't know what the Moto software recovery is. Is it what you get by pressing Power-volume down?
This phone doesn't have its own section in the forum yet, so I decided to put here a little guide for those who haven't figured out how to root it yet.
There is no twrp version for this Motorola yet, so I'm going to teach you how to root it without recovery.
This is how I rooted my Motorola One Macro:
Unlock your bootloader here.
Check the Compilation Number of your firmware (probably something like PMDXX.XX-XX)
Download THE SAME VERSION of your compilation from here.
Extract from the zip the boot.img
Copy boot.img in a folder of your choice in your phone.
Install Magisk Manager apk in your phone (download here)
Open Magisk Manager and choose Install --> Install --> Patch file
Select boot.img and wait until it's patched
A new file would be created in the same folder you put the boot.img, named magisk_patched.img
Copy magisk_patched.img to your PC.
Reboot your phone to bootloader
Now replace the boot.img of your phone with the new one patched by magisk using the following commands:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
fastboot reboot
And now you are rooted. Enjoy
Pretinaverse said:
This phone doesn't have its own section in the forum yet, so I decided to put here a little guide for those who haven't figured out how to root it yet.
There is no twrp version for this Motorola yet, so I'm going to teach you how to root it without recovery.
This is how I rooted my Motorola One Macro:
Unlock your bootloader here.
Check the Compilation Number of your firmware (probably something like PMDXX.XX-XX)
Download THE SAME VERSION of your compilation from here.
Extract from the zip the boot.img
Copy boot.img in a folder of your choice in your phone.
Install Magisk Manager apk in your phone (download here)
Open Magisk Manager and choose Install --> Install --> Patch file
Select boot.img and wait until it's patched
A new file would be created in the same folder you put the boot.img, named magisk_patched.img
Copy magisk_patched.img to your PC.
Reboot your phone to bootloader
Now replace the boot.img of your phone with the new one patched by magisk using the following commands:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
fastboot reboot
And now you are rooted. Enjoy
Click to expand...
Click to collapse
hi...
this guide works for me.
Motorola One Macro LatinAmerican version Telcel.
Pretinaverse said:
This phone doesn't have its own section in the forum yet, so I decided to put here a little guide for those who haven't figured out how to root it yet.
There is no twrp version for this Motorola yet, so I'm going to teach you how to root it without recovery.
This is how I rooted my Motorola One Macro:
Unlock your bootloader here.
Check the Compilation Number of your firmware (probably something like PMDXX.XX-XX)
Download THE SAME VERSION of your compilation from here.
Extract from the zip the boot.img
Copy boot.img in a folder of your choice in your phone.
Install Magisk Manager apk in your phone (download here)
Open Magisk Manager and choose Install --> Install --> Patch file
Select boot.img and wait until it's patched
A new file would be created in the same folder you put the boot.img, named magisk_patched.img
Copy magisk_patched.img to your PC.
Reboot your phone to bootloader
Now replace the boot.img of your phone with the new one patched by magisk using the following commands:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
fastboot reboot
And now you are rooted. Enjoy
Click to expand...
Click to collapse
This worked for me too.
Hello! Thank you very much for the tutorial for the Moto One Macro. I was tired of looking for a tutorial for mine.
But one question remained: Because I am unable to install a Recovery, am I unable to flash a custom rom? Because I was trying to root the device just to install a Custom Rom of the Lineage OS type of Android 10, considering that as far as Motorola is concerned, the pro 10 update will not come anytime soon. But I still thank you for the tutorial.
Sent from my Motorola One Hyper using XDA Labs
Question
I have multiple questions I would like to ask.
1. Would this format the phone? Which partitions will get formatted?
2. Can you explain the namings of the folder in the link to the post? What do they mean? I've seen a compilation number close to mines in the 'retail' folder.
3. From where do people get these uploads? I've tried multiple times contacting Motorola for image uploads and they never sent anything. I am very interested in the origin of the files.
4. Is there anyway to recover from a failed patch?
The reason I want this is that I've tried patching the bootloader using an image from a fishy website and it soft-bricked my phone, I had to reformat the whole thing with a fresh image
Btw, thank you for contributing to the phone's community!
Update:
Installed successfully, magisk is enabled and root is functioning and whatnot. Problem is, sometimes on booting the phone hangs on the weird colorful animation. It's not consistent and I can't figure out why. I discovered force rebooting the phone multiple times boots the phone successfully but does not fix the problem. Boot times are slower, probably because of modules.
Screen mirroring Motorola one
Hello,
I have a root Motorola one Android 10, but I can't share my screen to my Samsung smart TV, i search a lot but I didn't have success, first I edited the build.prop lines,
persist.debug.wfd.enable=1 (before it was persist.debug.wfd.enable=0)
persist.hwc.enable_vds=0 (before it was persist.hwc.enable_vds=1)
I added this in the end
wlan.wfd.hdcp=disable
I added another line but I don't remember all because I erased it, i only remember the beginning
Persist.sys....
But it can't work, in my TV only show something like
"Screen mirroring: motorola is connecting" but then the signal is lost
Nothing that I tried work, only one thing is good and is that in my cellphone in the option of share screen after change this line: persist.debug.wfd.enable=1 (before it was persist.debug.wfd.enable=0) I could activate wireless screen and it let me TRY to connect with my TV but without success.
In other post show the last configuration with an extra thing, I should edit a file (wfdconfig.xml) and it supposed to stay in this direction system/etc/ wfdconfig.xml. But I search in all files and I didn't find.
Maybe someone can help me.
Thanks.
altffour said:
I have multiple questions I would like to ask.
1. Would this format the phone? Which partitions will get formatted?
2. Can you explain the namings of the folder in the link to the post? What do they mean? I've seen a compilation number close to mines in the 'retail' folder.
3. From where do people get these uploads? I've tried multiple times contacting Motorola for image uploads and they never sent anything. I am very interested in the origin of the files.
4. Is there anyway to recover from a failed patch?
The reason I want this is that I've tried patching the bootloader using an image from a fishy website and it soft-bricked my phone, I had to reformat the whole thing with a fresh image
Btw, thank you for contributing to the phone's community!
Update:
Installed successfully, magisk is enabled and root is functioning and whatnot. Problem is, sometimes on booting the phone hangs on the weird colorful animation. It's not consistent and I can't figure out why. I discovered force rebooting the phone multiple times boots the phone successfully but does not fix the problem. Boot times are slower, probably because of modules.
Click to expand...
Click to collapse
Motorola doesn't official share the firmware, but there has always been people with access to the firmware servers.
https://mirrors.lolinet.com/firmware/moto/ has lots of moto firmware
LMSA can also be used to get firmware for most moto devices
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk
Can't find build number
Pretinaverse said:
[*]Check the Compilation Number of your firmware (probably something like PMDXX.XX-XX)
[*]Download THE SAME VERSION of your compilation from here.
Click to expand...
Click to collapse
Hi, I can't find my Build Number in there. Mine is PMDS29.70-81-3.
I see several PMDS29.70-81 but none of them have the -3 I need. Any suggestions?
lorenzzv said:
Hi, I can't find my Build Number in there. Mine is PMDS29.70-81-3.
I see several PMDS29.70-81 but none of them have the -3 I need. Any suggestions?
Click to expand...
Click to collapse
yeah me too, but I solved it, I just rooted mine just download and use Rescue and Smart Assistant to download your firmware and repeat the steps above and that's it, it took me about five minutes to root my phone.
Can any one please confirm, if after rooting this phone are you able to do call recording both side clearly ?
Not working
Help, I did this and now my phone is stuck on the Motorola logo, ¿is a way to undo this process? T_T
just download motorola smart assisstant on your laptop and plug your mobile to it and it will do the rest
atattooedgod said:
just download motorola smart assisstant on your laptop and plug your mobile to it and it will do the rest
Click to expand...
Click to collapse
That did the trick. MY ETERNAL GRATITUDE TO YOU, SIR. YOU ROCK.
HELP
atattooedgod said:
yeah me too, but I solved it, I just rooted mine just download and use Rescue and Smart Assistant to download your firmware and repeat the steps above and that's it, it took me about five minutes to root my phone.
Click to expand...
Click to collapse
Hey bro, im looking for this, can u upload? or give any link related? LMSA is coded by monkeys with cocaine in water and tells that my XT2016-2 is'nt compatible :\
Help!
I am from Brazil and I have a Motorola One Macro and the device does not appear in the list of supported devices for OEM unlocking on the Motorola website.
Do you have TWRP for XT2016-2 ?
mrmanson07 said:
I am from Brazil and I have a Motorola One Macro and the device does not appear in the list of supported devices for OEM unlocking on the Motorola website.
Click to expand...
Click to collapse
Ignore the list the list of never been complete.
The only way to know if the bootloader can be unlocked is to try to unlock it.
Sent from my Moto E (4) using Tapatalk
Nice
VD171 said:
Do you have TWRP for XT2016-2 ?
Click to expand...
Click to collapse
There is not, but i am working on developing one we'll see soon if i can complete it succesfully due actually there are a lot of problems with this one
TWRP would be a nice treat here. Keep the thread updated on any progress.
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