Related
I have a P10 with the following info:
Model number: VTR-L29
Build Number: VTR-L29C185B113
With a variety of different models, its a bit confusing trying to find info applicable to a specific model.
Can anyone tell me if there is root available for my P10 and point me in the right direction to get started with it?
Thanks!
Try this worked for me
Root Huawei P10, P10+
https://forum.xda-developers.com/p10/help/root-huawei-p10-p10-t3589946
so 77 said:
Try this worked for me
Root Huawei P10, P10+
https://forum.xda-developers.com/p10/help/root-huawei-p10-p10-t3589946
Click to expand...
Click to collapse
Thanks, I've been reading through the forums and did come across the TWRP thread. It seems that TWRP is still in beta and there are still some issues that need to be addressed.
Since there aren't many ROMS for the P10 at this stage, it's probably not worth the risk trying to flash software which is not ready yet (I would rather not risk bricking my P10). I think I'm going to wait a while (with eager anticipation) to see how things progress with TWRP for the P10 before I jump into it.
Byte_76 said:
Thanks, I've been reading through the forums and did come across the TWRP thread. It seems that TWRP is still in beta and there are still some issues that need to be addressed.
Since there aren't many ROMS for the P10 at this stage, it's probably not worth the risk trying to flash software which is not ready yet (I would rather not risk bricking my P10). I think I'm going to wait a while (with eager anticipation) to see how things progress with TWRP for the P10 before I jump into it.
Click to expand...
Click to collapse
The root modifies the boot.img only and this file is the same for all VTR-L09 or L29 models. TWRP ist just in beta, yes. But for flashing the zip is this state enough. I haven't any issues since release.
The only two things you have to remember:
1. if you unlock your bootloader the phone will do a factory reset. All data on the internal storage will be lost. So do a backup.
2. OTAs aren't possible. If you want to root, update to newest version before you root. B113 is very old and there're newer version. In this process you can rebrand your device if you want so.
If you need any help, you can contact me. I did this a lot to my phone and never had any problems.
I'm looking for a new smartphone, and I'd like to get the P Smart 2019 model, because it seems well suited for my needs.
However, I haven't been able to find clear indication that it is rootable (yet). The instructions I find seem for the older (2018) model, or seem to be fake/incomplete.
One site states that huawei is no longer allowing the bootloader to be unlocked: https://www.xda-developers.com/huawei-p-smart-2019-launches-uk/
So - is there anything I can follow about a possible root for P Smart 2019, or should I look for a different phone?
You can use DC-Unlocker to unlock the bootloader, but i don't know if the device is supported yet by the software.
I think it can't be rooted yet because we don't have any custom recovery for it
alexmanu1 said:
You can use DC-Unlocker to unlock the bootloader, but i don't know if the device is supported yet by the software.
I think it can't be rooted yet because we don't have any custom recovery for it
Click to expand...
Click to collapse
Thanks.... I'll wait for a month or two to see if a recovery comes along.
Would you say the P Smart 2019 will be a popular phone (e.g. that can get enough community behind so that it will be well supported in terms of root/customizations), or are there better fish in the pond?
alexmanu1 said:
You can use DC-Unlocker to unlock the bootloader, but i don't know if the device is supported yet by the software.
I think it can't be rooted yet because we don't have any custom recovery for it
Click to expand...
Click to collapse
That's so bad. i bought today and 1/03 arrive to me and there isn't root method
mad_ady said:
Thanks.... I'll wait for a month or two to see if a recovery comes along.
Would you say the P Smart 2019 will be a popular phone (e.g. that can get enough community behind so that it will be well supported in terms of root/customizations), or are there better fish in the pond?
Click to expand...
Click to collapse
I would say we need to wait a bit as the phone still is at the beggining of the road
If DC-Unlocked provides a unlock method, we might have devs for the device...
you can root any phone with an unlocked bootloader... you patch the boot. img with magisk manager apk and flash it back using fastboot
your problem is that yes, dc-unlocker provides bootloader unlock codes for 4€..
HOWEVEr... you are SOL cos the huawei 2019 most likely will launch with a security patch that will stop dc-unlocker...
for the p smart 2018 you can downgrade to the first version of stock rom and then unlock but i think 2019 has launched with too high a security patch..
this dude who already ordered it should contact dc and see or post here the date of his security patch out of the box
lastly DO NOT Update.. just in case you can unlock anyway..
dont buy Huawei.. they are anti dev mod and root so don't support them
get a xiaomi.. same quality and price but more dev friendly
Thank you for your suggestion. I'll have a look at a different vendor as well.
Bluetooth still crappy on this one
Huawei P Smart 2019 root manual at techdroidtips
Not sure to what extent xdadevelopers permits external links, but google allows a quick find of instructions for rooting the 2019 at techdroidtips dot com. It looks very serious and reliable. What do you guys think about?
I would go for the first "manual" method, however the easy "automatic" option with KingRoot sounds convincing, too. Any recommendations or comments are welcome!
Sorry, that site doesn't seem reliable and the pages seem autogenerated:
Before rooting, do install TWRP Recovery on Huawei P Smart (2019) (IMP STEP TWRP File May Or May Not Be available as per the development) Though methods are mentioned below that require no Recovery.
Click to expand...
Click to collapse
I can't find any TWRP recovery for this model, so I assume none exists yet.
Klemse said:
Not sure to what extent xdadevelopers permits external links, but google allows a quick find of instructions for rooting the 2019 at techdroidtips dot com. It looks very serious and reliable. What do you guys think about?
I would go for the first "manual" method, however the easy "automatic" option with KingRoot sounds convincing, too. Any recommendations or comments are welcome!
Click to expand...
Click to collapse
jajaja ...are you joking ...kingroot ......kingroot is outdated and also adware / bloatware ....
you have been explained ...only root to road through unlocking your bootloader ....the question is whether the your security patch is outdated enough to allow you to use dc-unlocker to use their method to readback your code from your device for you
if you have an unlocked bootloader you can flash custom roms without root using fastboot and treble system images ( NO ROOT NEEDED) & If yourealky wanted root you could patch your boot.img with magisk and flash that back with fastboot
IN BOTH CASES NO TWRP EVEN NEEDED .....:silly:
In the meantime a have to admit, that you're right and the mentioned source may represent an useful general overview of available approaches, but is not at all device specific (and indeed automatic generated with replacing phone devices as tokens).
So, sorry for the terrible research so far. Hopefully the following summary is better:
1) Because Huawei stopped their Unlocking Support in Mid of 2018, we need alternative ways to do so. One of them could be DC-unlocker, however it doesn't seem to be supported yet (at least not listed as '(2019)'). So other services as for example mentioned at huaweiadvices dot com could be a solution, although they cost 35$ or more. I'm wondering how those companies (like FunkyHuawei or MinistryOfSolutions) do access/receive the Unlock code?
2) Because there aren't (somehow based on issue 1) compatible ROMs for Huawei-P-Smart-2019, yet, or at least no well known/tested ones, an experienced user like me should wait till there is an announced model supported release. A very interesting source seems to be OpenKirin. So waiting for a release for the Kirin 710 (which is not yet listed) could be promising. Btw, what ways do you know for finding fitting ROMs?
Do those two conditions seem proper to you?
Device specific custom roms seems to be the thing of the past . The future is project treble ....so for all intents and purposes there are many custom roms that could installed on your device ...read how treble works and perhaps you will understand....kirin 710 is irrelevant ...in treble you are flashing a system.img which is generic ( any treble device ) because the "drivers" for yourhardware is not in the system img ...
Magisk is the main and perhaps only cross platform root method ...once again ...your device is irrelevant ...
Your only mission here is to unlock your bootloader so you can flash .img files that are not approved by Huawei ...
So your only time spent that will be worth anything will be obtaining a bootloader unlock code
However Whichway because without it you will go pretty much nowhere ...with it ...you don't even need a twrp nor do you need a custom specifically announced as being for P smart 2019
Huawei is like Apple ..of Android ....without any jailbreak community and at a lower price / quality point
Since taking the step not to support bootloader unlocking ...they are worthless as a phone to a person who wants root and good custom roms ..
just because dc says unsupported doesn't mean it won't work ...i told you to contact by email your security patch level to enquire if it might work ...so until youhave done that this whole chat is worthless ...
if your security patch is quite recent you are SOL
you should off-load it on an old guy who doesn't know what root is and get another phone .
Hi KevMetal, thanks for your effort to clarify and increasing my understanding. Didn't want you to have yourself repeated...sry
Anyway, I tried to follow your advice and have sent now the following device information to [email protected]:
◦ Model: POT-LX1
◦ Build-Number: 9.0.1.129(C432E8R1P12)
◦ EMUI-Version: 9.0.1
◦ Android Security Patch: 1st Nov' 2018
Don't know if this is enough. However couldn't find a number for the Security Patch or anything beyond that release date.
Will share the information here, If I get an answer...
Klemse said:
Hi KevMetal, thanks for your effort to clarify and increasing my understanding. Didn't want you to have yourself repeated...sry
Anyway, I tried to follow your advice and have sent now the following device information to [email protected]:
◦ Model: POT-LX1
◦ Build-Number: 9.0.1.129(C432E8R1P12)
◦ EMUI-Version: 9.0.1
◦ Android Security Patch: 1st Nov' 2018
Don't know if this is enough. However couldn't find a number for the Security Patch or anything beyond that release date.
Will share the information here, If I get an answer...
Click to expand...
Click to collapse
The info is fine, it does according to release date ...i can almost guarantee that it's too recent .....but rather wait for confirmation ....if you are really lucky some really clever Dev or devs or unlock team looking for money will find another exploit to readback the bootloader code but as for now you are SOL ...but unless you see info floating in XDA or 4pda and it's vouched for by experienced members it's probably a scam to get cash or just adware or bloatware ... after android nougat there are / were very few legit root exploits and when legit they get patched in a security update after release locking down newer models ...cheaper or midrange devices just don't get enough attention from the right people ......not to mention that the OSgets locked down tighter and finding exploits is a time consuming past time ...:good:..sorry bro
tools like software based root exploit tools released to public depends on finding weaknesses in the security of the OS whereas bootloader unlock lets you flash images that includes root or boot images patched previously so its very different
Any news? I boutht the 2019 version and joping there will be some root method soon and perhaps some rom.
Any good dark material emui 9 theme in the meantime?
Is there any way I can enalrge icons in the status bar, they are so tiny no matter what font settings are applied?
Huawei P Smart 2019 root/magisk — missing Bootloader unlocking!
Well, unfortunately there is only little hope. I got answers from [email protected] that there is no support so far, however they „[…] hope so it will become supported in future, but there are no news or information available about it yet.“
I won't wait for it and switched to another phone...
Today, I have got bootloader unlock code for P Smart 2019 for 31 USD from
global-unlocking-solutions.miiduu.com/bootloader-unlock-codes-choose-model-below
Unfortunately I cannot get Magisk to work, tried so many things and still no root, also non of working twrp recoveries exist ...
xcodejps said:
Today, I have got bootloader unlock code for P Smart 2019 for 31 USD from
global-unlocking-solutions.miiduu.com/bootloader-unlock-codes-choose-model-below
Unfortunately I cannot get Magisk to work, tried so many things and still no root, also non of working twrp recoveries exist ...
Click to expand...
Click to collapse
if you unlocked your bootloader you can flash any prerooted treble system.img
....how is it exactly that you cant get magisk to work ....download your stock rom ..extract the boot.img ...patch it with magisk apk ...flash it back using fastboot
post screenshots here if your unlocked bootloader then i will explain you how to flash a treble GSI
NO TWRP NECESSARY ANYMORE SINCE PROJECT TREBLE ...WHAT DONT YOU UNDERSTAND ..just go read about treble a little ..:silly:
or is this fake spam to dupe people into forking out 31$ for a bootloader unlock code that doesnt arrive ..post proof of your unlocked bootloader with screenshots from fastboot
KevMetal said:
if you unlocked your bootloader you can flash any prerooted treble system.img
....how is it exactly that you cant get magisk to work ....download your stock rom ..extract the boot.img ...patch it with magisk apk ...flash it back using fastboot
post screenshots here if your unlocked bootloader then i will explain you how to flash a treble GSI
NO TWRP NECESSARY ANYMORE SINCE PROJECT TREBLE ...WHAT DONT YOU UNDERSTAND ..just go read about treble a little ..:silly:
or is this fake spam to dupe people into forking out 31$ for a bootloader unlock code that doesnt arrive ..post proof of your unlocked bootloader with screenshots from fastboot
Click to expand...
Click to collapse
Hi, I've been rooting other older phones before, i will read more about treble gsi, thank you, but i can promise you it is real, i've been tracking for unlock codes for my phone for two months and just yesterday they managed to generate the unlock code for me. I have no intention to lie, here are the screenshots i've been able to gather just now.
imgur.com/a/YuoGGvC
If i flash it to recovery_ramdisk and then quickly disconnect usb and hold vol up it will bootloop once (and never i get magisk installed) i have tried to install twrp for kirin 710 from honor device, but screen is not working can't touch anything then. I have downloaded latest full firmware 9.0.1.152(C432E8R1P12) and trie to patch RECOVERY_RAMDISK.IMG multiple times using magiskmanager with different versions of magisk 18v 19v with options enabled/disabled
Greetings Folks
For starters I just got Mi8 and am planning to go for Havoc or Pixel Experience there is a Pixel Port too I'll have to try which is best close to stock but with gestures features and full fledged Gcam support
Back to Questions
I have seen many threads where newer folks are victim of their devices getting bricked and paying for fix?
Why isnt there a proper guide thread to avoid these obstacles and spread awareness out ?
I know there are certain partitions you need to backup too e.g efs in case of lost IMEI there was a thread Its hell I have been through it with a Samsung Device,There was a guy who messed up his phone sensor files?
But most of all EDL and Devices getting brick so lets address the elephant in the room
Now My Phone is on
MIUI 10.3 Global 10.3.2.0(PEAMIXM)
Android Version : 9 PKQ1.180729.001
Android Security Patch : 2019-04-01
Rom threads say 9.3
take havoc for example
Help Appreciated thanks
@techyrock
Here is a guide : https://forum.xda-developers.com/mi-8/how-to/how-to-install-roms-resolve-issues-t3911611
Part 1 ( The OP is general info ) Below the first couple of comments have detailed steps for AOSP.
Be extremely careful, unfortunately this community doesn't have a lot of highly active professionals.
So definitely double check any advice that you are given, or that you find. With that being said there are definitely several members that are mature, knowledgeable, friendly and overall fantastic.
If you need help, feel free to ask me anytime, I haven't had a lot of time to use XDA recently. But if I am around, I am always willing to help. At the moment I am going to sleep, but go ahead and read my thread, and I have made some lengthy post that may be helpful as well. You can find those posts by reading my post history. Enjoy.
As long as your account is bound to your device, unbricking is pretty easy with these phones. If you want to avoid a brick, avoid brand new builds, test software etc. Some of the recent issues actually stemmed from the 7.11 china developer rom which had a major issue.
if you want to use Miui with zero ads, and every single feature, then Mi-Globe is pretty great, and solid on a week to week basis.
As far as AOSP, I feel that in my experience that Syberia is practically always highly stable, but it's a little plain compared to some other roms. I also liked Pixel 3, Bootleggers ( Newer version) and Havoc. ( I used Havoc in the beginning of July and loved it, that build is fantastic)
I haven't tried a lot of AOSP roms on this phone yet. So that is all I have
Addition to that, the main issue is people are using Miflash to flash a ROM from bootloader. DO NOT USE IT.
Just use the flash_all.bat in the fastboot rom zip, it's easy. Miflash chooses to lock bootloader by default, and if you don't change it, you'll need to use EDL to fix your device. People usually forget about it, and will whine here to be able to unbrick. Don't be one of them
Don't relock the damn bootloader. It's unnecessary, and dangerous on a Chinese machine.
The War Profiteer said:
Addition to that, the main issue is people are using Miflash to flash a ROM from bootloader. DO NOT USE IT.
Just use the flash_all.bat in the fastboot rom zip, it's easy. Miflash chooses to lock bootloader by default, and if you don't change it, you'll need to use EDL to fix your device. People usually forget about it, and will whine here to be able to unbrick. Don't be one of them
Don't relock the damn bootloader. It's unnecessary, and dangerous on a Chinese machine.
Click to expand...
Click to collapse
We ok that to unlock bootloader on mi8 we have to use mi "flash" unlock tool. Right?
Cheers
Erpe7 said:
We ok that to unlock bootloader on mi8 we have to use mi "flash" unlock tool. Right?
Cheers
Click to expand...
Click to collapse
Yes, that is the only way to unlock. he was talking about using Mi Flash to flash roms, which may seem to be user friendly which it is but is also extremely dangerous because the the option to lock the bootloader is checked by default. If using it make sure that its unchecked and you should not have any issues.
Personally, I prefer ADB if flashing via fastboot or TWRP with a OTG flash drive.
Also there is a tool that is excellent that I have also used many times, its called Tool all in One ( TAIO) After your bootloader is unlocked, you can use TAIO for many functions, including keep your PC's ADB platform tools, up to date, and providing system wide access. You can use it to remove encryption, flash recovery, root, roms or to restore to stock. It definitely worth installing if if you only use it to keep your drivers, and platform tools up to date.
First of all thanks guys for replies wasn't expecting this response
My device is Global Mi8 bootloader is locked for now I still have some hours left I'll be able to unlock it by 26th
miflash_unlock prompted to bind my account from developer option for unlocking,I did so it will be bound to my account and ill be unlocking it for first time I believe i bought it used but previous owner seemed to have know info about ROMs though
I have been using Pixel 2XL twice followed by Nokia 8 so I am much more inclined towards AOSP stock experience the two feature I would love to have from MIUI are the
1)MIUI gestures
2)MIUI Dual Apps (I am aware of Play store alternatives but clash of clans doesnt work as good on them as on dual apps )
I know gestures are on Havoc
guess you guys have been playing around with your mi8 kindly guide me to right directrion what ROMs you guys prefer and why ?
how would you prefer to flash a ROM do I need to back up any partitions ? if so which app should use for it ,Ill surely back up everything via TWRP for sure
also the encryption thingy should I sign out my google account before bootloader unlock and other stuff?
and since I am on
MIUI 10.3 Global 10.3.2.0(PEAMIXM)
Android Version : 9 PKQ1.180729.001
Android Security Patch : 2019-04-01
is it safe to flash havoc ?
tsongming said:
Yes, that is the only way to unlock. he was talking about using Mi Flash to flash roms, which may seem to be user friendly which it is but is also extremely dangerous because the the option to lock the bootloader is checked by default. If using it make sure that its unchecked and you should not have any issues.
Personally, I prefer ADB if flashing via fastboot or TWRP with a OTG flash drive.
Also there is a tool that is excellent that I have also used many times, its called Tool all in One ( TAIO) After your bootloader is unlocked, you can use TAIO for many functions, including keep your PC's ADB platform tools, up to date, and providing system wide access. You can use it to remove encryption, flash recovery, root, roms or to restore to stock. It definitely worth installing if if you only use it to keep your drivers, and platform tools up to date.
Click to expand...
Click to collapse
Thank you for this precious advices ;(
I'll note that!
Sent from my Redmi Note 5 Pro using XDA Labs
Thank you folks.
Could someone explain what EDL is meaning?
Gesendet von meinem BTV-DL09 mit Tapatalk
ktrokar said:
Thank you folks.
Could someone explain what EDL is meaning?
Gesendet von meinem BTV-DL09 mit Tapatalk
Click to expand...
Click to collapse
There's a primary bootloader that we consumer know of and there's Qualcomm's Emergency Download Mode bootloader (EDL) , since Mi8 has ARB(Anti Rollback) downgrading the phone gets it bricked to EDL mode requiring EDL authentication to my understanding thats why edl is a thing(since its just emergency bootloader for oems to work with) I have not experienced it personally so I don't know whether it bricks that way or not but ARB and EDL authentication are a thing with Mi8 from what I have read in different threads
Sent from my MI 8 using Tapatalk
ktrokar said:
Thank you folks.
Could someone explain what EDL is meaning?
Gesendet von meinem BTV-DL09 mit Tapatalk
Click to expand...
Click to collapse
EDL is Qualcomm recovery mode, it's the mode that you must be in to restore a hard bricked phone.
As long as you are careful you should never need to worry about EDL. Basically, you place the phone into a mode that the computer is able to recognise port 9008, once that is down you can use 1 of 4 techniques to restore your phone. Unbricking Xiaomi's is actually very easy to do, as long as the device is bound to your account.
The big issue is that unscrupulous Chinese vendors, used their own account to unlock bootloaders of Mi8's and other Xiaomi devices, then installed the Global Miui ROM and then sold the phone as new to unsuspecting western customers and at a lower price than western outlets such as Amazon. These vendors marketed the phones as Ïnternational versions" when they were actually Chinese devices and not the Global version that the customer thought they bought.
When these customer's used programs such as MiFlash to upgrade their phone's their bootloaders were locked and the are unable to log into their Mi Account to restore the phone. Remember the vendors unlocked the phone, so these Mi8's were bound to the vendor and not the final customer. This is the Primary reason why Xiaomi makes us wait to unlock the bootloader. Finally, ARB is potential issue, but it hasn't been implemented yet on Global devices.
So do your research before flashing anything and you should be safe.
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.
Has anyone found a working guide for unlocking the bootloader? Non of the linux or windows tools have worked and I've been trying for quite a while now. Does anyone have a guide for doing it manually via the cli?
No.
Does not exist no one cli for unlocking bootloader of xiaomi devices.
You need to use the software for unlocking and then wait for the time given by xiaomi server.
Here, you can find the excellent guide by @Akitake about how unlock bootloader on xiaomi devices:
[GUIDES & FAQ][Merlin] Bootloader, Magisk, EdXposed, SafetyNet, GSI/Treble ROMs
DISCLAIMERS (please read !) This thread is made for the Redmi Note 9, also known as Redmi 10X 4G. This device's codename is Merlin. I will not be held responsible if you brick your device. Follow the instructions shown in this thread at your own...
forum.xda-developers.com
VD171 said:
Here, you can find the excellent guide by @Akitake about how unlock bootloader on xiaomi devices:
[GUIDES & FAQ][Merlin] Bootloader, Magisk, EdXposed, SafetyNet, GSI/Treble ROMs
DISCLAIMERS (please read !) This thread is made for the Redmi Note 9, also known as Redmi 10X 4G. This device's codename is Merlin. I will not be held responsible if you brick your device. Follow the instructions shown in this thread at your own...
forum.xda-developers.com
Click to expand...
Click to collapse
I don't all of that. The PC sweet cant see the devices, fastboot works fine through cli
It happens when you have multiple android usb drivers installed.
Right, going to setup a fresh install in that case. Shame I didn't try it on my new work laptop before installing Linux. What do we reckon, XP, 7 or 10?
lukemovement1 said:
Right, going to setup a fresh install in that case. Shame I didn't try it on my new work laptop before installing Linux. What do we reckon, XP, 7 or 10?
Click to expand...
Click to collapse
You can unlock bootloader easily on linux or windows.
Just use xiaomitoolv2: https://xiaomitool.com/V2/
VD171 said:
You can unlock bootloader easily on linux or windows.
Just use xiaomitoolv2: https://xiaomitool.com/V2/
Click to expand...
Click to collapse
It returns 'missingToken cookie'. I looked at the ADB logs and couldn't find anything that looked problematic.
Been working as a developer for 14 years now so I wouldn't be asking if any of these tools worked as the guides stated.
So have you not managed to unlock the bootloader
You just need to keep trying and then you will see the problem.
You have to do exactly same steps of all world to unlock bootloader of xiaomi devices.
The steps are EXACTLY same to everyone.
"disable driver signature enforcement" was what I was looking for.