[SIZE=+3]Frequently Asked Questions[/SIZE]
[SIZE=+2]Google Nexus 6[/SIZE]
[SIZE=+1]This a short list of frequently asked questions in this device forum and the answers often given as a response. It should serve as a starting point for gathering knowledge and finding solutions to many common problems. Please only post in this thread with feedback on how to improve this document. Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread or create your own. Do not use this as a general help thread.[/SIZE]
[SIZE=+1]Q1: I'm new to Nexus 6, where do I find a thread with guides and useful information?[/SIZE]The sticky roll up thread in the general forum has all of the guides and important information. You can find that HERE.
[SIZE=+1]Q2: Where can I find tools such as USB drivers[/SIZE]You can find the universal Google driver inside of the Android SDK found HERE. Or you can install ADB/fastboot and universal drivers from HERE.
[SIZE=+1]Q3: What does "flashing" my phone mean?[/SIZE]Well, there are a couple of meanings here. "Flashing" a custom ROM means to overwrite your current OS with a new one. "Flashing" can also mean, changing from a carrier to a pre-paid carrier. Example: I need to flash my phone from AT&T to Cricket.
[SIZE=+1]Q4: Bootloader.. What is this?[/SIZE]For an easy explanation of what a bootloader is, look HERE.
The most recent bootloader and radio can be found here : Here is a recovery flashable zip of the 6.0.1 bootloader and 32r radio
[SIZE=+1]Q5: How do I root my device?[/SIZE]There are a few options. The most recommended way is to unlock your bootloader, flash custom recovery, flash superSU zip, install superSU app. Also there are more automated methods, such as toolkits and auto root. HERE is a great place to get that information.
[SIZE=+1]Q6: What is a factory image?[/SIZE]A factory image for Nexus devices is provided directly from Google. They are used to return your device to the state it was in when it was put in the box. They can be found HERE.
Most recent is 6.0.1 (MMB29Q)
[SIZE=+1]Q7: How do I backup my device in case I bork it?[/SIZE]TWRP recovery has the feature of allowing you to backup your device. It is highly recommended to backup your stock image after installing TWRP and before flashing anything else. Simply use the backup option in TWRP. Think of this as a restore point to go back to when things get borked. Also, you can backup all of your files to your PC before beginning the root process because unlocking your bootloader will wipe your device. There are also apps available that will back up your apps and app data Titanium Backup is a great choice if you already have root. Helium is an option for non-rooted users.
Latest recovery is [RECOVERY][shamu] TWRP 3.0.0-0 touch recovery [2016-02-06]
[SIZE=+1]Q8: How do I flash a factory image?[/SIZE]Flashing a factory image is a fairly easy process. You can use the fastboot method or a toolkit. Toolkits can be found in the development section and an excellent guide to the fastboot method can be found HERE.
[SIZE=+1]Q9: Do the carrier versions matter in deciding on root or ROM?[/SIZE]No. there are no carrier specific ROMs or root methods. There are only two versions of the Nexus 6, Domestic (XT1103) and international (XT1100). Device wiki can be found HERE.. Bootloader unlock method is universal as well.
[SIZE=+1]Q10: What is encryption and should I disable it?[/SIZE]First off, to best answer the "what is" question, look HERE. Now, whether or not to disable it, is entirely up to you. For the most part, the benefits are dependent on your usage. HERE is a thread discussing encryption on 5.1 so please check it out.
[SIZE=+1]Q11: What are fastboot and ADB and should I learn how to use them?[/SIZE]You should absolutely have at least some knowledge of fastboot and ADB. These simple yet powerful tools can save you from trouble and do wonders for your device. The basic principles and commands are extremely easy to learn and thankfully, there are plenty of guides that will help you understand and learn how to use them. Fastboot and ADB aren't exclusive to Nexus either, you can use them with Android as a whole. You can find my favorite guide to using fastboot and ADB right HERE.
[SIZE=+1]Q12: Can I install an OTA if I'm rooted/unencrypted?[/SIZE]No. Since the onset of lollipop, absolutely no system or boot img modifications can be present in order for the OTA to flash. HERE is a thread dedicated to OTA related Q&A and instructions for sideloading. HERE is a thread for OTA files available for sideloading.
[SIZE=+1]Q13: What is a toolkit and should I use one?[/SIZE]First, a toolkit is a program that auto runs and makes changes to your android device. Those changes can be very significant and difficult to recover from when things go wrong. With a toolkit, you can obtain root, return to stock, flash recovery, etc. However, once you start to run the program, you have no idea what is happening to your device. It comes highly recommended to have the basic knowledge of ADB and fastboot even if you are using toolkits. So, should you use one? Sure! No one will tell you not to try, just know what you're getting into and that most experienced users will not use them at all. Therefore, you are more likely to get helped quickly if you have a basic understanding of fastboot, and a tested and working fastboot/ADB environment on your PC, should an issue arise where you need help. Toolkits are absolutely awesome and highly useful in some situations, so don't underestimate their usefulness. It is just that with a Nexus, and a few simple fastboot commands, you can obtain root, return to stock, flash recovery, etc. While typing those commands, you can be 100% certain of what is happening to your device.
[SIZE=+1]Q14: What is CMTE(cyanogenmod theme engine?[/SIZE]Here is a better explanation here And please take note, This is only supported by ROMS that has already adopted CMTE instead of Layers.
[SIZE=+1]Q15: What is Layers (RRO)?[/SIZE]Layers is a extension of runtime resource overlay.
RRO is a framework created by sony for use as a way for them to create xperia themes but also for internal quick prototyping. More explaination from the original thread here. And take note, this is only going to work with ROMs that has adopted to use layers instead of CMTE. Stock roms natively support layers. Just need to download necessary apps and your good to go.
[SIZE=+1]Q16: Systemless Root?[/SIZE]A new way of getting root without modifying /system. More news here.
[SIZE=+1]Q17: Android Pay?[/SIZE]If your running stock and not rooted, no doubt its gonna work out of the box. There was a previous discussion on how to run the feature on rooted devices. It was fun while it lasted. And here is the latest story about android pay.
[SIZE=+1]Q18: I'm trying to search for something specific but I'm having trouble. How do I use XDA Search?[/SIZE]Look HERE for a detailed guide on how to use XDA Search to it's fullest capabilities.*
And here are some terms to ponder
ADB - "Android Debug Bridge" a system that can be accessed using a computer where you can manage the device from. You need the Android SDK to use it.
AOSP - "Android open source project" a project by Google Inc. to give android to developers and manufactures for free.
APK - "Android Package" an Android application
Bloatware - Software or 'apps' that you don't need, but come preinstalled to a device's /system partition, meaning that you cannot remove them unless the device has been rooted. Usually, these are apps are sponsored by a company and included by a carrier for profit
CDMA/GSM - A type of network communication between phones and carriers. GSM phones normally are included with SIM Cards that authorize them onto the network. CDMA have this authorization built in and do not need a sim card.
Custom recovery - A modified version of stock recoveries that allow you to do more things in the recovery mode.
Cyanogenmod (CM) - A free open-source project based on the AOSP. It is a modded version of the Android firmware
Dalvik-Cache - Holds all of the pre-compiled .dex files created from installed apps. These files are static and do not change unless the app is updated.
Deodexed - Where ODEX files are moved into the actual applications modded) version of the Android firmware.
Developer - A man or woman who has created (developed) software.
Firmware - a piece of software to make hardware function correctly. This can refer to Radio Firmware, but is normally used as another name for ROM.
Governor - A system embedded into the kernel to automatically change the current working CPU frequency depending on the workload. It would only go up to what it is overclocked (or underclocked) to, this is called the maximum frequency. It would not drop below the minimum frequency.
KANG - The process of creating a code based of someone else's code.
Kernel - An important part of all operating systems that handles the CPU and other vital components. A modded kernel may be used for overclocking.
Logcat - A logging system built into the ADB
Mod - A modification to a part of the phones software. It is also POSSIBLE to mod the phones hardware but is not recommended.
OTA - "Over the air" a term used to indicate software that was sent to phones directly through the internet to their phones.
Open-source - (not to be confussed with free) A peice of software that is free to edit, use, distribute and share with no charge.
Overclock - To exceed the default maximum CPU speed. This could make a phone more powerful but may cause damage. Although no damaged has been reported so far it could still drain battery life.
Radio Firmware - A type of software that allows correct communication with the radio and the operating system. A newer firmware would normally improve battery life and call quality. The radio firmware only applies to the CDMA/GSM radio.
Radio - (not to be confused with Radio Firmware) A piece of hardware that allows communication. There are 3 main radios in your phone. Bluetooth, WiFi and GSM/CDMA.
ROM -
1. A modified version of the Android operating system operating system.
2. Read Only Memory, a place where information is stored and can not be destroyed, modified or written to.
Stock - An unchanged version of something. Example: I just flashed stock sense.
Underclock - To change your phones maximum frequency to LOWER than the default to attempt to extend the phones lifespan and battery.
WIP - "Work In Progress"
Zipalligned - An archive alignment tool that provides important optimization to Android application (.apk) files. The purpose is to ensure that all uncompressed data starts with a particular alignment relative to the start of the file. Specifically, it causes all uncompressed data within the .apk, such as images or raw files, to be aligned on 4-byte boundaries. This allows all portions to be accessed directly with mmap() even if they contain binary data with alignment restrictions. The benefit is a reduction in the amount of RAM consumed when running the application.
INTL - International
Odex - Files that are collections of parts of an application that are optimized before booting. Doing so speeds up the boot process, as it preloads part of an application.
Recovery Mode - A special environment that you can boot into for troubleshooting and upgrading purposes
Thanks to @benjamingwynn for the glossary of terms
Click to expand...
Click to collapse
Forum Rules | New Users Guide | XDA Tour | Report Posts
This FAQ is part of a Recognized Contributor Group Initiative. Please look for a similar FAQ thread when visiting another device forum.
A special thanks to everyone who contributed to the production of this FAQ
This thread is an ongoing process. This will be a WIP for a period of time
Click to expand...
Click to collapse
This is not intended to be a Q&A help thread. Please only post suggestions for content that should be added to the OP. Post the relevant links to accompany your request.
If you need help or have a general question, consider using these links:
Ask any question/Noob friendly: http://forum.xda-developers.com/nexus-6/help/noob-friendly-qa-help-thread-t3068327
General question and off topic: http://forum.xda-developers.com/nexus-6/general/google-nexus-6-t3077130
Otherwise, create a new post here: http://forum.xda-developers.com/nexus-6/help
A suggestion. Maybe have some info on encrypted vs decrypted, what it is how it works,how to decrypt and stay that way. This thread has a file that you flash in recovery to make sure encryption does not get forced while flashing a ROM or kernel (don't know if I broke any rules by linking without permission if I did let me know this is NOT my work all credit goes to the dev) http://forum.xda-developers.com/showthread.php?t=3000788. Also maybe a link to the noob question thread (though it looks like it's one post above for now) thanks for this thread always nice to just read something to find an answer and not have to make a useless post.
elevatorguy said:
A suggestion. Maybe have some info on encrypted vs decrypted, what it is how it works,how to decrypt and stay that way. This thread has a file that you flash in recovery to make sure encryption does not get forced while flashing a ROM or kernel (don't know if I broke any rules by linking without permission if I did let me know this is NOT my work all credit goes to the dev) http://forum.xda-developers.com/showthread.php?t=3000788. Also maybe a link to the noob question thread (though it looks like it's one post above for now) thanks for this thread always nice to just read something to find an answer and not have to make a useless post.
Click to expand...
Click to collapse
Excellent suggestion, I will get something together tomorrow. Thank you.
"is there a thread with links to important guides and information ?"
"yes, general > sticky roll-up"
Or maybe reword question 1 a little so people know that's where guides are.
rootSU said:
"is there a thread with links to important guides and information ?"
"yes, general > sticky roll-up"
Or maybe reword question 1 a little so people know that's where guides are.
Click to expand...
Click to collapse
Done. Thanks!
elevatorguy said:
A suggestion. Maybe have some info on encrypted vs decrypted, what it is how it works,how to decrypt and stay that way. This thread has a file that you flash in recovery to make sure encryption does not get forced while flashing a ROM or kernel (don't know if I broke any rules by linking without permission if I did let me know this is NOT my work all credit goes to the dev) http://forum.xda-developers.com/showthread.php?t=3000788. Also maybe a link to the noob question thread (though it looks like it's one post above for now) thanks for this thread always nice to just read something to find an answer and not have to make a useless post.
Click to expand...
Click to collapse
Done, thanks again.
rootSU said:
One day we'll rebel
Click to expand...
Click to collapse
Question 18 added to build the rebel forces.
Question 19 added.
Question 20 seems to be a frequent flyer.
Thread has been cleaned per OP request.
Please only post questions with answers, you feel would help your fellow Nexus 6 user.
All other conversion... please bring to a new thread or the lounge:good: Keeping in mind this is not a Q&A thread.
Thank you @Evolution_Tech for continued updates.
Questions 21 and 22 added since we have a new update.
Question 23...toolkits.
Post #2 updated with links to general help threads.
cam30era said:
@Evolution_Tech,
While responding to a thread this morning, I was "asked" to change to the New 2015 XDA thread view (web view). Not sure I like it, but that's not why I'm here. What's the difference between "commenting" on a post and "posting a reply"?
Update: Weirder still, some on the comments aren't even viewable in the XDA Premium app. Just shows a web link....... @danarama 's Black Screen thread.
Click to expand...
Click to collapse
I specifically chose a new template for that thread which allows answers to be "up voted" as you may have seen on many technical sites, most prominently, Microsoft technet.
The apps can't handle it so they make you use a browser.
Reply is an answer or solution. Comments are to a particular answer, so for example, I can say "tried that" without creating a response that is seen as a votable answer.
Question #24 added. How to use XDA Search.
updates coming.. stay tuned
Hey guys I'm new here and hope this is the correct forum. I recently purchased a nexus 6 off amazon and when it arrived I was surprised to find it had been rooted already. I want to set it back to original stock image but I'm not sure which version to download. I don't know which provider it was originally on. It is on Verizon now. Can I just download mmb29q and expect it to work? System info says I have mmb29u but there is no option for that version. Thank you.
Any version will work but all marshmallow builds are unified and 29q is the latest factory image
MassiveDynam1c said:
Hey guys I'm new here and hope this is the correct forum. I recently purchased a nexus 6 off amazon and when it arrived I was surprised to find it had been rooted already. I want to set it back to original stock image but I'm not sure which version to download. I don't know which provider it was originally on. It is on Verizon now. Can I just download mmb29q and expect it to work? System info says I have mmb29u but there is no option for that version. Thank you.
Click to expand...
Click to collapse
this is not q&a thread. this is for the most common FAQ's..
but to answer ur question. go with 29q. this is the latest stock firmware .
how did u ever got 29u as a stock rom? thats the latest aosp. nexus 6 never had a 29u stock firmeware
Related
This is the latest Flashtool 0.9.13.0:
Download here: Mod edit - links removed
Flashtool is a S1 flashing software that works for all Sony phones from X10 to Xperia Z Ultra. They all use the S1 protocol for flashing firmwares.
This program was originally made to flash sin files downloaded by SEUS or PCC. From time to time, sin files have been bundled into what is now well known FTF (Flash Tool Firmwares). That is the core of Flashtool and the reason of its name.
Flashtool can also easily unlock the bootloader of the phone using the BLU icon as far as the bootloader of your phone is unlockable
The flashing feature as well as bootloader unlock feature are available whatever the phone is recognized or not by the application. What is only mandatory for flashing is to own the FTF file according to the device you want to flash it on.
Why should I use flashtool ?
Once bootloader unlocked, official sony tools do not work anymore.
Using official sony tools, you can only upgrade. No downgrade possible.
Using flashtool, you can choose what to flash and what not to flash. This said, many rooting scenarios are available implying kernel only downgrade to retrieve a patched rooting exploit and then flash back the right kernel.
You said unlocking bootloader ?
This process gives you the opportunity to flash custom roms such as CyanogenMod ROMs.
I invite you to visit the FXP Project that brings CM to xperia devices.
Many other features have been built-in so that Flashtool can also be used to (as far as the phone is recognized by Flashtool) :
Root your phone
Install recovery, busybox, custom kernels
Clean your rom (remove /system/apps apps of your choice) (Be careful, unless you really know what you do, do not modify the default list. This can make your phone stuck at the SE Logo)
Clear dalvik cache
Optimize (install of JIT v2) (plugin for 2.1 phones only from 2010 line)
Customize (installs apps found in the custom/apps folder of the flashtool)
Edit any text file on the device
Rebrand your device
Hi.... what different with this http://www.flashtool.net/index.php
sorry confused for this thread....
this thread should be reported and deleted... nothing new about flashtool. he just uploaded the .exe file to uploaded server and uploaded pays some money to the uploader for each download.
this user posted exactly this in a spanish forum...
if you look for flashtool in google you can find the original web and links in download section
There is a topic about Flashtool already as well. http://forum.xda-developers.com/showthread.php?t=1000012
Thread closed for the following rule violations:
12. Using the work of others.
If you are developing something that is based on the work of another Member, you MUST first seek their permission and you must give credit to the member whose work you used. If a dispute occurs about who developed / created a piece of work, first try to settle the matter by private message and NOT in open forum. If this fails, you may then contact a Moderator and provide clear evidence that the work was created by you.
Convincing evidence will result in the copied work being removed. If there is no clear evidence that it was you who created the work, then in the spirit of sharing, all work will remain posted on the forums.
As an addition, developers have the right to hold exclusivity over their work for as long as it is deemed necessary by that developer. However, if the work is claimed as exclusive, it must remain as such. No selective sharing will be allowed (ie, allowing certain people to use it and not others). Should the developer decide to start sharing the work with others, the work automatically becomes fair game for all to use, albeit with the relative credit displayed.
In regard to permissions, the same rules apply for this but if permission was already given and unless there is a very valid reason, it cannot be revoked (same applies to major updates on the work). Under that same premise, permissions cannot be denied unless the work is exclusive or under extreme circumstances.
In plain English: If you want to keep your work exclusive, go for it. However, if you are going to share your work, do it fairly.
These rules apply to all software posted on XDA (including but not limited to ROMs, RUUs, apps, games, kernels, themes, icons, etc) unless that software comes with a license that waives these rules.
Click to expand...
Click to collapse
13. Advertising and Income Generation
Commercial advertising, advertising referral links, pay-per-click links and other income generating methods are forbidden. Do not use XDA-Developers as a means to make money.
Click to expand...
Click to collapse
Deleted
bubba1601 said:
Hi
I have this new device but it's not any of the versions listed here (Nora/Rhyanna)
It's the UK version XT1920-15 sim unlocked, I'm just wandering if the steps to unlock/root are the same on this device as the other versions?
Click to expand...
Click to collapse
https://www.getdroidtips.com/unlock-bootloader-moto-e5-play/
I used this guide to unlock it. I also have this phone, but mine is from latin america, and it should work for yours. :good:
Deleted
bubba1601 said:
Your device is not the same.
The American / latin American version has android 8.0, 2 GB ram and a 5.2 inch screen.
The UK version has android 8.1, 1gb of ram and a 5.3 inch screen.
All such tutorials that work for the US version DON'T work on the UK version and TWRP installation fails completely.
Please be mindful when advising users things "should" work, as it doesn't work and your device is completely different to mine, so should not be attempted from that link.
Click to expand...
Click to collapse
No my phone has 1Gb of Ram and 16gigs of storage space along with 8.1 and TWRP installed. I used that guide to unlock the bootloader the TWRP in that guide doesn't work for our phones. I managed to find the TWRP version of the phone.
Deleted
bubba1601 said:
The guide says it's for android 8.0 though?
I still can't unlock the bootloader!
Click to expand...
Click to collapse
fastboot oem get_unlock_data
"Now command will return a string which you need to copy the string to a notepad with a single line by deleting all spaceNotepad
(Note: Only copy the highlighted sections above. Do not copy the INFO or (bootloader) prefix)"
"To Get Bootloader Key for Moto E5 Play - Open the website Motorola’s unlock the bootloader site by Signing up or Log in in via Google Plus account"
Link:https://accounts.motorola.com/ssoau...ct/standalone/bootloader/unlock-your-device-b
Make an account, also check if your device can even be unlocked on the website.
"Once you click the "Can my Device be unlocked?" you will receive a mail with unlock key.
Now copy the unlock key and type the following command and enter.
fastboot oem unlock UNLOCK_KEY
Here UNLOCK_Key is the place where you have to paste the unlock key which you copied from the email.
That's it! Your device will unlock. hah! Have fun!"
That's how you unlock the boot loader
Link for TWRP for PETTYL:https://mega.nz/#!anwAACZT!MJ95FCiIDH-kkLaZLpFvnKT5j_3Fe2goU-aZmSVeCKo
I couldn't find on XDA so I uploaded it to mega.
Deleted
Here a twrp buckup Twrp image and rooted boot for XT1920-15 if you manage to boot into twrp or try booting boot image https://drive.google.com/drive/u/0/mobile/folders/1P0yVep9l3yTN2Hzy7QiRXj3kuL_N7Dxz?usp=sharing
did the op get it sorted
Deleted
bubba1601 said:
I'm running stock again.
No root, no twrp and as far as I'm concerned, project treble ROMs/images are complete waste of time, especially for this device where half the posted steps don't work, supplied resources don't work or twrp images and twrp back ups supposedly for this device don't work
Worse still, I had to pay to redownload my firmware.
Click to expand...
Click to collapse
No idea why it dosent work for you I maneged to flash twrp and root it with magisek also tried linege and ResurexionRemix it works fine only xposed dosent work
Deleted
plscotland said:
Here a twrp buckup Twrp image and rooted boot for XT1920-15 if you manage to boot into twrp or try booting boot image https://drive.google.com/drive/u/0/mobile/folders/1P0yVep9l3yTN2Hzy7QiRXj3kuL_N7Dxz?usp=sharing
Click to expand...
Click to collapse
Can I flash this Recovery to XT1920-16 pettyl?
The file Moto_E5_XT1920-15-recovery.img is TWRP or STOCK recovery?
Also i'm loocking for Stock recovery for XT1920-16
Deleted
I just build custom recovery for pettyl -- ORANGE FOX , download at orangefox.tech
thanks. enjoy!
~whodat aka flash
Deleted
bubba1601 said:
There's already three different TWRPs for PETTYL.....two work one doesn't.
I made a TWRP for pettyl and it works 100% , The reason the others do not work is because they have EXT4 filesystem set to data partitions in the fstabs they were made with. Data partition is set to f2fs and thus it cannot be read. I also made a decrypt.zip for pettyl aswell, and I do not even own this device... I have only dove into android dev less than 2 months ago
Many people are already confused about twrp so do we really need another one to confuse everyone even more?
Click to expand...
Click to collapse
*triple facepalm* are you serious ?!?!
Maybe this site and android modifications is not for you bubba.
---------- Post added at 12:44 PM ---------- Previous post was at 12:32 PM ----------
bubba1601 said:
The comment you quoted says it's a TWRP file and I've not seen the stock recovery available for PETTYL .
Just bear in mind that I'm assuming the xt1920-15 that I have and txt1920-16 you have are identical, but I obviously cannot confirm that or do I know if they work the same I'm just assuming they do.
Click to expand...
Click to collapse
lol to get stock recovery file all you have to do is fastboot boot TWRP or OrangeFox and make a backup of recovery. Its that simple, but what would anyone want with stock recovery anyway?
If you really want it you can get the full stock firmware here, extract it and you will have stock recovery.img along with stock boot.img and everything else....
https://mirrors.lolinet.com/firmware/moto/pettyl/official/
Again, ENJOY!
Deleted
bubba1601 said:
If you had explained what's better or different about your recovery rather than making a mocking reply I would not have asked if another custom recovery was necessary......
There's currently two working TWRPs for PETTYL and another posted on here that doesn't work at all.
Every PETTYL user that's posted here has had issues with both TWRP versions or have been unable to follow the instructions on how to install either version.
Don't tell me this site and android modding isn't for me, because when the time is right I'll decide to stop, you will not make that decision or suggest I stop because you didn't like my question - which you didn't answer.
So I'll ask you calmly and politely again.
Is it really necessary to have so many different TWRPs and custom recovery for PETTYL?
What does your orange fox offer different to TWRP?
You haven't even posted a proper link......no explanation, no proceedures, no instructions. Nothing.
Explain yourself so people understand, don't mock.
Edit.
My question was not a criticism of what you have done.
I've stopped any further modifications to my own PETTYL because it's obvious a 1gb ram android go device cannot handle 9.0 pie and in the 10 years I've been modding various devices the E5 play is the most complicated piece of S*** I've I've used.
But even worse, if the user base cannot ask a simple question of people without someone like you being rude and sarcastic in reply and telling a fellow user to go away - then I've made the right decision not to work with my E5 or this thread any longer.
The user and support base for the E5 play PETTYL has suddenly hit an all time low, and doesn't need rudeness or your sarcasm to justify its existence..
Click to expand...
Click to collapse
He explained y other recoveries had prob and y his wouldn't next it has added features such as built in magisk and etc. test it to see other extra features instead of being a lil upset and taking it out on ppl being nice and fixing ur recovery probs
bubba1601 said:
If you had explained what's better or different about your recovery rather than making a mocking reply I would not have asked if another custom recovery was necessary......
There's currently two working TWRPs for PETTYL and another posted on here that doesn't work at all.
Every PETTYL user that's posted here has had issues with both TWRP versions or have been unable to follow the instructions on how to install either version.
Don't tell me this site and android modding isn't for me, because when the time is right I'll decide to stop, you will not make that decision or suggest I stop because you didn't like my question - which you didn't answer.
So I'll ask you calmly and politely again.
Is it really necessary to have so many different TWRPs and custom recovery for PETTYL?
What does your orange fox offer different to TWRP?
You haven't even posted a proper link......no explanation, no proceedures, no instructions. Nothing.
Explain yourself so people understand, don't mock.
Edit.
My question was not a criticism of what you have done.
I've stopped any further modifications to my own PETTYL because it's obvious a 1gb ram android go device cannot handle 9.0 pie and in the 10 years I've been modding various devices the E5 play is the most complicated piece of S*** I've I've used.
But even worse, if the user base cannot ask a simple question of people without someone like you being rude and sarcastic in reply and telling a fellow user to go away - then I've made the right decision not to work with my E5 or this thread any longer.
The user and support base for the E5 play PETTYL has suddenly hit an all time low, and doesn't need rudeness or your sarcasm to justify its existence..
Click to expand...
Click to collapse
Don't be a d*$k lashing out at a dev who does this work FOR free using up HIS free time to make it possible for you to make this complaint. We developers have to research to gain this knowledge. Be courteous and try to search the web to find the answers you seek and to fill in the blanks. Possibly guide others users in the right direction based on the knowledge you discover.
Don't bite the hand that feeds you. Listen to some nine inch nails, you might learn a thing or two about how to properly human.
He doesn't even own that device yet goes out of his way to provide support for it just for ungrateful individuals such as yourself to lash out at him for not explaining things clearly enough. If you lack the knowledge to fill in the blanks that he may have missed, that just shows that you're at risk of bricking your device from lack of knowledge on the subject. It won't hurt you to do a bit of research for yourself.
Sincerely,
The guy helping to guide that developer you lashed out at to supporting 64bit for YOUR DEVICE.
So this is my first thread and had a heck of a time trying to successfully root the 6t using Magisk and TWRP. Why might you ask? Because the unofficial TWRP for the Oneplus 6T has a bug with the Media Transfer Protocal (MTP) so once TWRP is installed, you can't use it to install flashable zips. The device shows the 6T internal storage as empty and therefor you cant flash a zip if TWRP cant find a zip to flash. So anyways heres what I did to get this working.
*****NOTE***** I am not a dev, i simply stumbled across a solution (work-around), to the TWRP MTP issue, and therefor if anything goes wrong with your device, it is on you. DO NOT BLAME ME if you brick your device. If you so choose to follow this guide, ANY/ALL risk and the subsequent consequences, are YOURS AND YOURS ALONE.
***CREDITS*** TO: @topjohnwu for MAGISK & @mauronofrio for his unofficial android Q TWRP
STEP1: Grab this TWRP https://androidfilehost.com/?fid=1395089523397961761
STEP2: Grap magisk beta v19.2 https://github.com/topjohnwu/Magisk/releases/download/v19.2/Magisk-v19.2.zip
STEP3: Run the following command: fastboot flash boot twrp.img
***NOTICE ABOVE COMMAND*** (uses "flash boot" instead of "boot")
STEP4: Manually reboot into back into recovery
***NOTE*** once in recovery I used "swipe to allow modifications" , dont know if it matters
STEP5: Go to adb sideload tab from within TWRP Recovery
STEP6: Once adb sideload finishes loading, run the following command: adb sideload magisk.zip
STEP7: Let sideload finish, reboot device, open magisk app and follow its instructions to finish install.
kluongo said:
So this is my first thread and had a heck of a time trying to successfully root the 6t using Magisk and TWRP. Why might you ask? Because the unofficial TWRP for the Oneplus 6T has a bug with the Media Transfer Protocal (MTP) so once TWRP is installed, you can't use it to install flashable zips. The device shows the 6T internal storage as empty and therefor you cant flash a zip if TWRP cant find a zip to flash. So anyways heres what I did to get this working.
*****NOTE***** I am not a dev, i simply stumbled across a solution (work-around), to the TWRP MTP issue, and therefor if anything goes wrong with your device, it is on you. DO NOT BLAME ME if you brick your device. If you so choose to follow this guide, ANY/ALL risk and the subsequent consequences, are YOURS AND YOURS ALONE.
***CREDITS*** TO: @topjohnwu for MAGISK & @mauronofrio for his unofficial android Q TWRP
STEP1: Grab this TWRP https://androidfilehost.com/?fid=1395089523397961761
STEP2: Grap magisk beta v19.2 https://github.com/topjohnwu/Magisk/releases/download/v19.2/Magisk-v19.2.zip
STEP3: Run the following command: fastboot flash boot twrp.img
***NOTICE ABOVE COMMAND*** (uses "flash boot" instead of "boot")
STEP4: Manually reboot into back into recovery
***NOTE*** once in recovery I used "swipe to allow modifications" , dont know if it matters
STEP5: Go to adb sideload tab from within TWRP Recovery
STEP6: Once adb sideload finishes loading, run the following command: adb sideload magisk.zip
STEP7: Let sideload finish, reboot device, open magisk app and follow its instructions to finish install.
Click to expand...
Click to collapse
The twrp we have works fine dude
Lol
And you are referring to using TWRP on Android Q beta correct??? Because when I tried using the latest stable TWRP for 6T but with Android Q... It would not flash
JUST FYI
The mtp issue is a known bug with the Q developer preview.
Rite from download page.
"Known Issues
Camera, portrait mode does not work
Ambient Display is not working
System stability issues
Encryption will change in the next preview build
Some apps may not function as expected when running on this Developer preview release
Issue With MTP cannot copy rollback from PC to Phone."
Not with twrp.
The only issue with twrp at the moment is reading v3 synthetic keys to decrypt if you have pin/password set and running may security patch.
kluongo said:
And you are referring to using TWRP on Android Q beta correct??? Because when I tried using the latest stable TWRP for 6T but with Android Q... It would not flash
Click to expand...
Click to collapse
Thank you twinn for clarifying that... So I stand corrected on twinns point... But not on fullofhells needless comment
kluongo said:
Thank you twinn for clarifying that... So I stand corrected on twinns point... But not on fullofhells needless comment
Click to expand...
Click to collapse
Use Blu spark, secondly the resolution for mtp, is enable dev options and turn on USB file transfer. Then USB works. Use a prepatched twrp and pre rooted twrp Blu spark kernel. Flash in fastboot, twrp works fine. Fully. Not apparently not needless if u still have issues posting erroneous comments that serve no purpose. U should read. It serves so many purposes. U would see the fix for mtp on Q and how in the main twrp thread a week or more ago I discussed how twrp works fine if u do as I listed there.. I read everything, I assumed every other user does the same.
fullofhell said:
Use Blu spark, secondly the resolution for mtp, is enable dev options and turn on USB file transfer. Then USB works. Use a prepatched twrp and pre rooted twrp Blu spark kernel. Flash in fastboot, twrp works fine. Fully. Not apparently not needless if u still have issues posting erroneous comments that serve no purpose. U should read. It serves so many purposes. U would see the fix for mtp on Q and how in the main twrp thread a week or more ago I discussed how twrp works fine if u do as I listed there.. I read everything, I assumed every other user does the same.
Click to expand...
Click to collapse
:highfive:
WOW.
Where to start here?
The TWRP you linked (https://androidfilehost.com/?fid=1395089523397961761) is for OPO 6, not 6T, but it does say fajita, and not enchilada
TWRP works fine for us, if you use the latest.
P and Q are different beasts, as of now, and there are posts on how to flash TWRP on Q.
This thread seems redundant an unnecessary.
But....that's just my $.02
So first, i just searched all 9 pages of the 6t Guides thread section... not one single thread explaining, or detailing, any guide or tutorial, for individuals to play around with Q... On that point, not redundant.... Secondly the fajita image i posted is not for the 6... its from mauronofrio for the 6t, under the thread he started for twrp images for the 6t... so.. if it is in fact for the 6... maybe he should be notified?..... and if this thread is redudnant, why cant i find any guide detailing steps to mess around with Q?
kluongo said:
So first, i just searched all 9 pages of the 6t Guides thread section... not one single thread explaining, or detailing, any guide or tutorial, for individuals to play around with Q... On that point, not redundant.... Secondly the fajita image i posted is not for the 6... its from mauronofrio for the 6t, under the thread he started for twrp images for the 6t... so.. if it is in fact for the 6... maybe he should be notified?..... and if this thread is redudnant, why cant i find any guide detailing steps to mess around with Q?
Click to expand...
Click to collapse
Here's a thread about Q on the 6T: https://forum.xda-developers.com/oneplus-6t/how-to/oneplus-6t-androidq-beta-release-links-t3928174 (specifically post #62)
The TWRP link page you linked specifically says "Download test-twrp-3.3.0-Q-fajita.img for the OnePlus OnePlus 6" but I commented that it was correctly for the 6T. I would get ahold of Mauronofrio to inform him of the error.
It's only redundant because after reading the thread I posted above^, it seems we have some waiting to do until we even get a stable Q build.
Thanks!
Yes, I did in fact see that thread and briefly read it over. On the contrary, it did not help me in the manner i needed. Alot of people don't have the time to dig through threads to find an answer to a problem, especially from a thread which was never intended to address said problem in the first place (according to its title, as well as the entire first page of posts). I have been following these forums, quietly, since the galaxy s4 was released and hence, when I look for a guide or missing piece of information I require, i know to read and look around a bit before starting a thread. As such, I have not needed to create a thread EVER... and then there was this problem with no clear cut guide, thread, solution... nada.... so alas, I decided to provide one for a change... I am now reminded why i choose to stay mostly quiet... because xda has become a honeypot full of negative trollers, and "full-of-themself" donald trumps, when it should contain more people offering constructive critisicm, positive environment, and turning the less knowledgeable into the more informed android enthusiast.
Just my $.01
kluongo said:
Yes, I did in fact see that thread and briefly read it over. On the contrary, it did not help me in the manner i needed. Alot of people don't have the time to dig through threads to find an answer to a problem, especially from a thread which was never intended to address said problem in the first place (according to its title, as well as the entire first page of posts). I have been following these forums, quietly, since the galaxy s4 was released and hence, when I look for a guide or missing piece of information I require, i know to read and look around a bit before starting a thread. As such, I have not needed to create a thread EVER... and then there was this problem with no clear cut guide, thread, solution... nada.... so alas, I decided to provide one for a change... I am now reminded why i choose to stay mostly quiet... because xda has become a honeypot full of negative trollers, and "full-of-themself" donald trumps, when it should contain more people offering constructive critisicm, positive environment, and turning the less knowledgeable into the more informed android enthusiast.
Just my $.01
Click to expand...
Click to collapse
No need to stay quiet, just learn to use the search function, and participate on the already created threads instead of creating new ones. (Just a suggestion...)
And the ad hominem attempts are unnecessary.
Love,
'full-of-myself'
No..
Love,
@fullofhellself
?
Damn wth did I do..lol... We are a system of checks and balances for all users. Full of myself... Yeah okay.. better be nice or mom's not gunna pay your internet bill.. and I hate trumpian politics. I just loathe redundant unusable posts. As do my constituents here..
kluongo said:
Yes, I did in fact see that thread and briefly read it over. On the contrary, it did not help me in the manner i needed. Alot of people don't have the time to dig through threads to find an answer to a problem, especially from a thread which was never intended to address said problem in the first place (according to its title, as well as the entire first page of posts). I have been following these forums, quietly, since the galaxy s4 was released and hence, when I look for a guide or missing piece of information I require, i know to read and look around a bit before starting a thread. As such, I have not needed to create a thread EVER... and then there was this problem with no clear cut guide, thread, solution... nada.... so alas, I decided to provide one for a change... I am now reminded why i choose to stay mostly quiet... because xda has become a honeypot full of negative trollers, and "full-of-themself" donald trumps, when it should contain more people offering constructive critisicm, positive environment, and turning the less knowledgeable into the more informed android enthusiast.
Just my $.01
Click to expand...
Click to collapse
Chill out, no need to bring politics into a phone modding forum, seems kinda silly doesn't it? But yes, you should have just gone to the existing 6T Android Q thread and just used the search function. Wouldn't have been that hard. I never even installed Android Q and I even remember reading through numerous posts of people wanting to return to stock. I don't blame you for posting or anything, I'm just letting you know that there definitely was a clear-cut easy way to find a way to go to stock from the Q beta.
LMAO xda is getting out of control... I agree with the OP as the other thread is not about this particular issue... Which was getting twrp and magisk going on the Q beta (NOT returning to stock - like where did that even come from if your following along lol)
I could easily see him getting flamed for hijacking the thread if he posted this tutorial in the other person's thread. You can't win for loosing any more.
This is also why I stay mostly silent on here smh!
juggz143 said:
LMAO xda is getting out of control... I agree with the OP as the other thread is not about this particular issue... Which was getting twrp and magisk going on the Q beta (NOT returning to stock - like where did that even come from if your following along lol)
I could easily see him getting flamed for hijacking the thread if he posted this tutorial in the other person's thread. You can't win for loosing any more.
This is also why I stay mostly silent on here smh!
Click to expand...
Click to collapse
omfg. Read post 1. Reread. Read again. Now read your sentences. Try not to feel dumb. Search function = no one wastes time. That's all.
fullofhell said:
omfg. Read post 1. Reread. Read again. Now read your sentences. Try not to feel dumb. Search function = no one wastes time. That's all.
Click to expand...
Click to collapse
[emoji848]Maybe it's you who should re-read. The first post doesn't mention anything about returning to stock. He's trying to install magisk on a BETA, which is the polar opposite of returning to stock [emoji2375][emoji2363]...
If anything having a dedicated thread for a "specific reason" is much easier to find, and less time consuming, than searching for a possible answer in the comments of another thread on a somewhat related post. He's making the search more efficient since you mention "wasting time", you're the one wasting time *****ing on a usefull post lol.
You're assuming installing TWRP is for the purpose of returning to stock but there's a ton of other reasons someone could want to install TWRP and then magisk... Also there's other ways to return to stock besides TWRP soooo [emoji2375] i guess that's a waste of time too...
What are we doing SMH [emoji23][emoji24][emoji88]
Sent from my SM-G975U1 using Tapatalk
juggz14301 said:
[emoji848]Maybe it's you who should re-read. The first post doesn't mention anything about returning to stock. He's trying to install magisk on a BETA, which is the polar opposite of returning to stock [emoji2375][emoji2363]...
If anything having a dedicated thread for a "specific reason" is much easier to find, and less time consuming, than searching for a possible answer in the comments of another thread on a somewhat related post. He's making the search more efficient since you mention "wasting time", you're the one wasting time *****ing on a usefull post lol.
You're assuming installing TWRP is for the purpose of returning to stock but there's a ton of other reasons someone could want to install TWRP and then magisk... Also there's other ways to return to stock besides TWRP soooo [emoji2375] i guess that's a waste of time too...
What are we doing SMH [emoji23][emoji24][emoji88]
Click to expand...
Click to collapse
Who is talking about returning to stock? He's talking about installing TWRP and magisk on Q beta.
Follow the following at your own risk! I am not responsible for any mishaps with your devices. This will NOT obviously work for Verizon, AT&T, and Cricket phones.
Okay, So I've been asking questions, playing, unpacking, and repacking, trying tools, etc. And I got a very experimental port of TWRP happening. VERY EXPERIMENTAL.
THINGS TO KNOW AFTER THE EXCITEMENT DIES DOWN:
For starters, yes THIS DOES BOOT TO TWRP! I'm quite proud about that. This is my first ever port of anything like this. I mostly just fiddle with making bootable stock roms, and not too much since Android 9 and this new nuts file system. Anyway, I set out to try and get a TWRP together for this phone and that happened, so I'm proud of myself I didn't get discouraged.
Having said that, it has ZERO touchscreen functionality. From my research this was also an initial problem for the peeps over at the Moto One 5G Plus variant (Nairo) before they worked out the bugs. Hopefully they will take mercy on us and come give some feedback.
Also, this is a port. I used @Hovatek's Qualcomm tool to accomplish this since unpacking, repacking, copying and pasting a port from Nairo in the Carliv Image Kitchen or Android Image Kitchen just soft bricked my phone. It also doesn't help the traditional porting methods prior to Android 9 don't work anymore. They came up with a great tool, Gawd Bless Em'.
Should you try this for hoots and giggles just know you will have to hard reset. Android will force a factory reset because of the vbmeta flashing, and your phone will be factory brand spanking new. Backup your contacts, pics, messages, and anything else you want to keep just in case.
I'm not going to put detailed instructions on this just yet since it's experimental - this is really for folks that know what they're doing with their phone.
Notes:
You must have the bootloader unlocked and be rooted with Magisk for this to fly. Can't say how this would work on locked bootloaders without root so proceed cautiously on that.
1. Flash VBmeta first. The VBMeta is a blank file and that's to make sure DM-Verity isn't acting up (which as of now I'm 50% certain it is and that's why I had to go ahead and factory reset). The commands to disbale dm-verity didn't work for me. If anybody knows how to get that shut off please add to the discussion.
2. I didn't replace my original recovery. I just did fastboot boot recovery image to see if it would load. I wouldn't advise flashing it to replace the current recovery as it might seriously bootloop.
If anybody wants to try and work on this with me (or take over since I'm a hobbyist at best) then by all means share. But at least now we're getting somewhere, slowly but surely.
Today was a good day in hacking Android 10 on this phone.
Articul8Madness said:
Follow the following at your own risk! I am not responsible for any mishaps with your devices. This will NOT obviously work for Verizon, AT&T, and Cricket phones.
Okay, So I've been asking questions, playing, unpacking, and repacking, trying tools, etc. And I got a very experimental port of TWRP happening. VERY EXPERIMENTAL.
THINGS TO KNOW AFTER THE EXCITEMENT DIES DOWN:
For starters, yes THIS DOES BOOT TO TWRP! I'm quite proud about that. This is my first ever port of anything like this. I mostly just fiddle with making bootable stock roms, and not too much since Android 9 and this new nuts file system. Anyway, I set out to try and get a TWRP together for this phone and that happened, so I'm proud of myself I didn't get discouraged.
Having said that, it has ZERO touchscreen functionality. From my research this was also an initial problem for the peeps over at the Moto One 5G Plus variant (Nairo) before they worked out the bugs. Hopefully they will take mercy on us and come give some feedback.
Also, this is a port. I used @Hovatek's Qualcomm tool to accomplish this since unpacking, repacking, copying and pasting a port from Nairo in the Carliv Image Kitchen or Android Image Kitchen just soft bricked my phone. It also doesn't help the traditional porting methods prior to Android 9 don't work anymore. They came up with a great tool, Gawd Bless Em'.
Should you try this for hoots and giggles just know you will have to hard reset. Android will force a factory reset because of the vbmeta flashing, and your phone will be factory brand spanking new. Backup your contacts, pics, messages, and anything else you want to keep just in case.
I'm not going to put detailed instructions on this just yet since it's experimental - this is really for folks that know what they're doing with their phone.
Notes:
You must have the bootloader unlocked and be rooted with Magisk for this to fly. Can't say how this would work on locked bootloaders without root so proceed cautiously on that.
1. Flash VBmeta first. The VBMeta is a blank file and that's to make sure DM-Verity isn't acting up (which as of now I'm 50% certain it is and that's why I had to go ahead and factory reset). The commands to disbale dm-verity didn't work for me. If anybody knows how to get that shut off please add to the discussion.
2. I didn't replace my original recovery. I just did fastboot boot recovery image to see if it would load. I wouldn't advise flashing it to replace the current recovery as it might seriously bootloop.
If anybody wants to try and work on this with me (or take over since I'm a hobbyist at best) then by all means share. But at least now we're getting somewhere, slowly but surely.
Today was a good day in hacking Android 10 on this phone.
Click to expand...
Click to collapse
Hi. I appreciate a lot your efforts. I know the feeling when you progress with stuff like this. I'm sorry I have no time in these months to assist. Anyway, I hope you'll manage to go forward with this. Keep up with the good work.
useless789 said:
Hi. I appreciate a lot your efforts. I know the feeling when you progress with stuff like this. I'm sorry I have no time in these months to assist. Anyway, I hope you'll manage to go forward with this. Keep up with the good work.
Click to expand...
Click to collapse
CAn you at least tell me how to port a TWRP on Android 10? Can't find any useful information with the new filetypes.
Articul8Madness said:
CAn you at least tell me how to port a TWRP on Android 10? Can't find any useful information with the new filetypes.
Click to expand...
Click to collapse
I'm not sure what you mean by filetypes. Do you mean the A/B partitions (and the fact that there's no separate recovery partition) or something else?
Articul8Madness said:
Follow the following at your own risk! I am not responsible for any mishaps with your devices. This will NOT obviously work for Verizon, AT&T, and Cricket phones.
Okay, So I've been asking questions, playing, unpacking, and repacking, trying tools, etc. And I got a very experimental port of TWRP happening. VERY EXPERIMENTAL.
THINGS TO KNOW AFTER THE EXCITEMENT DIES DOWN:
For starters, yes THIS DOES BOOT TO TWRP! I'm quite proud about that. This is my first ever port of anything like this. I mostly just fiddle with making bootable stock roms, and not too much since Android 9 and this new nuts file system. Anyway, I set out to try and get a TWRP together for this phone and that happened, so I'm proud of myself I didn't get discouraged.
Having said that, it has ZERO touchscreen functionality. From my research this was also an initial problem for the peeps over at the Moto One 5G Plus variant (Nairo) before they worked out the bugs. Hopefully they will take mercy on us and come give some feedback.
Also, this is a port. I used @Hovatek's Qualcomm tool to accomplish this since unpacking, repacking, copying and pasting a port from Nairo in the Carliv Image Kitchen or Android Image Kitchen just soft bricked my phone. It also doesn't help the traditional porting methods prior to Android 9 don't work anymore. They came up with a great tool, Gawd Bless Em'.
Should you try this for hoots and giggles just know you will have to hard reset. Android will force a factory reset because of the vbmeta flashing, and your phone will be factory brand spanking new. Backup your contacts, pics, messages, and anything else you want to keep just in case.
I'm not going to put detailed instructions on this just yet since it's experimental - this is really for folks that know what they're doing with their phone.
Notes:
You must have the bootloader unlocked and be rooted with Magisk for this to fly. Can't say how this would work on locked bootloaders without root so proceed cautiously on that.
1. Flash VBmeta first. The VBMeta is a blank file and that's to make sure DM-Verity isn't acting up (which as of now I'm 50% certain it is and that's why I had to go ahead and factory reset). The commands to disbale dm-verity didn't work for me. If anybody knows how to get that shut off please add to the discussion.
2. I didn't replace my original recovery. I just did fastboot boot recovery image to see if it would load. I wouldn't advise flashing it to replace the current recovery as it might seriously bootloop.
If anybody wants to try and work on this with me (or take over since I'm a hobbyist at best) then by all means share. But at least now we're getting somewhere, slowly but surely.
Today was a good day in hacking Android 10 on this phone.
Click to expand...
Click to collapse
This is tremendously amazing work. TWRP would be a killer feature with the 5G Ace. Couple that with Lenovo having released the source code, and this forum may get popping again!
useless789 said:
I'm not sure what you mean by filetypes. Do you mean the A/B partitions (and the fact that there's no separate recovery partition) or something else?
Click to expand...
Click to collapse
I was referring to the super_sparsechunk type files that when you look at their "filetype" it has 0 image by its name if its super_sparsechunk.0, 1 if its super_sparsechunk.1 and the like. This is different than the old basic img files that read .img. This is where the learning curve for me kicks in.
Articul8Madness said:
I was referring to the super_sparsechunk type files that when you look at their "filetype" it has 0 image by its name if its super_sparsechunk.0, 1 if its super_sparsechunk.1 and the like. This is different than the old basic img files that read .img. This is where the learning curve for me kicks in.
Click to expand...
Click to collapse
I see. Thanks for the explanation. I'm not sure if this could help, but a quick search on google led me to this (a bit old) video:
I'm really busy until the end of the month so I can't really dedicate my time to this stuff though I would love to.
useless789 said:
I see. Thanks for the explanation. I'm not sure if this could help, but a quick search on google led me to this (a bit old) video:
I'm really busy until the end of the month so I can't really dedicate my time to this stuff though I would love to.
Click to expand...
Click to collapse
I see you already tried this here: Post in thread '[Tool] SparseConverter v1.0.1' https://forum.xda-developers.com/t/tool-sparseconverter-v1-0-1.2749797/post-84767377
If I manage I'll take a look at this asap.
useless789 said:
I see you already tried this here: Post in thread '[Tool] SparseConverter v1.0.1' https://forum.xda-developers.com/t/tool-sparseconverter-v1-0-1.2749797/post-84767377
If I manage I'll take a look at this asap.
Click to expand...
Click to collapse
Any and all contributing help is appreciated!
@Articul8Madness I managed to combine the sparse chunk files into a raw image file. I also managed to mount the image, but only in read-only mode. I'll post with updates as I get passed this obstacle.
Seems the US version of this phone isn't popular enough for dev support...oh well I have R/W access so I was able to delete system app bloatware and I have xposed installed. Stock Reteu firmware is working perfectly on Metro...good luck everybody.. I'm looking for a new 5G phone..
Unfortunately, there are no developers here.
All we can produce is a ported twrp where the touchscreen does not work.
The touchscreen does not work due to problems with the porting tool and the smartphone.
I heard that if you build it from source yourself, it will work.
But I can't find any tutorials for android 10+ and I don't even know what files I need.
PEACH-PIT said:
Unfortunately, there are no developers here.
All we can produce is a ported twrp where the touchscreen does not work.
The touchscreen does not work due to problems with the porting tool and the smartphone.
I heard that if you build it from source yourself, it will work.
But I can't find any tutorials for android 10+ and I don't even know what files I need.
Click to expand...
Click to collapse
I posted the source code. The guys over on the Moto One 5G know what tools you need. I was using Carliv's kitchen to build but I've never built before - they had the same problem as us with the touchscreen and had to make modules. That counts me out because that's above my paygrade, lol.
Articul8Madness said:
I posted the source code. The guys over on the Moto One 5G know what tools you need. I was using Carliv's kitchen to build but I've never built before - they had the same problem as us with the touchscreen and had to make modules. That counts me out because that's above my paygrade, lol.
Click to expand...
Click to collapse
Not entirely sure what you mean. If your doing some kind of frankenstein recovery, I'm sure you just failed to copy some module or firmware, obviously the ts works in the official software.
1.) Find out what touchscreen chipset your device uses (you can use kernel log or system info apps or whatever)
2.) Determine which kernel module supports it (all modules built will be in your kernel config)
3.) modprobe that module from adb in your recovery. If it doesn't just work, you will receive some error on the command line or dmesg that you can use to fix it. Could need a configuration file or something, idk. It's likely an opensource module that you can read through and I bet you can find specific info online since your not the first to hit this issue.
If your wondering how to build the kernel, I can help a little, but it's incomplete:
Kernel source:
GitHub - MotorolaMobilityLLC/kernel-msm at MMI-QZK30.Q4-40-52
Linux Kernel for Motorola devices using MSM-based chipset - GitHub - MotorolaMobilityLLC/kernel-msm at MMI-QZK30.Q4-40-52
github.com
Build instructions:
readme/MMI-QPN30.33-40.txt at master · MotorolaMobilityLLC/readme
Readme's for motorola builds. Contribute to MotorolaMobilityLLC/readme development by creating an account on GitHub.
github.com
Snapdragon LLVM Toolchain:
snapdragon-llvm-8.0.6-linux64.tar.gz
drive.google.com
Retail config is on your device:
/proc/config.gz
The instructions don't cover the qcom toolchain, you just take the files here:
snapdragon-llvm-8.0.6-linux64.tar.gz/toolchains/llvm-Snapdragon_LLVM_for_Android_8.0/prebuilt/linux-x86_64/*
and place them here:
$my_top_dir/vendor/qcom/proprietary/llvm-arm-toolchain-ship/8.0/
When building, skip the cat command, and place your config manually to $kernel_out_dir/.config
The step I haven't done is build a device tree. It's not that it's too difficult, I just haven't put in the time required to do it. It's not strictly necessary to achieve for my goals since I only wanted modules and know how to patch the kernel to be able to use them.
https://github.com/moto-sm7250/android_device_motorola_kiev/tree/android-10
Will this not work?
I do not know how to build it.
fddm said:
Not entirely sure what you mean. If your doing some kind of frankenstein recovery, I'm sure you just failed to copy some module or firmware, obviously the ts works in the official software.
1.) Find out what touchscreen chipset your device uses (you can use kernel log or system info apps or whatever)
2.) Determine which kernel module supports it (all modules built will be in your kernel config)
3.) modprobe that module from adb in your recovery. If it doesn't just work, you will receive some error on the command line or dmesg that you can use to fix it. Could need a configuration file or something, idk. It's likely an opensource module that you can read through and I bet you can find specific info online since your not the first to hit this issue.
If your wondering how to build the kernel, I can help a little, but it's incomplete:
Kernel source:
GitHub - MotorolaMobilityLLC/kernel-msm at MMI-QZK30.Q4-40-52
Linux Kernel for Motorola devices using MSM-based chipset - GitHub - MotorolaMobilityLLC/kernel-msm at MMI-QZK30.Q4-40-52
github.com
Build instructions:
readme/MMI-QPN30.33-40.txt at master · MotorolaMobilityLLC/readme
Readme's for motorola builds. Contribute to MotorolaMobilityLLC/readme development by creating an account on GitHub.
github.com
Snapdragon LLVM Toolchain:
snapdragon-llvm-8.0.6-linux64.tar.gz
drive.google.com
Retail config is on your device:
/proc/config.gz
The instructions don't cover the qcom toolchain, you just take the files here:
snapdragon-llvm-8.0.6-linux64.tar.gz/toolchains/llvm-Snapdragon_LLVM_for_Android_8.0/prebuilt/linux-x86_64/*
and place them here:
$my_top_dir/vendor/qcom/proprietary/llvm-arm-toolchain-ship/8.0/
When building, skip the cat command, and place your config manually to $kernel_out_dir/.config
The step I haven't done is build a device tree. It's not that it's too difficult, I just haven't put in the time required to do it. It's not strictly necessary to achieve for my goals since I only wanted modules and know how to patch the kernel to be able to use them.
Click to expand...
Click to collapse
This recovery I built in this thread I used Hovatek's tool to do. I have never built a recovery and I was hoping if someone got the ball rolling we could get a dev to jump in. That hasn't happened.
The guys with the other variant of this phone said they had to create modules. Go to the Moto One 5G forums and see the thread. They had the same problems too, but they had more dev support than we do.
I have never built a TWRP, let alone from source, so half of what you sent I have no idea what it is or how to decompile it (yet).
I have posted the entire Kernel Motorola released its in the other thread. The Device Tree is official and out on github.
Guys, I'm a developer, just that I'm still really busy. I'm following your posts and have looked into some of the stuff, just I'm proceeding slowly due to lack of time. I'll post as soon as I have something working.
useless789 said:
Guys, I'm a developer, just that I'm still really busy. I'm following your posts and have looked into some of the stuff, just I'm proceeding slowly due to lack of time. I'll post as soon as I have something working.
Click to expand...
Click to collapse
Is this the correct twrp for this phone?
Root Motorola One 5G Ace XT2113 and Install TWRP Recovery 3.5.0
Easy tutorial to Root Motorola One 5G Ace XT2113-2, XT2113-3, XT2113-5 easily. For rooting, you have to flash TWRP Recovery 3.5.0 on Android 10 through guide.
www.androidweblog.com
Later guys, keep up the good work
Tomspector said:
Is this the correct twrp for this phone?
Root Motorola One 5G Ace XT2113 and Install TWRP Recovery 3.5.0
Easy tutorial to Root Motorola One 5G Ace XT2113-2, XT2113-3, XT2113-5 easily. For rooting, you have to flash TWRP Recovery 3.5.0 on Android 10 through guide.
www.androidweblog.com
Later guys, keep up the good work
Click to expand...
Click to collapse
This is a fake. It's non-functional garbage.
There is no harm in trying it, unless you flash it, but there is no need to try it.
useless789 said:
Guys, I'm a developer, just that I'm still really busy. I'm following your posts and have looked into some of the stuff, just I'm proceeding slowly due to lack of time. I'll post as soon as I have something working.
Click to expand...
Click to collapse
I have a request to the developers.
GitHub - moto-sm7250/android_device_motorola_kiev at android-10
DT for Moto G 5G / One 5G Ace. Contribute to moto-sm7250/android_device_motorola_kiev development by creating an account on GitHub.
github.com
Can you please build this twrp?
I'm trying to build it.
But I don't know how to solve the error.
I don't think I can build it.
Hi guys. First post here and I'm not around my files so it will be a straight forward guide with no downloads right now, you're smart, you know where to source them...
Ok first and foremost, Unlock your bootloader, Motorola makes it easy and there are good guides on this site to do that.
Once your bootloader is unlocked your going to look for an Unofficial TWRP package for the Lenovo K12 Pro... "What?", You say... Yep K12 Pro. Download it and jump over to your boot loader and flash it or just boot to it through fastboot and now you have a way to install root permanently, or not if you would rather not, but you have that option now.
Next find the lastest Magisk apk and get that joker installed using TWRP. Now reboot into system and everything should load up as normal BUT now you have root with TWRP recovery. I have did this at least 100 times since figuring it out and sometimes I do this with a fresh factory flash and sometimes I do this as is without even wiping user data before or after. I'm no expert and I don't care to lose my files so on the rare occasion that I do have a boot loop or soft brick, I get myself into recovery and flash ANY of the cebu firmwares and do it all over again...
Ok, so now we know how to get root and custom recovery... Next find an AB version of Gsi 11 or "borrow" the latest system.img from an Android 12 update or firmware image and open up fastboot again and flash only the system.image to the system partition. Wipe or don't wipe, up to how lucky you're feeling, and then reboot to system... 11 will take 2-3 minutes to boot the first time and I had nearly all functionality when it did. 12, well, that's a little different, it took 3-4 minutes to boot to the setup screen and then lagged like crazy BUT it eventually started downloading a few files it was missing and got better. I couldn't get my calls or messaging to work right but I could hear my phone ring but it never called the phone app to open and let me answer... Weird stuff BUT FYI 12 is a pretty nice to look at OS and maybe one of you guys can take this to the next level and get some true usefulness out of it. I know it's not very technical but when one of you true geniuses try it and get it worked out please feel free to post a true guide with proper instruction and proper terms.
That's all I got guys. Thanks for reading this and ALSO if anybody has a complete list of fastboot and adb commands for the g9 Power or the K12 Pro please share them with me. I've gotten better at getting around but I'm not near as good as if like to be.
Obligatory safety PSA:
The Lenovo K12 Pro is just the Moto G9 Power sold under a different name, however, there could be minor differences that could cause problems.
Also, while searching for this unofficial TWRP build, I only found it on websites like unofficialtwrp.com, and the like. I couldn't find one on XDA. I was unable to find the device tree, or the kernel sources used by this website anywhere on the internet, and as such, the TWRP images provided on such websites are literal blackboxes.
TWRP images created and shared on XDA can be trusted, the source code used to create the image is displayed on the posts of the images, and XDA itself is a trusted site.
Here is what the official TWRP team have to say on the matter:
Unofficial TWRP Downloads
Like the TWRP team say, it is up to you to flash these images or not, but be careful.
mistersmee said:
Obligatory safety PSA:
The Lenovo K12 Pro is just the Moto G9 Power sold under a different name, however, there could be minor differences that could cause problems.
Also, while searching for this unofficial TWRP build, I only found it on websites like unofficialtwrp.com, and the like. I couldn't find one on XDA. I was unable to find the device tree, or the kernel sources used by this website anywhere on the internet, and as such, the TWRP images provided on such websites are literal blackboxes.
TWRP images created and shared on XDA can be trusted, the source code used to create the image is displayed on the posts of the images, and XDA itself is a trusted site.
Here is what the official TWRP team have to say on the matter:
Unofficial TWRP Downloads
Like the TWRP team say, it is up to you to flash these images or not, but be careful.
Click to expand...
Click to collapse
Agreed, I posted as a proof of concept so people with more know how could improve upon. Use this at your own discretion and have fun in doing so.
Is there a way you could post a detailed, step by step instructions of this, please?
I've found the unofficial twrp, but haven't rooted a phone in over 2 years, so I'm a bit rusty, plus things have changed a lot these last couple years.
I'd really appreciate if you could take your time for that.
Thanks in advance.
I don't mind helping you out but I can't post publicly because the rules of the forum and the fact that it's unofficial. I'll get a guide wrote up and PM you. I've had no issues with my device at all but remember it is use at your own discretion.
Dauksza72 said:
I don't mind helping you out but I can't post publicly because the rules of the forum and the fact that it's unofficial. I'll get a guide wrote up and PM you. I've had no issues with my device at all but remember it is use at your own discretion.
Click to expand...
Click to collapse
That would be awesome mate!
I really appreciate that!
Thanks in advance.
Dauksza72 said:
I don't mind helping you out but I can't post publicly because the rules of the forum and the fact that it's unofficial. I'll get a guide wrote up and PM you. I've had no issues with my device at all but remember it is use at your own discretion.
Click to expand...
Click to collapse
I was able to boot into TWRP but when I flash Twrp.img to recovery it won't stick, I always had to do fastboot into recovery if I try to boot into recovery it just reboots back into system, also can't remove any junkware from system, it always gives me error when I tried to remove it using root browser, im still on stock
zfk110 said:
I was able to boot into TWRP but when I flash Twrp.img to recovery it won't stick, I always had to do fastboot into recovery if I try to boot into recovery it just reboots back into system, also can't remove any junkware from system, it always gives me error when I tried to remove it using root browser, im still on stock
Click to expand...
Click to collapse
Check out https://forum.xda-developers.com/t/recovery-unofficial-twrp-3-5-2-cebu.4279917/
for TWRP.
As for removing junkware, as you may or may not know, dynamic partitions is a thing since Android 10. In it, the /system, /product and /vendor partitions have been subsumed under a /super partition. And Google has conveniently used a type of ext4 filesystem for that /super partition, that is read-only.
TL;DR: You cannot modify Android using any sort of "root browser" or inside TWRP, for that matter, anymore.
Off the top of my head, the only way you can remove "junkware" is through some Magisk modules, and even they might not even work.
There are three ways to debloat AFAIK:
Magisk - this is my preferred method. You either replace apks you want removed or empty the /product/etc/nondisable folder so they can be disabled. Takes minimal effort to figure out how to make modules and no scripting knowledge required.
Cross-flashing - you can flash retail software, often including modem firmware, to most Moto phones. The result is a clean system with no carrier junkware.
System R/W Scripts - this is the most nonsensical of the options(IMO), but this option exists if you look around and want to experiment. The big drawback here is that you have to redo everything after every update.
Dauksza72 said:
I don't mind helping you out but I can't post publicly because the rules of the forum and the fact that it's unofficial. I'll get a guide wrote up and PM you. I've had no issues with my device at all but remember it is use at your own discretion.
Click to expand...
Click to collapse
Hello. I know you're new and welcome. I just want you to know, being an unofficial twrp isn't necessarily bad by itself. It's that the sources can't be verified. Lots of devces don't have official TWRPs, yet still have a rockin development section with TWRP instructions, as long as it's shared on a trusted site (I only trust 1 other) and lists it's sources and, even then, it should have the warning. Lots of scam sites target root noobs, as you've probably noticed. I don't think sharing instructions would have been against the rules, but should include a warning to let people know it's a questionable twrp build and it poses a risk, but all of our phones are at risk anyway. We don't have to worry about it anymore though since we have an official and still we are at risk, just far less risk. It comes with the territory. On the other hand, I've been I've been doing this for a very long time with countless phones and I've never noticed any malicious activity on any on any of them.