Hello,
I have the G100 and I want to know how I can install TWRP where it actually works not just sitting on the boot screen, it's flashing or intermittently working and I don't get it. Once this is done I can then get LineageOS as my main OS on the device which would be nice since installing gapps is a pain without TWRP.
Thanks
Related
I do not understand how to do what I want to do. I want to install the custom ROM LineageOS 14.1. Here's where I am stuck.
In trying to install the xt926/spyder 14.1 nightly build from 6.30.17 using ROM Manager, I get the following error message E3004: This package is for device: cdma_spyder; this device is xt926. It seems the error message states I am trying to install it on the wrong phone, so the install is aborted. But I do have an xt926 that I'm trying to install to. I posted on the Lineage site. I was told "don't use rom manager or clockworkmod they haven't been supported in years; also make sure you're using the latest TWRP for the correct device. The "this is device xxxx" is based on what the recovery says it is." I do not know which old TWRP I can use. In ROM Manager it states my current recovery is ClockworkMod 6.0.4.4. What's wrong with my recovery? The installer says I have an xt926, so why did it really fail? I'm wondering if I need the KKBL (KitKat bootloader), and the lack of that is why it really failed. If so, I do not understand from reading the posts how to get the KKBL. I read where I felt some were stating there was a small window to be able to get it and still root. I read about just flashing the BL, but then some said to never do that. Can someone please help me? TIA
Current -
OS: android 4.1.1 / 9.1.41xt926.verizon.en.us
Bootloader unlocked
Rooted
Baseband version: vanquish_bp_100700.210.64.05p
Kernel version: 3.0.31-g59a8475
System modifications: android 4.1.1 / 9.1.41xt926.verizon.en.us
Goal -
LineageOS 14.1 (Nougat)
Bootloader unlocked
Rooted
retalger said:
I do not understand how to do what I want to do. I want to install the custom ROM LineageOS 14.1. Here's where I am stuck.
In trying to install the xt926/spyder 14.1 nightly build from 6.30.17 using ROM Manager, I get the following error message E3004: This package is for device: cdma_spyder; this device is xt926. It seems the error message states I am trying to install it on the wrong phone, so the install is aborted. But I do have an xt926 that I'm trying to install to. I posted on the Lineage site. I was told "don't use rom manager or clockworkmod they haven't been supported in years; also make sure you're using the latest TWRP for the correct device. The "this is device xxxx" is based on what the recovery says it is." I do not know which old TWRP I can use. In ROM Manager it states my current recovery is ClockworkMod 6.0.4.4. What's wrong with my recovery? The installer says I have an xt926, so why did it really fail? I'm wondering if I need the KKBL (KitKat bootloader), and the lack of that is why it really failed. If so, I do not understand from reading the posts how to get the KKBL. I read where I felt some were stating there was a small window to be able to get it and still root. I read about just flashing the BL, but then some said to never do that. Can someone please help me? TIA
Current -
OS: android 4.1.1 / 9.1.41xt926.verizon.en.us
Bootloader unlocked
Rooted
Baseband version: vanquish_bp_100700.210.64.05p
Kernel version: 3.0.31-g59a8475
System modifications: android 4.1.1 / 9.1.41xt926.verizon.en.us
Goal -
LineageOS 14.1 (Nougat)
Bootloader unlocked
Rooted
Click to expand...
Click to collapse
The spyer is the old razor xt912 not the razor hd xt926 the xt926 is the vanquish. your flashing xt912 firmware on an xt926 device.
SOLVED
OGdroidster said:
The spyer is the old razor xt912 not the razor hd xt926 the xt926 is the vanquish. your flashing xt912 firmware on an xt926 device.
Click to expand...
Click to collapse
Oh! Thank you so much for the help.
retalger said:
Oh! Thank you so much for the help.
Click to expand...
Click to collapse
Sure your welcome
Has anyone managed to get Lineage OS 14.1 working on the xt926? I was able to flash it through TWRP along with opengapps 7.1 and it boots but either System UI or Setup is constantly crashing meaning i'm unable to proceed past setup.
drkdeath5000 said:
Has anyone managed to get Lineage OS 14.1 working on the xt926? I was able to flash it through TWRP along with opengapps 7.1 and it boots but either System UI or Setup is constantly crashing meaning i'm unable to proceed past setup.
Click to expand...
Click to collapse
To get 14.1 working you need to use RSDLite to flash back to 4.1.2 Jelly Bean (https://www.androidfilehost.com/?fid=24269982087011677), then install TWRP for the Photon Q (https://twrp.me/devices/motorolaphotonq.html) then use the official nightly builds for the Photon Q posted on the Lineage website. Open Gapps ARM 7.1 nano works best for me.
That said, you won't be able to use your main mic for phone calls, only speakerphone. I have yet to find a rom/recovery/firmware combination that will allow fully functional phone calls with anything above 4.4. This isn't a problem for me as this is a toy without a sim card in it, what some people call a toilet phone. It sits in my bathroom vanity and comes out when I forget one of my main devices. Other than that I play with it once every few months to see how far the development community has pushed it.
thunder2132 said:
To get 14.1 working you need to use RSDLite to flash back to 4.1.2 Jelly Bean (https://www.androidfilehost.com/?fid=24269982087011677), then install TWRP for the Photon Q (https://twrp.me/devices/motorolaphotonq.html) then use the official nightly builds for the Photon Q posted on the Lineage website. Open Gapps ARM 7.1 nano works best for me.
That said, you won't be able to use your main mic for phone calls, only speakerphone. I have yet to find a rom/recovery/firmware combination that will allow fully functional phone calls with anything above 4.4. This isn't a problem for me as this is a toy without a sim card in it, what some people call a toilet phone. It sits in my bathroom vanity and comes out when I forget one of my main devices. Other than that I play with it once every few months to see how far the development community has pushed it.
Click to expand...
Click to collapse
I tried this last weekend but was getting constant force closes from System UI so i gave up and went back to the MokeeOS build.
Thanks @thunder2132. After fumbling about, I finally got this working:
- In TWRP, wiped cache, data & system
- Reflashed 4.1.2 factory image
- I used fastboot manually and followed the recipe in the XML file. The gpt and tz images can't be downgraded, and I did not wipe userdata [not wiping this was probably a mistake])
- Rebooted to system with sim card
- Powered off
- Booted into bootloader/fastboot and flashed TWRP
- `fastboot reboot-bootloader` (in an attempt to keep the phone from trying to boot into system again)
- Booted into TWRP, flashed LOS & OpenGApps Nano
- Tried to reboot into system and failed
- Booted into TWRP, "Format Data"
- Rebooted into system, waited, profited
Now I'd like to figure out why I can only use ADB over the network. >:| It doesn't show up at all over USB, neither in LOS nor TWRP.
PS: Later I wiped system, reflashed LOS, and flashed OpenGApps *Pico*. No issues yet.
polyzen said:
Thanks @thunder2132. After fumbling about, I finally got this working:
- In TWRP, wiped cache, data & system
- Reflashed 4.1.2 factory image
- I used fastboot manually and followed the recipe in the XML file. The gpt and tz images can't be downgraded, and I did not wipe userdata [not wiping this was probably a mistake])
- Rebooted to system with sim card
- Powered off
- Booted into bootloader/fastboot and flashed TWRP
- `fastboot reboot-bootloader` (in an attempt to keep the phone from trying to boot into system again)
- Booted into TWRP, flashed LOS & OpenGApps Nano
- Tried to reboot into system and failed
- Booted into TWRP, "Format Data"
- Rebooted into system, waited, profited
Now I'd like to figure out why I can only use ADB over the network. >:| It doesn't show up at all over USB, neither in LOS nor TWRP.
PS: Later I wiped system, reflashed LOS, and flashed OpenGApps *Pico*. No issues yet.
Click to expand...
Click to collapse
Nice! I'm glad you got it working.
what do you mean with reflashed factory image 4.1.2?
I was on Resurrection Remix for the Razr M and now flashed LOS from this thread because of connectivity problems and I hoped it is a problem of RR. But unfortunately I still just have Edge connection, no 3G or 4G. Does anyone know how to fix that? There were no problems under 4.1.
Edit: I went back to 4.1.2 and wanted to start from zero but now on 4.1.2 there's only Edge connection as well :/
So long time android user. I have the tmo variant of the Oneplus7 pro with unlocked bootloader via exploit found. Have twrp installed amd stock rom rooted with magisk. I tried installing the Havoc and the Aosip rom followed directions step by step. Havoc booted to the first gteen splash screen then reboots to fastboot. Aosip gets to the settimg up wifi then reboots to fastboot. I made a backup of the stock rom before installing anything and im able to restore it with twrp and root. I looked in the threads but didn't find anything unless i missed it. Also been sitting on telegram waiting on someone to shed some light.
fordstang99 said:
So long time android user. I have the tmo variant of the Oneplus7 pro with unlocked bootloader via exploit found. Have twrp installed amd stock rom rooted with magisk. I tried installing the Havoc and the Aosip rom followed directions step by step. Havoc booted to the first gteen splash screen then reboots to fastboot. Aosip gets to the settimg up wifi then reboots to fastboot. I made a backup of the stock rom before installing anything and im able to restore it with twrp and root. I looked in the threads but didn't find anything unless i missed it. Also been sitting on telegram waiting on someone to shed some light.
Click to expand...
Click to collapse
Trying the canary build
It worked with canary 19.4
Mods please delete if need be
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.
I have a problem installing Lineage OS. I have installed it with its official method, but at the time of starting its initial configuration it restarts several times until it goes into recovery mode, with the legend of Corrupt Android.
The same thing happens to me with the Pixel Experience which is being developed to be the official ROM soon. The difference is that before restarting and finishing in the same it appears to me that "com.phone.services" It has stopped.
I have done everything by fastboot and platforms tools as indicated by the official methods and their own provided recovery's.
With the STOCK ROM no problem.
Does anyone know what happens?
The recovery images that come from LineageOS site don't seem to work for me. I had to go here to get LOSRecovery.img for it since that's the only possible way any version of LineageOS will function.
Also, from my experience, the unofficial TWRP has issues when installed, but not when booted up directly from bootloader.
PeeJay Bonobo said:
The recovery images that come from LineageOS site don't seem to work for me. I had to go here to get LOSRecovery.img for it since that's the only possible way any version of LineageOS will function.
Also, from my experience, the unofficial TWRP has issues when installed, but not when booted up directly from bootloader.
Click to expand...
Click to collapse
PeeJay Bonobo said:
The recovery images that come from LineageOS site don't seem to work for me. I had to go here to get LOSRecovery.img for it since that's the only possible way any version of LineageOS will function.
Also, from my experience, the unofficial TWRP has issues when installed, but not when booted up directly from bootloader.
Click to expand...
Click to collapse
I understand, but it is something that also happens to me with the Pixel Experience.
I have not used TWRP. Only the official methods by fastboot and platforms tools
I am still trying to fully wrap my head around Android moving to Slot partitions. I am reading as much as I can and feel I have a better understanding of it but have tried to flash lineageOS with microg but ended up with a bricked device maybe due to not doing the proper steps to switch to the active slot? My question is if I have TWRP installed and currently on OOS 11, can I just flash the zip file for lineage OS or so I need to do something additional? The TWRP script states you have to boot into Recovery to switch active slots and flash additional items. I know if I flash lineage I will end up with their Recovery as well which I obviously dont want. Can I flash the TWRP installer after flashing lineageOS zip or no? Please help confirm or deny what needs to be done given my current setup.
Thank you all in advance for any help/experiences you can share about this.