Related
I have always gone with Motorola phones in the past because they have always been root friendly. Not too long ago I picked up a Moto e6 after looking online to make sure it was rootable. Seems I may have the only version of the phone on earth that cannot be rooted. I've been trying to use the Magisk method. First, I tried having Magisk modify the boot.img file and while it says "success" at the end, with no errors, it is totally borked. The boot.img (original) is 32Mb in size but the Magisk-modified (rooted) boot.img is only 9.7Mb. I've gone down this road before and if I go ahead and try and flash that boot.img to my phone, it will brick. Then I tried to run Magisk on the recovery.img instead. That original file is 48Mb in size but the Magisk-modified version is only 15.9Mb. Again, from past experience I'm not even going to try and flash that image to the phone because the recovery will be borked.
My phone is a Moto e6 Surfna, retail unlocked, Android 9, build number PPBS29.73-81-5-14-5-4-2-6-3. I tried once before using a basic stock ROM of 28.73-81 but that REALLY borked the phone with it, pre-root attempt, being unable to even see its own cell phone modem (it became a tiny tablet device with only wifi). I assume that there was something wrong/missing in the stock rom vs my phone. Why is Magisk borking the boot and recovery images so badly? Is there ANYONE on Earth with a successfully rooted Moto e6 retail with the build I have?
So I'm pretty new on the whole android customization scene and I've been really wanting to install Android Open Source Project on my Android 10 phone for a while. I've found a video detailing how to go about it, but my problem is that there's not a version of TWRP for my specific phone yet (I have a Blackview BL6000 pro). For the purposes of making a recovery and installing AOSP, I'm wondering if there's another good app that could replace TWRP that functionally does the same things (Or if someone has a TWRP version somehow) that lets me install AOSP.
The video in question I was using as a guide was this one:
Any help would be hugely appreciated!
magermerch said:
So I'm pretty new on the whole android customization scene and I've been really wanting to install Android Open Source Project on my Android 10 phone for a while. I've found a video detailing how to go about it, but my problem is that there's not a version of TWRP for my specific phone yet (I have a Blackview BL6000 pro). For the purposes of making a recovery and installing AOSP, I'm wondering if there's another good app that could replace TWRP that functionally does the same things (Or if someone has a TWRP version somehow) that lets me install AOSP.
The video in question I was using as a guide was this one:
Any help would be hugely appreciated!
Click to expand...
Click to collapse
You not need TWRP for flash GSI (Custom ROMs). You need stock firmware of your device from company or you should make that your self about any problem with your actions.
After you can know how to do have GSI in your device with commands fastbootd: Installing GSI with fastbootd
and/or using this software: Treble Toolkit [A and A/B]
Ofcourse if yourr device is A/B so you need flash the GSI.img in the system_a or system_b so need know what slot is able to that.
Hello,
I have a moto G100 I just purchased. I unlocked the bootloader and I tried to install LineageOS but it was being difficult. I could get it to boot into TWRP. Now I tried to restore everything to stock as it wasn't even booting. After flashing the rom back in via fastboot the unit shows up as a serial device but that's it, no picture on the screen or anything.
I need some help to get this working again. Besides the directions on the LineageOS page sucks, steps are missing and things do not work properly.
Any help would be appreciated.
This is Qualcomm HS-USB QDLoader 9008 mode and won't boot.
Can anyone please help so this won't take weeks or months?
Thanks
Hello,
I fixed the brick with the blankflash file blankflash_nio_RRTS31.Q1-84-24-3-6
I was able to then use the official tool to recover the firmware. I was able to get LineageOS working but I wasn't able to do TWRP at all properly.
So I managed to install twrp but couldn't install lineage or anything out of it...
I managed to get TWRP installed but it was essentially useless as I couldn't access the internal flash unless it was setup by the OS already if you format the internal flash storage with TWRP it's useless especially via MTP.
I was able to install LineageOS and I was able to boot it, but I don't understand why it says I do not have enough space to install gapps. Without gapps LineageOS is essentially useless as an OS unless you do not use anything from google at all whatsoever not eve maps or anything.
How do I fix it so I can install gapps? I can't resize the system partition via TWRP as it doesn't even show it.
Thanks
if you have the bootloader unlocked you can try the "tinyflashscript" way and use that to overwrite all partitions with a stock image found here
RET stands for Retail and than the region code follows, just download the latest one for your region
after that your partitions are reset to the start and you could keep it that way or attempt to install lineage again but clean this time
I ran into the exact same situation as you with the storage issues and this fixed it for me
Hello my G100 was fully hard bricked trying to installed LineageOS (not the modded). I followed the following steps:
1. Installed and booted into LineageOS recovery from electimon.
2. Factory reset
3. Install ROM as adb sideload.
However, installation stuck at 47% and aborted. Phone was hard bricked once turned off. It couldn't even boot into booloader.
Luckily, I was able to enter EDL mode by pressing and holding volume and power down together for some time while it was plugged into PC using usb. Then I used blankflash to restore. This saved me from taking it to repair centre.
Hello,
I had the same brick issue and blankflash fixed it for me. I will try writing stock again then install LOSRecovery again and then try sideloading both LineageOS and gapps but I don't think that will work correctly as I think I did try that but we shall see, last time I did an install though after fixing the brick issue I used fastboot to do the stock recovery which should have fixed the partition sizes...
Thanks
It's strange that device becomes hard bricked because I installed LineageOS before and it booted fine. Only thing now changed is that I'm using February stock ROM instead of December one. Did Motorola change anything in Feb update that would cause hard brick when trying to install custom ROM?
Also, I've never did the "Ensuring all firmware partitions are consistent" thing. It worked before but not sure if we need to do it now.
Hello,
Strange indeed I can get LineageOS installed BUT because this is an A/B phone which is so silly, I can't install Gapps into LineageOS so essentially useless as the installer says the partition is too small and I do not have a way to fix that at the moment.
Thanks, and blankflash was able to get me up and running on stock but I cannot use the phone yet just like the DooGee S95 Pro I bought in hopes to use LineageOS... long story. Stuck with my ZTE Axon 7 from 2016 and a crap phone to make calls since my provider killed service to my ZTE Axon 7 so I carry basically 3 phones now. Until there is a fully working TWRP I am essentially screwed and feel like I wasted $400 on another phone.
marcusah123 said:
Hello,
Strange indeed I can get LineageOS installed BUT because this is an A/B phone which is so silly, I can't install Gapps into LineageOS so essentially useless as the installer says the partition is too small and I do not have a way to fix that at the moment.
Thanks, and blankflash was able to get me up and running on stock but I cannot use the phone yet just like the DooGee S95 Pro I bought in hopes to use LineageOS... long story. Stuck with my ZTE Axon 7 from 2016 and a crap phone to make calls since my provider killed service to my ZTE Axon 7 so I carry basically 3 phones now. Until there is a fully working TWRP I am essentially screwed and feel like I wasted $400 on another phone.
Click to expand...
Click to collapse
Using the method I described above I was able to install Lineageos 19.1 and then gapps (mindthegapps) using lineage recovery. it should be entirely possible
Hello,
With the storage not being large enough I was trying to install openGapps ( stock size ) for Android 11 since I was trying to use Lineage 18.1 and not 19/19.1 since 19/19.1 appear to have bugs and 18.1 does not. Anyhow I tried to sideload openGapps and it said there wasn't enough space on the system partition. I suppose I should try mindthegapps instead.
Thanks
So anyone successfully installed it without causing hardbrick? What exact steps did u follow? r u using g100 or edge s and what is the build number of stock rom prior to install? thanks
Windoors said:
So anyone successfully installed it without causing hardbrick? What exact steps did u follow? r u using g100 or edge s and what is the build number of stock rom prior to install? thanks
Click to expand...
Click to collapse
I used the latest stock after doing a recovery with blankflash and the rescue utility from Motorola. I then installed LOSrecovery because TWRP isn't ready. I then booted into LOSrecovery and sideloaded 19.1 latest from this forum. I can't figure out how to resize /system correctly so I cannot install anything other than MindTheGapps which sucks a lot.
Anyhow if we get a working TWRP soon that will allow resize as TWRP can't show the system partition and A/B switching is being worked out then we will be good to go.
If this isn't helpful or you need exact commands then I can do that too for you.
Hi! Are there any pro’s out there that can help out with some issues, we are having with 3 phones.
It would be greatly appreciated. I believe we are not the only ones.
How can a BOOT.IMG be extracted from an Android Phone if there is no Stock Firmware ROM available?
All 3 phones manufactured in 2022.
The Bootloader is unlocked for all 3. USB Debugging is turned on.
- Moxee m2160 MH-T6000 only boots to Fastboot & Recovery. I have tried to restore but it will not restore.
- Vortex V22 has a GSI Pixel Experience Plus 13 ROM installed and is unable to go back to factory ROM image.
- ANS ACK2326 is on a stock Android 12 ROM and hasn’t been modified but has a build number kirk2_v1 2.0_BTM-ST.
Is it possible to get a Generic BOOT.IMG to modify for root?
Are there other ROMS like GSI’s with a BOOT.IMG that could work to try to get root?
Are there other ways to get root without a BOOT.IMG?
Is there a way to parse the entire phone to compile a BOOT.IMG?
The manufacturers were contacted. No system firmware ROM is available online that we could find after searching. We don’t have any experience searching china websites or know where to begin. If someone knows where we could find the stock ROM's on a China website that would be a great help!
Are we SOL? Are phones that don’t publish stock firmware that secure that if you need a BOOT.img from stock firmware to get to access the entire encrypted rom, you are out of luck?
Or, would we need a Jtag hardware reader?
Thank you in advance for your time and help which is greatly appreciated!
The boot image contains the kernel for that specific device; there is no such thing as a "generic boot image", as the kernel has to have the basic drivers for that specific device's hardware.
It's possible to dump the boot image if you already have root, but I'm assuming that the whole reason you want the boot image is to patch it with Magisk to gain root.
The alternative, if TWRP is available, is to use ADB through TWRP to dump the boot partition.
If you can't use TWRP and aren't rooted, there is no way to dump the boot partition through fastboot.
V0latyle said:
The boot image contains the kernel for that specific device; there is no such thing as a "generic boot image", as the kernel has to have the basic drivers for that specific device's hardware.
It's possible to dump the boot image if you already have root, but I'm assuming that the whole reason you want the boot image is to patch it with Magisk to gain root.
The alternative, if TWRP is available, is to use ADB through TWRP to dump the boot partition.
If you can't use TWRP and aren't rooted, there is no way to dump the boot partition through fastboot.
Click to expand...
Click to collapse
Thanks you for the reply! That is correct. Our ultimate goal is to gain root on these devices. Is Magisk the only root pathway or are there other rooting options?
Can you use ADB Shell, ADB root and dd to pull the boot partitions?
There is not a TWRP available for these devices. How would you go about making a TWRP for these phones? Do you need the stock firmware?
defcondoc said:
Thanks you for the reply! That is correct. Our ultimate goal is to gain root on these devices. Is Magisk the only root pathway or are there other rooting options?
Click to expand...
Click to collapse
No, but it is the most popular and arguably the best
defcondoc said:
Can you use ADB Shell, ADB root and dd to pull the boot partitions?
Click to expand...
Click to collapse
No, because again you need root to run adbd as root. I could be wrong...
defcondoc said:
There is not a TWRP available for these devices. How would you go about making a TWRP for these phones? Do you need the stock firmware?
Click to expand...
Click to collapse
I am not a developer so I have no idea but I imagine you'd need the original kernel source, yes.
If u have mtk there are many options
1:using mtk client
2: using mtk bypass and wwr2
Then if u have snapdragon u need the gfil software and the phone firehose programmer
another risky way is to flash rooted GSI. but in case it boot loops, you are screwed without stock ROM. the user @gregeerg ended up with a semi bricked phone, luckily he was able to pull boot.img from adb, so another member @Jet! with same device could finally root his phone and provide super.img for unbrick. So this method is only working if you have two identical phones.
kelvinchinedu said:
If u have mtk there are many options
1:using mtk client
2: using mtk bypass and wwr2
Then if u have snapdragon u need the gfil software and the phone firehose programmer
Click to expand...
Click to collapse
I actually had or was going to ask this if there is a way to access firmware from the hardware level. Somehow the post never got posted or deleted.
Anyway, with MTK Client & QFIL, how complicated is it to extract the firmware from a device? Will it work with all devices, or will I run into issues with newer devices? I will do some researching on these and see what I can find. Thank you!
alecxs said:
another risky way is to flash rooted GSI. but in case it boot loops, you are screwed without stock ROM. the user @gregeerg ended up with a semi bricked phone, luckily he was able to pull boot.img from adb, so another member @Jet! with same device could finally root his phone and provide super.img for unbrick. So this method is only working if you have two identical phones.
Click to expand...
Click to collapse
Interesting. Where can I get a rooted GSI? I tried to searching but couldn't find anything. Is there a special way to search for one. I would be willing to try this. I had a boot loop on one and a unofficial unrooted PixelExp13 GSi fixed it.
[DISCONTINUED][GSI][11] LineageOS 18.x GSI (all archs)
Background: This is a natural continuation/extension of the LineageOS 17.x GSIs I've been making since November 2019. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance...
forum.xda-developers.com
alecxs said:
[DISCONTINUED][GSI][11] LineageOS 18.x GSI (all archs)
Background: This is a natural continuation/extension of the LineageOS 17.x GSIs I've been making since November 2019. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you! I'm assuming these are all GSI builds from LOS 16-20? Am I also correct in saying the difference in the bgN, bvN, bvS, files? b = a/b system, g = gapps installed, v = vanilla - no gapps installed. N = No Root? S = Root?
To get a GSI that is already rooted, I must install the file with S in the filename?
alecxs said:
[DISCONTINUED][GSI][11] LineageOS 18.x GSI (all archs)
Background: This is a natural continuation/extension of the LineageOS 17.x GSIs I've been making since November 2019. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance...
forum.xda-developers.com
Click to expand...
Click to collapse
OMG Thank you alecxs! Bravo! This is exactly what I was looking for! One install with no stock ROM rooted successfully!, two more to go. And especially thanks to andyyan for making this GSI image possible!
defcondoc said:
OMG Thank you alecxs! Bravo! This is exactly what I was looking for! One install with no stock ROM rooted successfully!, two more to go. And especially thanks to andyyan for making this GSI image possible!
Click to expand...
Click to collapse
May I ask you which of your devices listed above did you get it to work on the reason I ask is I have 2 of those phones am I'm trying to do the same thing. Thanks
omb714.1980 said:
May I ask you which of your devices listed above did you get it to work on the reason I ask is I have 2 of those phones am I'm trying to do the same thing. Thanks
Click to expand...
Click to collapse
The Vortex V22 I got to work successfully with a GSI root. I was able to get root with the Moxee but I have yet to get a custom rom or working GSI rom. I'll post when I get a working rom with the Moxee. The ANS has been a bit of trouble because I cannot get the BL unlocked even though it has OEM unlocking turned on.
defcondoc said:
The Vortex V22 I got to work successfully with a GSI root. I was able to get root with the Moxee but I have yet to get a custom rom or working GSI rom. I'll post when I get a working rom with the Moxee. The ANS has been a bit of trouble because I cannot get the BL unlocked even though it has OEM unlocking turned on.
Click to expand...
Click to collapse
I'm having the same issue with the ANS your not alone.
omb714.1980 said:
I'm having the same issue with the ANS your not alone.
Click to expand...
Click to collapse
I appreciate you letting me know. Good to know I'm not the only one.
Did anyone ever figure out how to unlock the bootloader yet?
ronnieshane1 said:
Did anyone ever figure out how to unlock the bootloader yet?
Click to expand...
Click to collapse
I do know it is available somewhere and most likely password protected but to my knowledge it hasn't been made publicly yet. I'm still waiting as well. I've be able to do some workarounds with the stock rom but I would really like to get access to the firmware or boot image.
defcondoc said:
I do know it is available somewhere and most likely password protected but to my knowledge it hasn't been made publicly yet. I'm still waiting as well. I've be able to do some workarounds with the stock rom but I would really like to get access to the firmware or boot image.
Click to expand...
Click to collapse
I know right! I cant find hardly anything on the ACK2326 at all! I wish they would go ahead and make it public already.
Hi, I know I'm making a big ask here. But I picked this model of phone Moto One with the intent of flashing /e/ OS to it. I have the device in hand now and have noticed it seems to be stuck on Android 10. I'm on build QZKS30.Q4-40-64-23 I've went out and grabbed the next latest version of firmware I could find XT2113-5_KIEV_ATT_11_RZKS31.Q3-45-16-8-3_subsidy-ATT_RSU_regulatory-DEFAULT_CFC.xml I've also grabbed the TWRP from this same forum. I've already unlocked the bootloader and enabled ADB debugging. Finally I've got the android sdk on computer, I'm running on Mint linux. is upgrading the ROM on this as easy as flashing it from recovery? Or is there more required to go from 10 to 11? I just need to this phone to Android 11 so I can flash /e/ on it. Thanks in advance for any help/advice!
You can't flash a stock ROM from recovery. But it is easy enough from fastboot.
CaptainIndustry said:
Hi, I know I'm making a big ask here. But I picked this model of phone Moto One with the intent of flashing /e/ OS to it. I have the device in hand now and have noticed it seems to be stuck on Android 10. I'm on build QZKS30.Q4-40-64-23 I've went out and grabbed the next latest version of firmware I could find XT2113-5_KIEV_ATT_11_RZKS31.Q3-45-16-8-3_subsidy-ATT_RSU_regulatory-DEFAULT_CFC.xml I've also grabbed the TWRP from this same forum. I've already unlocked the bootloader and enabled ADB debugging. Finally I've got the android sdk on computer, I'm running on Mint linux. is upgrading the ROM on this as easy as flashing it from recovery? Or is there more required to go from 10 to 11? I just need to this phone to Android 11 so I can flash /e/ on it. Thanks in advance for any help/advice!
Click to expand...
Click to collapse
So I lied about the bootloader being unlocked, apparently its not eligible for unlocking due to Motos policies. Is there any other way to get this device to 11 or am I at the end of the road already?
You need to flash the firmware you downloaded in fastboot. There's a bunch of scripts to do this, I think I used RSD-Lite-Mac-Linux last time. flashfile.xml wipes data and servicefile.xml keeps data.
If your at all unsure about the firmware being correct for your device, go to a Windows PC and use the official recovery tool instead.