Related
Hi someone with an account on 4dpa with 30 posts could please download this rom and share it here? I don't know Russian so it's impossible for me to write 30 posts.
I have a Zenfone Go (Z00VD) and the stock ROM it's terrible (crash in the camera, 1 Gigabyte of app space already full....)
In case you can't, could you provide an alternative ROM with as less bugs as possible?
Thank you
Original Thread 4pda
Translated Google
Guess we're on the same boat buddy. Have you tried the other ROMs on their forum like the nougat ones? They seem nice.
I personally prefer to use the RR 5.5.9 lollipop rom provided by 4pda since for some reason the nougat and marshmallow roms on their site just give me bootloops. It may be different for you though.
JustAnormalGuy said:
Guess we're on the same boat buddy. Have you tried the other ROMs on their forum like the nougat ones? They seem nice.
I personally prefer to use the RR 5.5.9 lollipop rom provided by 4pda since for some reason the nougat and marshmallow roms on their site just give me bootloops. It may be different for you though.
Click to expand...
Click to collapse
Hi, not yet, it's not my phone so I'm searching a stable ROM. I saw the nougat thread here but it's not very clear what works and what not, there seems to be a nougat rom on 4dpa which should work well except the videocamera with the stock app, but the Oreo one seems almost bug free although more complex to install. Unfortunately I can't access it.
Hello,
From what I can tell, both Oreo and Nougat ROMs were unstable and/or sluggish for me, so I'd recommend to stick to Marshmallow based ROMs(for now). My personal preference is ResRemix 5.7.4, but if you decide to try any of them, keep in mind that ROMs with kernel 3.18.19(as far as I've seen most of ROMs in that thread) all have these two issues that I was able to find so far:
Notification LED doesn't work
Bluetooth audio doesn't work either
Other than that, the ROM is super-stable and somehow better than 5.1.1 ROMs from official dev thread there.
And for JustAnormalGuy, bootloops in later ROMs seem to happen because of unwiped internal storage(basicly needs entire /data partition wiped somewhy). Try marking the 'Internal SD' option when wiping partitions for ROM installing.
Good luck!
aurismat said:
Hello,
From what I can tell, both Oreo and Nougat ROMs were unstable and/or sluggish for me, so I'd recommend to stick to Marshmallow based ROMs(for now). My personal preference is ResRemix 5.7.4, but if you decide to try any of them, keep in mind that ROMs with kernel 3.18.19(as far as I've seen most of ROMs in that thread) all have these two issues that I was able to find so far:
Notification LED doesn't work
Bluetooth audio doesn't work either
Other than that, the ROM is super-stable and somehow better than 5.1.1 ROMs from official dev thread there.
And for JustAnormalGuy, bootloops in later ROMs seem to happen because of unwiped internal storage(basicly needs entire /data partition wiped somewhy). Try marking the 'Internal SD' option when wiping partitions for ROM installing.
Good luck!
Click to expand...
Click to collapse
Those 2 bugs are not a deal breaker for me, would you mind linking to the ResRemix 5.7.4 rom that you used?
Sure, buut since I can't post links(thanks XDA for 10 post restriction, love ya!), I'll have to send one another way.
PM me your Discord handle(if you have one) or something else. I should be able to send you the link there.
aurismat, and what version of twrp do you use ?
I use TWRP 3.0 by Jemmini. It's been a *long* time since I installed it though, so if you have something different, I'm afraid I won't be of much help unless I'll be able to pull my recovery .img file.
Actually, i use the same version. Problem is most probably my method of root. The common method of rooting for our device didn't include any flashing with sp flash tool. But for my situation, my bootloader is locked even after downgrading. So i did the other method (also found on the forum) in which includes flashing.
Hmm, it *may* be the root method, may be also the locked bootloader.
If I recall right(and this might be THE common way), I used the fastboot method from XDA, and I knew it'd work cause I rooted more phones that way. I remember downgrading the stock ROM down to version 39(i think that one still had the bootloader check in dev options) and then trying to unlock the bootloader and obviously go through flashing the recovery image.
Dunno what might be the issue with your way of flashing, though. AFAIK might be anything from leftover files to bootloader giving the finger.
@aurismat i think the problem might be that i used the "format all + download" option on sp flash tool. Does that affect the phone in any way that deprives my phone from using 6.0 - 7.0 roms? (Besides the "null" imei effect)
@JustAnormalGuy I don't think it should be a problem, because the ROM .zips install their own stuff to the partitions AFAIK, so even if Flashtool wipes everything, it should still be fine. Try doing one of them ROMs(previously said ResRemix worked for me), but remember to wipe the Internal Storage partition if you can.
Oh and remember to take a backup of your current ROM, should it bootloop again at least you won't have to do the hassle of reinstalling everything back(learned that the hard eay haha).
EDIT: was it just Nougat ROMs that you were trying or was it both Nougat and Marshmallow? Not sure what might be the cause, but the ROMs developed under the same kernel from ska-vova in 4PDA worked for me. Just a thought.
well actually i already tried various roms from Marshmallow to Nougat all of which gave me bootloops. I've already followed the steps of installation as written. However, i tried once installing a Marshmallow rom from the facebook group named "ASUS Zenfone Go Indonesia" and it surpisingly worked for me (numerous bugs present however), as well as most of the marshmallow (and only marshamallow roms) on their group.
The thing is I also might think one of the reasons why i get the bootloops in the roms from the 4pda forum is the kernel used in them. (just speculation) Should it be correct to assume that ?
As I recall:
Working rom shows "kernel version > [email protected]"
Not working rom - "kernel version > [email protected]"
Hmm, I'm using [email protected] kernel version 3.18.19.
All the ROMs there seem to be by mosly nik-kst's kernel. ska-vova seems to just build ROMs with the kernel.
Besides, take note from the working ROM - it's also from 4PDA.
Only thing I can speculate is that your device is somewhat different(maybe different hardware, not sure) and hence why it gives you BLs.
Dunno, this case is a tough cookie to be honest - only thing I can recommend at this point is to flash literally EVERYTHING back to stock and try using fastboot method to get recovery and root back.
Hey @Darkorn,
Over the span of a few days, I've tried installing 4PDA's Oreo ROM.
It took me a good couple of headaches to make out what translated Russian meant in the instructions, but I've managed to repartition the entire device to the guide.
Seems to work properly so far, hell even Bluetooth and Notification LED issues from older ROMs seem to be fixed!
Though one thing that annoys me *personally* is that it's impossible to install SuperSU, so you're stuck with Magisk. It's not the end of the world, though, as long as you don't care about SafetyNet's BS.
Oh and @JustAnormalGuy, try repartitioning your device according to the Oreo instructions in 4PDA, that might be the solution for ya.
If I ever get up to 10 posts I'll ask those guys permission to let me post the tutorial here with all the links(hopefully).
Until then, good luck to both of ya!
aurismat said:
Hey @Darkorn,
Over the span of a few days, I've tried installing 4PDA's Oreo ROM.
It took me a good couple of headaches to make out what translated Russian meant in the instructions, but I've managed to repartition the entire device to the guide.
Seems to work properly so far, hell even Bluetooth and Notification LED issues from older ROMs seem to be fixed!
Though one thing that annoys me *personally* is that it's impossible to install SuperSU, so you're stuck with Magisk. It's not the end of the world, though, as long as you don't care about SafetyNet's BS.
Oh and @JustAnormalGuy, try repartitioning your device according to the Oreo instructions in 4PDA, that might be the solution for ya.
If I ever get up to 10 posts I'll ask those guys permission to let me post the tutorial here with all the links(hopefully).
Until then, good luck to both of ya!
Click to expand...
Click to collapse
Nice! Resurrection Remix is working too well to bother, but who knows in a few months!
That would be great man, thanks !!
So about 3 weeks ago my 2 year old 3T just stopped working out of nowhere. I debated on whether to upgrade for over a week, but eventually decided to replace it with the same, just to have the familiar ROM, & not to have to learn anything new or mess with anything else, since I'm going through a lot of personal stuff right now. Anyway, I got the phone over a week ago and I've tried everything since then to get it running something beside OOS to no avail. Every single time it goes to sleep in another ROM, once I wake it up, touch is no longer responsive. I can't for the life of me figure out why. I have tried so many different things, in so many different ways. I know it might sound ridiculous but at this point I'm just in tears... I really need a functional phone, and I never would have bought another OP3T if I knew I'd be stuck with OOS....
The process I went through as soon as I got it:
Unfortunately I don't remember the version of OOS that it came with
- Unlock bootloader
- Flash TWRP (twrp-3.0.4-1 due to a thread I came across and was confused by)
- Wipe everything
- Flash recommended firmware for my ROM (posted in the ROM's thread)
- Flash my favorite ROM (Unofficial RR)
- Flash Magisk
- Boot, everything seems fine, screen goes off, turn it back on, unable to use touchscreen anymore.
I then used the unbrick tool, and tried again. Same problem. Used unbrick tool, unlocked bootloader, this time tried to flash this unofficial Lineage . Booted. It went to sleep. Woke up. Touchscreen nonfunctional.
I shut it down. Unbrick tool. This time I let it update itself all the way up to the very latest version of OOS. I go through the entire process again, this time flashing TWRP 3.2.1.0, it's the same thing. I've tried going up to open beta and then flashing my roms. I've tried flashing the rom without firmware, without magisk. With gapps. Without gapps. I always format and wipe everything. I also tried this on the off chance it might work.... I have seriously done the process every way imaginable, over twenty times since I got the phone last week.... nothing ever works. I also just tried Cyanogenmod, but it wouldn't flash at all.
I don't know what to do anymore. I just want to have a phone that I don't hate. At this point, I am too tired and I've got too much going on to figure this out on my own anymore. I would be grateful to pay someone at this point just to help me get this working honestly.... so if there's anyone out there who knows how to fix this, please let me know
Did you buy a new unit from somewhere or did you get a second hand unit ? In the latter case, the person who owned the device before you might have replaced the display for whatever reason, replaced displays often run into these kind of issues.
Also, does this happen on all the ROMs ? It seems you're only flashing Nougat roms, It could be that the hardware is not falling in line with the older software (just a guess). Try flashing a newer, latest updated pie rom and see how that works out.
Mizart said:
It seems you're only flashing Nougat roms, It could be that the hardware is not falling in line with the older software (just a guess).
Click to expand...
Click to collapse
What does that even mean? Sounds like you are just making stuff up.
---------- Post added at 12:23 PM ---------- Previous post was at 12:19 PM ----------
SpaceOctopus said:
I shut it down. Unbrick tool. This time I let it update itself all the way up to the very latest version of OOS.
Click to expand...
Click to collapse
At any point, did you flash a full OOS zip (over 1 GB) and not just update patches? That is where I would start, to make sure it's one a completely stock baseline (including firmware, etc.).
You can get the latest full update zip from here: https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
@SpaceOctopus
I would try a newer firmware like the
Stable5.0.8 Firmware+Modem_OnePlus3T.zip
I would also recommend the latest TWRP = twrp-3.3.0-1-oneplus3.img
if still not working definitely flash the flash a full OOS zip from the post above which is 5.0.8
else you should try making the jump to a 9.0 PIE ROM, I see an official and unofficial RR if that is your goto ROM, easy to locate in the [INDEX] ROMs, Kernels & Misc. for 3/3T thread
.
Mizart said:
Did you buy a new unit from somewhere or did you get a second hand unit ? In the latter case, the person who owned the device before you might have replaced the display for whatever reason, replaced displays often run into these kind of issues.
Also, does this happen on all the ROMs ? It seems you're only flashing Nougat roms, It could be that the hardware is not falling in line with the older software (just a guess). Try flashing a newer, latest updated pie rom and see how that works out.
Click to expand...
Click to collapse
Brand new from ebay. Sealed in the box.
I did try flashing a more recent version of resurrection remix, but it failed. Any recommendations?
redpoint73 said:
What does that even mean? Sounds like you are just making stuff up.
---------- Post added at 12:23 PM ---------- Previous post was at 12:19 PM ----------
At any point, did you flash a full OOS zip (over 1 GB) and not just update patches? That is where I would start, to make sure it's one a completely stock baseline (including firmware, etc.).
You can get the latest full update zip from here: https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
Click to expand...
Click to collapse
I mean, does using the unbrick tool count? I think it completely flashes everything back to stock. Granted it's a very old version of OOS, but either way I will try that next just in case. Thank you.
hhp_211 said:
@SpaceOctopus
I would try a newer firmware like the
Stable5.0.8 Firmware+Modem_OnePlus3T.zip
I would also recommend the latest TWRP = twrp-3.3.0-1-oneplus3.img
if still not working definitely flash the flash a full OOS zip from the post above which is 5.0.8
else you should try making the jump to a 9.0 PIE ROM, I see an official and unofficial RR if that is your goto ROM, easy to locate in the [INDEX] ROMs, Kernels & Misc. for 3/3T thread
.
Click to expand...
Click to collapse
I did try that TWRP eventually. No change. I would probably have switched to pie a while ago, except one small thing. There's an xposed module I'm really attached to, and as far as I'm aware, xposed isn't available on pie? Or at least that's what I've heard/read. It's the xprivacy lua module that lets you control every type of data an app has access to. I think I've tried looking for an alternative and there aren't any, either. :'( You know, sometimes it's just that one small thing... lol
However, I did try to install the most recent version of RR yesterday, and it failed flashing. Don't know why. I'm going to try again after flashing the firmware. Maybe it'll work this time.
Anyway, I'm also going to try what you all have recommended and see what happens. Hopefully something happens. Thank you much for your help
Ok, well, this time it let me install Resurrection Remix latest version. It may not be exactly what I wanted, but it's pretty goddamn close, and it sure as hell isn't OOS! lol
Thanks for your help everyone! I really appreciate it. I do still really wish I knew wtf was happening honestly with it not properly running nougat ROM's, but hey, this works for me. It won't make me want to toss it in a dumpster and set it on fire every time I pick it up. :laugh: :laugh: :laugh:
Maybe I can get someone to figure it out in the future or something, I don't know. I sure wish someone would convert that xprivacy module to work with Magisk though! I'm surprised nobody has even made an alternative or an app or anything like it really.
SpaceOctopus said:
I mean, does using the unbrick tool count? I think it completely flashes everything back to stock. Granted it's a very old version of OOS, but either way I will try that next just in case.
Click to expand...
Click to collapse
I think the unbrick tool does flash the full OOS. But honestly not 100% sure, as I have never actually had to use the unbrick tool (knock on wood!). Which is one reason I decided to pose that as a question.
In any case, if the unbrick did flash an old OOS, best to replace with newer version (or at least the firmware). Updated firmware typically plays better with the current custom ROMs. And old firmware is often a culprit when random bugs occur after flashing a custom ROM. So again, flashing firmware and/or the full update zip (which also flashes the firmware) is best practice in such cases. And if you are in any doubt about the OOS version or corresponding firmware that was installed, it probably doesn't hurt to flash again.
So, to modify the modem of dipper in order to get VoWi-Fi on my phone, I probably need to have the aceess to 9008 DIAG port. When I enable the diag port from ADB shell, it only enables 901D which won't work with QFIL or QPST. Are there anybody succeded with this?
EDL enables 9008, but QPST or QFIL still won't let me to backup or modify since it's on the download mode.
@tsongming I believe you are experienced with this procedure, so I guess I want to tag you.
Edit : Anyone has an idea to fix this? NO PHONE / NO ESL on QPST
The War Profiteer said:
So, to modify the modem of dipper in order to get VoWi-Fi on my phone, I probably need to have the aceess to 9008 DIAG port. When I enable the diag port from ADB shell, it only enables 901D which won't work with QFIL or QPST. Are there anybody succeded with this?
EDL enables 9008, but QPST or QFIL still won't let me to backup or modify since it's on the download mode.
@tsongming I believe you are experienced with this procedure, so I guess I want to tag you.
Click to expand...
Click to collapse
I have seen this issue a few years ago and off the top of my head I don't remember. But there is a solution, and I am pretty sure that I made notes about it, give me a few minutes and I will look for it, and will be back soon.
---------- Post added at 12:31 AM ---------- Previous post was at 12:12 AM ----------
The War Profiteer said:
So, to modify the modem of dipper in order to get VoWi-Fi on my phone, I probably need to have the aceess to 9008 DIAG port. When I enable the diag port from ADB shell, it only enables 901D which won't work with QFIL or QPST. Are there anybody succeded with this?
EDL enables 9008, but QPST or QFIL still won't let me to backup or modify since it's on the download mode.
@tsongming I believe you are experienced with this procedure, so I guess I want to tag you.
Click to expand...
Click to collapse
Okay, at first I thought that you are bricked and that you could not get into EDL. But after re-reading your post. I see that you are not, You are wanting to open bands using QPST. While, I have read that this possible, as far as I know you need a proprietary a proprietary tool that is very expensive.
This link describes the steps and has a broken link to an old version of the tool and a link to a current version which is very pricy
https://forum.xda-developers.com/le-pro3/help/unlocking-bands-t3565979
I have more info on this, and when I find it, I will come back and add more. I remember an article on a Miui website that had instructions step by step, so I am looking for that too. I have never personally never attempted opening bands. However, I have read stories of success and failure when attempting to do it, so it may be risky. Nonetheless, I think you are well aware of that, and I am interested to see if it can be done.
Edit: If you are hard bricked and can not enter EDL, you will need to buy the EDL cable from Amazon they are cheap, like $5 or if the phone is seen from ADB you can get to EDL ( 9008) with this command : adb reboot edl
tsongming said:
I have seen this issue a few years ago and off the top of my head I don't remember. But there is a solution, and I am pretty sure that I made notes about it, give me a few minutes and I will look for it, and will be back soon.
---------- Post added at 12:31 AM ---------- Previous post was at 12:12 AM ----------
Okay, at first I thought that you are bricked and that you could not get into EDL. But after re-reading your post. I see that you are not, You are wanting to open bands using QPST. While, I have read that this possible, as far as I know you need a proprietary a proprietary tool that is very expensive.
This link describes the steps and has a broken link to an old version of the tool and a link to a current version which is very pricy
https://forum.xda-developers.com/le-pro3/help/unlocking-bands-t3565979
I have more info on this, and when I find it, I will come back and add more. I remember an article on a Miui website that had instructions step by step, so I am looking for that too. I have never personally never attempted opening bands. However, I have read stories of success and failure when attempting to do it, so it may be risky. Nonetheless, I think you are well aware of that, and I am interested to see if it can be done.
Click to expand...
Click to collapse
Thanks for your help. I'm not trying to unlock bands, I need to merge a few files into the phone using the QPST in order to get it working, so I need to get into 9008 without having to use download mode. ?
The War Profiteer said:
Thanks for your help. I'm not trying to unlock bands, I need to merge a few files into the phone using the QPST in order to get it working, so I need to get into 9008 without having to use download mode. ?
Click to expand...
Click to collapse
I edited the last post; EDL is port 9008 : you can get there with : adb reboot edl or worst case scenario : https://www.amazon.com/Flash-Cable-...coding=UTF8&psc=1&refRID=7ZR98PJHRW9BJE5SQXV3 Cheaper ones exist on Amazon
@The War Profiteer
You can also enter EDL with this TWRP : https://drive.google.com/open?id=1eOnz-NzHkLc_UNCeD_ecE6C3sCXhwU-U
Just choose the reboot to EDL option
tsongming said:
I edited the last post; EDL is port 9008 : you can get there with : adb reboot edl or worst case scenario : https://www.amazon.com/Flash-Cable-...coding=UTF8&psc=1&refRID=7ZR98PJHRW9BJE5SQXV3 Cheaper ones exist on Amazon
You can also enter EDL with this TWRP : https://drive.google.com/open?id=1eOnz-NzHkLc_UNCeD_ecE6C3sCXhwU-U
Click to expand...
Click to collapse
I see. Some people were able to backup or modify the firmware on 901D mode apparently, but I'm unable to do that. It says No Phone/No ESN on QPST program, and QFIL will say that no phone found on that port. Do you have any idea how can I achieve this? I've been trying many drivers to be able to do it, all of them has failed.
The War Profiteer said:
I see. Some people were able to backup or modify the firmware on 901D mode apparently, but I'm unable to do that. It says No Phone/No ESN on QPST program, and QFIL will say that no phone found on that port. Do you have any idea how can I achieve this? I've been trying many drivers to be able to do it, all of them has failed.
Click to expand...
Click to collapse
You can use software tools such as this : https://forum.hovatek.com/thread-22384.html
This guy claims to have had some luck : https://forum.xda-developers.com/showpost.php?p=76921725&postcount=23 with his Note 5 Pro. I am not sure if it will work on newer phones with, newer SDK's especially with the massive amount of security changes in the past 6 months.
tsongming said:
You can use software tools such as this : https://forum.hovatek.com/thread-22384.html
This guy claims to have had some luck : https://forum.xda-developers.com/showpost.php?p=76921725&postcount=23 with his Note 5 Pro. I am not sure if it will work on newer phones with, newer SDK's especially with the massive amount of security changes in the past 6 months.
Click to expand...
Click to collapse
Thanks a lot. I'm starting to think that I'm having this issue because of I'm on a custom rom. Does MIUI EU roms require wiping the data when migrating from other Custom roms? If so, I'll probably stop messing with it since I have 90 gb of data on my phone ?
The War Profiteer said:
Thanks a lot. I'm starting to think that I'm having this issue because of I'm on a custom rom. Does MIUI EU roms require wiping the data when migrating from other Custom roms? If so, I'll probably stop messing with it since I have 90 gb of data on my phone
Click to expand...
Click to collapse
The last time that I installed EU beta rom, I definitely had to format storage and of course the same for the Stable build.
However, there is usually no issues when switching from one custom Miui to another, sometimes all I do is wipe cache, install the new Rom, ( FYI : temporary remove root prior to switching to avoid bootloops) and usually there are no issues at all. After installing the new Rom, I check for Google updates, clean out any remaining files with SD Maid, then Root the phone. To be clear, in this example, I am talking about using Miui Pro to Mi-Globe or to Ros Miui etc.
Again, I usually will always have to wipe storage when using the beta EU builds, which is why I usually stick with Mi-Globe when using Miui. On the other hand, for a long while I was using a version of TWRP that could not decrypt data. So it possible that I would have the issue with the TWRP that I linked above.
Currently my data is unencrypted and although I really like the recent Havoc Rom that I have been using for several days, I am wanting to checkout the very latest Stable Miui build ( and manually debloat it)
I will see if I can keep my data without wiping and come back her and let you know if I have an issue. ( I keep all of my most commonly used files on a Flash drive, so it doesn't take very long to restore its no where near the amount of data that you have. Plus, one thing that is great about Mi Cloud is how it restores practically everything.
@The War Profiteer
Okay, I just installed the latest stable, its updating now and I was able to confirm that all of my data is still here. ( Nice!) Which also confirms that the last time when I had an issue and had to format user data it was mostly likely because of the version of TWRP that I was using at the time.
So it seems if you want to install Miui Stable or Miui EU, your data should remain in tact as long as you are using a TWRP that can decrypt data or you do not have your data encrypted.
tsongming said:
The last time that I installed EU beta rom, I definitely had to format storage and of course the same for the Stable build.
However, there is usually no issues when switching from one custom Miui to another, sometimes all I do is wipe cache, install the new Rom, ( FYI : temporary remove root prior to switching to avoid bootloops) and usually there are no issues at all. After installing the new Rom, I check for Google updates, clean out any remaining files with SD Maid, then Root the phone. To be clear, in this example, I am talking about using Miui Pro to Mi-Globe or to Ros Miui etc.
Again, I usually will always have to wipe storage when using the beta EU builds, which is why I usually stick with Mi-Globe when using Miui. On the other hand, for a long while I was using a version of TWRP that could not decrypt data. So it possible that I would have the issue with the TWRP that I linked above.
Currently my data is unencrypted and although I really like the recent Havoc Rom that I have been using for several days, I am wanting to checkout the very latest Stable Miui build ( and manually debloat it)
I will see if I can keep my data without wiping and come back her and let you know if I have an issue. ( I keep all of my most commonly used files on a Flash drive, so it doesn't take very long to restore its no where near the amount of data that you have. Plus, one thing that is great about Mi Cloud is how it restores practically everything.
@The War Profiteer
Okay, I just installed the latest stable, its updating now and I was able to confirm that all of my data is still here. ( Nice!) Which also confirms that the last time when I had an issue and had to format user data it was mostly likely because of the version of TWRP that I was using at the time.
So it seems if you want to install Miui Stable or Miui EU, your data should remain in tact as long as you are using a TWRP that can decrypt data or you do not have your data encrypted.
Click to expand...
Click to collapse
I'm using Pixel Experience. I'm sure switching between MIUI based roms are not an issue, but I'm afraid of AOSP to MIUI. ?
The War Profiteer said:
I'm using Pixel Experience. I'm sure switching between MIUI based roms are not an issue, but I'm afraid of AOSP to MIUI. ?
Click to expand...
Click to collapse
I was on Havoc, and went to Miui stable, I wrote that in my post above.
All of my data is still here. Photos, Music, Texts etc.
@The War Profiteer
The confusion maybe came from my original statement then I came back and edited the post.
So there my original was due to TWRP.
Apparently no issue going from AOSP to MIUI... Using the version of TWRP that works with encryption.
tsongming said:
I was on Havoc, and went to Miui stable, I wrote that in my post above.
All of my data is still here. Photos, Music, Texts etc.
@The War Profiteer
The confusion maybe came from my original statement then I came back and edited the post.
So there my original was due to TWRP.
Apparently no issue going from AOSP to MIUI... Using the version of TWRP that works with encryption.
Click to expand...
Click to collapse
That's awesome. Since I am creating backups of all of my apps, it feels safe to migrate temporarily. Still I will have NANDroid backups before I do. Thanks for the info.
The War Profiteer said:
That's awesome. Since I am creating backups of all of my apps, it feels safe to migrate temporarily. Still I will have NANDroid backups before I do. Thanks for the info.
Click to expand...
Click to collapse
Anytime brother, you have definitely helped me before as well
A heads up: It works on stock miui while not working on pixel experience. Please write on this thread if anyone gets it working on any other custom roms.
Edit: Apparently custom roms don't have the required tools to use the software, only stock roms will let you to modify your efs.
tsongming said:
Anytime brother, you have definitely helped me before as well
Click to expand...
Click to collapse
Hi, if you still are on MIUI, can I have a screenshot of your /sys/devices/virtual/android_usb/android0 ? I think the required USB drivers for the communication between QPST and Phone should be in this folder, which are non-existent on a custom rom. I am expecting a folder named "f_diag".
The War Profiteer said:
Hi, if you still are on MIUI, can I have a screenshot of your /sys/devices/virtual/android_usb/android0 ? I think the required USB drivers for the communication between QPST and Phone should be in this folder, which are non-existent on a custom rom. I am expecting a folder named "f_diag".
Click to expand...
Click to collapse
Sure, I am using Miui Pro at the moment. Here is the screen shot.
Unfortunately, no f_diag here. But I will look for it.
@The War Profiteer
This page has some information that may be helpful, there is also a video.
http://www.99mediasector.com/how-to-enable-qualcomm-diagnostic-mode-diag-port/
It's possible that the f_diag is hidden until its enabled.
According to the linked page : The DIAG PORT Code For Xiaomi Qualcomm : #*#717717#*#* or alternately *#*#13491#*#*
I hope this helps.
tsongming said:
Sure, I am using Miui Pro at the moment. Here is the screen shot.
Unfortunately, no f_diag here. But I will look for it.
@The War Profiteer
This page has some information that may be helpful, there is also a video.
http://www.99mediasector.com/how-to-enable-qualcomm-diagnostic-mode-diag-port/
It's possible that the f_diag is hidden until its enabled.
According to the linked page : The DIAG PORT Code For Xiaomi Qualcomm : #*#717717#*#* or alternately *#*#13491#*#*
I hope this helps.
Click to expand...
Click to collapse
Thank you for the information.
The issue here is while diag port can be enabled on any custom rom using the setprop command, and will be detected by host, I believe the interface that allows the communication of the host and device does not exist on custom roms. I thought that the f_diag folder's content would be the interface and that's why I asked for a screenshot.
I am guessing that custom roms won't support modified modem/efs to get custom files for WFC and ViLTE. So to fix this, I've tried to replace priv-app content of the Pixel Experience with the ones from MIUI, and didn't succeed.
For now, I'm trying to find out which files in OS are responsible for WFC (ViLTE is not that important) and the interface of MIUI or any other stock roms that allows you to communicate with diag port.
UPDATE: It appears that diag port has something to do with the kernel, I'm still looking into it. It's possible that the communication between the host and the device may need an interface that is supported by kernel, still unsure about it. Needs more investigation. Unfortunately most of the people asking for "How to open it", but nobody asks "How does it work and communicate"", which makes it difficult to find the information I need.
The War Profiteer said:
Thank you for the information.
The issue here is while diag port can be enabled on any custom rom using the setprop command, and will be detected by host, I believe the interface that allows the communication of the host and device does not exist on custom roms. I thought that the f_diag folder's content would be the interface and that's why I asked for a screenshot.
I am guessing that custom roms won't support modified modem/efs to get custom files for WFC and ViLTE. So to fix this, I've tried to replace priv-app content of the Pixel Experience with the ones from MIUI, and didn't succeed.
For now, I'm trying to find out which files in OS are responsible for WFC (ViLTE is not that important) and the interface of MIUI or any other stock roms that allows you to communicate with diag port.
UPDATE: It appears that diag port has something to do with the kernel, I'm still looking into it. It's possible that the communication between the host and the device may need an interface that is supported by kernel, still unsure about it. Needs more investigation. Unfortunately most of the people asking for "How to open it", but nobody asks "How does it work and communicate"", which makes it difficult to find the information I need.
Click to expand...
Click to collapse
I have a couple of friends who have developed Miui Roms for years, and they definitely know Miui inside and out. I haven't spoken to them for a while, but I will message both of them and ask if they can come here and help.
tsongming said:
I have a couple of friends who have developed Miui Roms for years, and they definitely know Miui inside and out. I haven't spoken to them for a while, but I will message both of them and ask if they can come here and help.
Click to expand...
Click to collapse
Thanks a lot!
So I'll summarize the issue:
- The goal: My priority is to be able to use VoWiFi with the modified EFS, which works flawlessly MIUI but not on other ROMs. I'm suspecting that the ROM files aren't able to read EFS to provide VoWiFi or they don't exist at all, which means VoWiFi isn't supported by the ROM. Wanna fix this.
- Diag port seems to be communicating on MIUI while doesn't on custom roms. The reason to work with this port is to be able to edit EFS while custom rom is installed, since I'm creating an EFS backup on Miui and reflasshing it on the desired ROM.
The War Profiteer said:
Thanks a lot!
So I'll summarize the issue:
- The goal: My priority is to be able to use VoWiFi with the modified EFS, which works flawlessly MIUI but not on other ROMs. I'm suspecting that the ROM files aren't able to read EFS to provide VoWiFi or they don't exist at all, which means VoWiFi isn't supported by the ROM. Wanna fix this.
- Diag port seems to be communicating on MIUI while doesn't on custom roms. The reason to work with this port is to be able to edit EFS while custom rom is installed, since I'm creating an EFS backup on Miui and reflasshing it on the desired ROM.
Click to expand...
Click to collapse
Just to clarify things a bit (my own experience):
-on my phone I have full working VoWIFI (at least on my second SIM) on Vodafone Germany.
-I'm using PE as a ROM
-it worked with both Sphinx and Canting Kernels
-VoLTE and VoWIFI are both Carrier dependant
-in order to get VoWIFI working, I just activated the option in the settings. It just worked ootb.
And I must say sorry, because I am not able to test other ROMs/kernels. I need a stable phone as a daily driver. I'm using my phone for work stuff too, because I don't want to have to carry two phones around.
phonexpert_alex said:
Just to clarify things a bit (my own experience):
-on my phone I have full working VoWIFI (at least on my second SIM) on Vodafone Germany.
-I'm using PE as a ROM
-it worked with both Sphinx and Canting Kernels
-VoLTE and VoWIFI are both Carrier dependant
-in order to get VoWIFI working, I just activated the option in the settings. It just worked ootb.
And I must say sorry, because I am not able to test other ROMs/kernels. I need a stable phone as a daily driver. I'm using my phone for work stuff too, because I don't want to have to carry two phones around.
Click to expand...
Click to collapse
Thank you for additional info, surely will help a lot to my search. I'm using PE CAF too (sadly, CAF will be cancelled).
First of all, I thought PE wasn't compatible with WFC, but your statement has confirmed that it's working, so the problem is on my side.
The problems I'm guessing that could be about ROMs and/or kernels are:
1- They may be unable to recognize/read/process a modified EFS and they may be reading only modem. I've merged the proprietary files for enabling VoWiFi, which were officially extracted from a SDM845 device that is officially supported by carrier, to the EFS using QPST. It was supposed to work on MIUI, and it did when I tested it. I created a backup of EFS and did a clean install of PE CAF, restored EFS from the backup and it didn't work. I also tested the backup with a clean MIUI setup and it did work, so I don't think there is an issue about the backup or restoration process since I used the same TWRP version.
2- Diagnostics port will be enabled with "# setprop sys.usb.config diag,adb" command, but since the kernel or the ROM doesn't have the interface to establish the communication between the host and the device, I was unable to check or edit the EFS partition if everything is OK.
I'm here to look for suggestions at the moment. Modifying modem image may be dangerous since it can be signed by the manufacturers in order to prevent any modification, which can lead to an unrecoverable bricks, and I don't know what to modify and how to do it.
Thanks, again. Pardon me if I did any grammar mistakes which will lead to misunderstandings or will make the post completely unintelligible.
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.
This might be completely unnecessary (mods feel free to remove if it is), but I see a LOT of misinformation regarding GSI ROMs and the G8. So. Here's a guide/FAQ for those wondering if/what is possible:
***I'M NOT RESPONSIBLE IF YOU BRICK YOUR PHONE, LOSE YOUR DATA, OR OTHERWISE DAMAGE YOUR DEVICE. IF YOU CHOOSE TO FOLLOW THIS GUIDE, THE FATE OF YOUR DEVICE IS IN YOUR HANDS, NOT MINE, NOT YOUR MOTHER'S, NOT ANYONE OTHER THAN YOUR OWN***
Prerequisites (yes, these are all NECESSARY. If you don't know how to unlock your bootloader or use fastboot, there are other guides here. Go find one.)
Unlocked bootloader (and the V50 engineering abl files as well as stock, plenty of guides here with download links)
QFIL/QPST
Basic Fastboot, ADB knowledge
BACKUP. I mean ALL YOUR DATA kinda backup. This WILL wipe your phone, do NOT come crying to me if you lose the last picture of your favorite sock. Not my fault.
GSI for Treble device (ab)
GApps (optional, but recommended)
Instructions to Flash via Fastboot
WIPE YOUR PHONE
Yeah, completely factory reset that sucker. Doesn't matter if it's through recovery, settings, or adb, just bite the bullet and restore factory settings. You can technicially flash without doing this first, but you'll still have to wipe it before any flashed ROM will run. Sorry.
Boot to EDL (NOT download, your screen should be black, dev manager should show QD Loader 9008 COMx)
Use QFIL to flash engineering abl file to both a and b slots - yes, all this work just for fastboot.
Reboot to fastboot!
I just unplug my phone, use power + vol- to shut phone off and then reconnect while holding vol-, but you do you.
In case you don't remember, your touch screen WILL NOT WORK during this time, even if you fully boot to system! Completely fine and normal, means you're on the right track!
Fastboot Devices should yield "LG850UM", also good!
Open cmd prompt from platform_tools, copy path to desired GSI while you're in there
Run these commands line-by-line:
fastboot format system
fastboot flash system *Path_To_GSI.img*
This is where I usually repeat the 2 commands and attempt reboot while I still have fastboot, whether or not it changes anything I have no idea, but it's never given me problems so why fix it if it ain't broke?
fastboot flash abl_a abl_STOCK.bin
fastboot flash abl_b abl_STOCK.bin
fastboot reboot
Ta-Da! Your shiny new ROM should be up and running. Use TWRP or any kernel manager (I like SmartPak) to flash TWRP, GApps, blah blah blah.
FAQ/Troubleshooting
Touchscreen still not working? Go back to EDL and load the stock abl bin files through QFIL, then reboot as normal.
You will likely be asked to input a password upon successful reboot, just enter your PIN/password, whatever you used to unlock your phone pre-flash
The cool things like QuadDAC and LG-specific tweaks will probably not work. Weigh your options before flashing.
Magisk comes pre-installed with most GSI's, just follow the prompts and you'll be just fine.
Don't want GApps? Just sideload desired apk's via ADB, or use the browser to search for them.
Can't I just use TWRP and make this whole process a lot simpler? Yep. But some of us don't have working TWRP or prefer using fastboot commands. This is for those people, don't hate.
Which ROMs work?? Not sure, haven't tried them all. Currently running HavocOS found in Treble GSI forum on here.
Help! I broke my phone! No, you probably didn't. It's advisable that you know how to emergency restore via LGUP prior to starting this process though. Please be specific as to what part of this "broke" your phone and why exactly your phone is "broken" if you're going to ask for help- "bricked device" has never helped anyone.
Rebooting is your best friend in this process, especially during the first boot. If anything starts to hang up or act funny, just give the phone a minute to catch its breath and, worst case, turn it off and back on again
As previously stated, this is probably pointless, but given all I see on the G8 forum is "no custom ROM" or "why bother trying to *insert idea here*", I figured it might help some folks out. I'm sure I left a few things out, feel free to correct or provide input as necessary.
Works on LM-G820QM5?, I have bootloader unlocked
Elihu_GmG said:
Works on LM-G820QM5?, I have bootloader unlocked
Click to expand...
Click to collapse
Yep, it's basically the unlocking/root process only you're formatting/flashing the "system" partition instead of "boot_a/b"
Great info, thnx for the write up. But what about the totc.cfg file? My understanding is no G8 is going to boot if there's a mis-match between that file and the hardware indication of what variant the phone is?
Sorry if my understanding is misguided, new to the G8 (and all it's idiosyncrasies).
AsItLies said:
Great info, thnx for the write up. But what about the totc.cfg file? My understanding is no G8 is going to boot if there's a mis-match between that file and the hardware indication of what variant the phone is?
Sorry if my understanding is misguided, new to the G8 (and all it's idiosyncrasies).
Click to expand...
Click to collapse
In this case there is no tot file, no recovery, laf, or the like. GSI's are generic system images that are capable of being flashed to most Treble-Enabled Androids from Oreo on up. You do lose some of the device specific things (hence, generic), but they're a great alternative if you're like us and stuck with next to no custom anything built for your device. There's a whole forum for them on here, I highly suggest checking it out- it's a pretty awesome option to have.
SirOlive said:
In this case there is no tot file, no recovery, laf, or the like. GSI's are generic system images that are capable of being flashed to most Treble-Enabled Androids from Oreo on up. You do lose some of the device specific things (hence, generic), but they're a great alternative if you're like us and stuck with next to no custom anything built for your device. There's a whole forum for them on here, I highly suggest checking it out- it's a pretty awesome option to have.
Click to expand...
Click to collapse
Great, thnx, sorry for being a jerk but, this does work on a G8? Tested and proven? I ask because it's my understanding that without a match between the hardware encoded variant of the device and what's in the totc file, it won't boot.
you say there is no totc? then how does the hardware encoding get verified? See, that's why there are no custom roms. LG did this to keep people from crossflashing and it killed rom development.
Hey, if I'm wrong, feel free to point that out. But as far as I've discovered so far, a GSI doesn't get a free pass to bypass this mess LG has created with this mis-match hw / totc file.
cheers
AsItLies said:
Great, thnx, sorry for being a jerk but, this does work on a G8? Tested and proven? I ask because it's my understanding that without a match between the hardware encoded variant of the device and what's in the totc file, it won't boot.
you say there is no totc? then how does the hardware encoding get verified? See, that's why there are no custom roms. LG did this to keep people from crossflashing and it killed rom development.
Hey, if I'm wrong, feel free to point that out. But as far as I've discovered so far, a GSI doesn't get a free pass to bypass this mess LG has created with this mis-match hw / totc file.
cheers
Click to expand...
Click to collapse
Sorry for being short, but a simple Google search would back up everything I've written. I wouldn't have written this up if it didn't work, or if it was just a theory... I wouldn't have said that my Verizon G8 is running Havoc if it didn't work. I was able to flash with zero problems. With the Treble Project, Google has mandated that Android devices boxed with 11+ (possibly 10?) be capable of not only recognizing, but running GSIs as to assist developers in testing apps and builds in varying versions of Android as quickly, easily, and simply as possible. This means that not only can one download and flash Android releases downloaded directly from Google, but devs can use the source code to create versions of their ROMs that will apply to a wide array of models that would never have seen development otherwise. Because these are "generic" images and are based upon system architecture type alone- not a particular make/model- there are sometimes things overlooked. For instance, in our case, the audio processing and LG's camera software are not present. These are decently made up for by the presence of flashable mods, though, and the phone remains fully functional, Google Play Certified (if desired), and as reliable as the ROM you choose to flash.
Basically, Google>LG. LG wants to use the Android platform, they must abide by Google's rules. They need not go into great detail, nor allow their devices to be changed to something fundamentally non-LG, nor divulge any potentially propitiatory subject matter (once again, "generic"), but they must allow the device to be open to a certain level of customization as designated by Google.
Is it ideal? Not if you're lucky enough to have ROMs tailored for your specific phone. But for those left behind- like the G8- it's a fantastic workaround that does, in fact, work. As I'm sure you're still skeptical, I will add screenshots tomorrow to prove the validity of this seemingly ludicrous claim. In the meantime, please do some research on the topic- or better yet, give it a shot- there's gotta be a guide around here somewhere.
It works
Of [email protected]*$king course it works. I’ve flashed it to my sprint v50 (v450pm). Had the same QuadDac problem though. Couldn’t get a sound out of it. I mean no sound of any kind. Also couldn’t get it to activate on Google Fi. Will be watching to see if someone solves the Sound problem. We could just skip on past A11.
hooutoo said:
Of [email protected]*$king course it works. I’ve flashed it to my sprint v50 (v450pm). Had the same QuadDac problem though. Couldn’t get a sound out of it. I mean no sound of any kind. Also couldn’t get it to activate on Google Fi. Will be watching to see if someone solves the Sound problem. We could just skip on past A11.
Click to expand...
Click to collapse
Where did you get V50 engineering abl files as well as stock?, I just want to make sure to get the correct files
Guide LG G8/G8x/v50 Bootloader Unlock and Magisk Root using Firehose
Disclaimer: I am not responsible for any problems from using this guide. Works for G8, G8s, G8x, and v50 Confirmed working on G8 and v50 Requirements: Android 10 QFIL...
forum.xda-developers.com
There's no such thing, afak, of a v50 Eng abl. Read the header on the thread! If you don't have one of those phone models, don't! All of this seems to be predicated on the g8x eng abl which is the DL on that thread. READ that thread closely. I did, BL unlock and then flash A12 GSI.
hooutoo said:
Guide LG G8/G8x/v50 Bootloader Unlock and Magisk Root using Firehose
Disclaimer: I am not responsible for any problems from using this guide. Works for G8, G8s, G8x, and v50 Confirmed working on G8 and v50 Requirements: Android 10 QFIL...
forum.xda-developers.com
There's no such thing, afak, of a v50 Eng abl. Read the header on the thread! If you don't have one of those phone models, don't! All of this seems to be predicated on the g8x eng abl which is the DL on that thread. READ that thread closely. I did, BL unlock and then flash A12 GSI.
Click to expand...
Click to collapse
Ok,ok
Hello, I followed your instructions as written but when I reboot my phone I am stuck at a boot logo cycle, but my comment doesnt have to do with that, I want to ask if maybe you know what could've gone wrong.
I also own a g8 from verizon, I do have bootloader unlock, and tried to install Havoc OS, I wanted to mention this in case it is useful
Dude, I have no knowledge of G8, per se. My main goal was to get away from Sprint software on my v450pm. These phones are a little touchy. I do know that if you have a proven RESTORE method then you can mess around.. If you're Qfil_ing your phone you MUST have a backup of EVERY damn partition. I trashed my ftm partition and it was bad. Use telegram group for very good info. I have yet to be able to logon to Google Fi, an mnvo of Tmob. I've crossflashed to Eu A11, no go. I'm about to try some other roms, but again a backup will be needed.
Remember, you gotta have a way out or you're gonna pay $14 bucks to a Russian.
hooutoo said:
Dude, I have no knowledge of G8, per se. My main goal was to get away from Sprint software on my v450pm. These phones are a little touchy. I do know that if you have a proven RESTORE method then you can mess around.. If you're Qfil_ing your phone you MUST have a backup of EVERY damn partition. I trashed my ftm partition and it was bad. Use telegram group for very good info. I have yet to be able to logon to Google Fi, an mnvo of Tmob. I've crossflashed to Eu A11, no go. I'm about to try some other roms, but again a backup will be needed.
Remember, you gotta have a way out or you're gonna pay $14 bucks to a Russian.
Click to expand...
Click to collapse
Yeah, I know, like I said in my previous comment my phone got stuck in a boot loop, I fix it just by loading system_a partition in qfil, so I am gonna give it another shot and see if it works, already backed up every partition just in case anything goes wrong
If you're goona play around, this is secondary bs. My real phone is a FLIP3 and I'm not allowed to play unlesss to make/awnswer call.
Does somebody tried tp flash GSI with LineAge (A11) or Arrow(A12) vendor to g8?
I`m interesting about dt2w .. I flashed GSI`s to my G820UM on the past (A10 stock vendor) and it have no dt2w.. ((
i ended zeroing my imei from sprint G8 but thats okay i dont care for it much but what i do care is getting some LOS 17.1 on the sprint G8
where do we have any links to these so called GSI images?
blaze2051 said:
where do we have any links to these so called GSI images?
Click to expand...
Click to collapse
Treble-Enabled Device Development A/AB ROMS
Treble-Enabled Device Development A/AB ROMS
forum.xda-developers.com
From what I remember when I tested multiple Android 11 GSIs such as Pixel Experience, I couldn't get vibration to work on my G8.