Hi,
I've unlocked and s-off'ed my m8 4.4.3 in an attempt to load a custom android 7.1.1 rom (resurrection remix to be exact). I go through all the steps laid out in wccftech.com's tutorial and when I initially install the flash boot of the extracted image (in the same folder as my sdk platform tools) and then reboot, it always gets stuck. I've tried rebooting manually after and then loading into hboot to continue with installing the .zip file in recovery, but it always fails and I think this is the cause. Is there some sort of workaround for this? It's done this on both resurrection and crDroid. I am at a loss.
Half Kitsune said:
Hi,
I've unlocked and s-off'ed my m8 4.4.3 in an attempt to load a custom android 7.1.1 rom (resurrection remix to be exact). I go through all the steps laid out in wccftech.com's tutorial and when I initially install the flash boot of the extracted image (in the same folder as my sdk platform tools) and then reboot, it always gets stuck. I've tried rebooting manually after and then loading into hboot to continue with installing the .zip file in recovery, but it always fails and I think this is the cause. Is there some sort of workaround for this? It's done this on both resurrection and crDroid. I am at a loss.
Click to expand...
Click to collapse
Do you have the latest version of twrp installed?
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 :/
Hi and a happy new year,
I have an old HTC ONE S which was running with cm10.1 until they shutdown their servers and the OS starts to missbehave.
After this I tried to switch to LieageOS 13.0 but this will need HBOOT 2.16 and as I read the upgrade of HBOOT requieres S-OFF. I tried to get the S-OFF and SID, I was able to change the SID but without a working android it seems to be impossible to get S-OFF. So I tried to reinstall the old CM 10.1 which was not working, now I installed the actual VENOM rom but all I got is a bootloop the bootloader splashscreen shows up, the phone turns black after some seconds and after this it boots into recovery (TWRP 3.1.0-0).
So I hope you will be able to help me booting an android rom and possibly upgrade HBOOT.
Thanks,
Power
With S-ON you need to manually flash the boot.img of the rom via fastboot. Unzip the rom, copy the boot.img into your fastboot directory and flash it with
Code:
fastboot flash boot boot.img
while the phone is booted to fasboot USB mode.
In addition, you might want to revert to TWRP 2.3.3.0. It's the recommended version for flashing ViperOneS 2.x*.
* I'm not sure whether facepalm can actually be used with ViperOneS 3.x since it's based on the unofficial firmware 4.05.401.1. The exploit might be fixed in that rom. However, I can tell you from personal experiences that it is working with ViperOneS 2.x. Alternatively, you could try rumrunner in combination with CM10 or CM11 (both combinations are known to work, as well).
Hi Flippy498,
thanks for your help.
It's a long time ago that I flashed this device so I didn't remember to flash the boot.img manually.
Now I have the S-OFF and was able to update HBOOT. Later on I will continue with the steps to install LineageOS.
As I can see from your footer you are using LineageOS 14.1 on this device. Are there any bugs or does this rom work without errors?
Best regards,
Alex
The proximity sensor misbehaves a bit if the lock screen is visible. Aside from that I haven't noticed any bugs/issues.
Sent from my HTC One M9 using XDA Labs
ROM cm13 or lineage
It would be interesting that someone can provide a thread where to make the steps to install a ROM cm13 or lineage from the beginning, with everything and recommendations of programs, radio, hboot and everything that is necessary...
Hi guys hope you can help,
After successfully installing Lineage OS on an old Samsung phone, I decided to try giving an old Xperia T a new lease of life. I followed this thread as a guide: https://forum.xda-developers.com/showthread.php?t=2000188
I successfully unlocked the bootloader and used flashtool to install the custom kernal listed on that thread. Thats where things got difficult, as upon restarting the phone it bootlooped. I tried flashing TWRP but couldn't get it to work so fastbooted CMD recovery, which works. I trying flashing Lineage OS as CWM13 is no longer available but could only find a Lineage 14.0 zip which I tried flashing off the exernal SD card (https://wiki.lineageos.org/devices/mint/install) which fails and gives the following error:
https://www.dropbox.com/s/ubuvxbbi2a7wruu/IMG_20180304_094603.jpg?dl=0
I was thinking maybe its not compatible so was looking for a lollypop rom to try instead, but marshmallow or above would be preferable.
Now im no expert at this so any help would be appreciated. Thanks in advance.
Ok fixed it. Also downloaded AOSPs OREO OS and the latest twrp img. The error was resolved after flashing twrp with flashtool then in recovery under advanced wipe, select system, repair or change file system, Ext4. Then flashed OS, SuperSU and Gapps (8.1) and did a backup.
Hi everyone!
I wanted to finally flash a custom ROM on my G930F (vanilla, with the latest official update) and started by installing TWRP (twrp-3.3.1-0-herolte.img.tar) via Odin (3.13.1) following this guide: https://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770.
Everything was going smoothly until step 9, because after swiping right I tried rebooting before flashing anything (found a thread on Reddit advising to just follow the guide without proceeding with rooting as indicated in the last steps). So now I'm stuck in a bootloop and I have no idea what to do, I can only access Download mode but that's it.
How do I solve this problem?
Step 10 included scenarios for both if you want root, or if you just want to boot successfully
Did you download and flash the dm-verity and force encryption disabler zip as per the step 10?
Repeat steps 6-10 and flash that zip
Beanvee7 said:
Step 10 included scenarios for both if you want root, or if you just want to boot successfully
Did you download and flash the dm-verity and force encryption disabler zip as per the step 10?
Repeat steps 6-10 and flash that zip
Click to expand...
Click to collapse
Thanks for answering!
Yes I figured out, installed TWRP via Odin again and then tried flashing that thing without wiping as shown in the video, but then I got some error messages and the device wouldn't boot up again, telling me I had to do a wipe. So I just went into recovery and did a factory reset.
Now I'd like to flash LineageOS but I'm not so sure anymore since I've had so many problems, and I have a few questions:
Do I need to reinstall TWRP?
Do I need root?
What version of LineageOS should I download?
Is there a guide for flashing LineageOS on the S7?
trim1_ss said:
Thanks for answering!
Yes I figured out, installed TWRP via Odin again and then tried flashing that thing without wiping as shown in the video, but then I got some error messages and the device wouldn't boot up again, telling me I had to do a wipe. So I just went into recovery and did a factory reset.
Now I'd like to flash LineageOS but I'm not so sure anymore since I've had so many problems, and I have a few questions:
Do I need to reinstall TWRP?
Do I need root?
What version of LineageOS should I download?
Is there a guide for flashing LineageOS on the S7?
Click to expand...
Click to collapse
Do I need to reinstall TWRP?
No TWRP will remain until you remove it or flash stock firmware.
Do I need root?
Not required to flash custom Rom's but useful
What version of LineageOS should I download?
Look at the ROM section and read up on which one you want, there are several different ones and builds so the choice is yours.
Is there a guide for flashing LineageOS on the S7?
There is always a guide contained in the post for the ROM usually at the beginning. The process of flashing Rom's is generally the same no matter what Rom you use.
All of the similar threads just end after a few replies (I think because people didn't have unlocked bootloaders) so I thought I'd try to ask again. I have a T-Mo OP8 (IN2017) on 10.5.22IN55CB. I already have the bootloader unlocked. But all of the root methods I can find need a payload.bin from the stock firmware, and I can't seem to find that. Is there another method or a source for branded firmware? I wasn't sure if I could do it by just booting the TWRP found on this board without flashing the recovery.
TIA.
SilverZero said:
All of the similar threads just end after a few replies (I think because people didn't have unlocked bootloaders) so I thought I'd try to ask again. I have a T-Mo OP8 (IN2017) on 10.5.22IN55CB. I already have the bootloader unlocked. But all of the root methods I can find need a payload.bin from the stock firmware, and I can't seem to find that. Is there another method or a source for branded firmware? I wasn't sure if I could do it by just booting the TWRP found on this board without flashing the recovery.
TIA.
Click to expand...
Click to collapse
I booted into TWRP and took a backup of the device. I then transferred the backup to my local PC and took the boot file from the backup, renaming the extension to .img. I then put this boot image on my device and downloaded magisk manager and set magisk manager to install magisk by patching a file. Once completed, I downloaded the patched file to my PC and booted to fastboot. While in fastboot, I flashed the magisk_patched boot image to both boot slots (boot_a, and boot_b). Upon rebooting, I had root. One thing, as soon as you have root, I recommend taking an image of your persist file (for fingerprint) to prevent any issues if the persist partition gets corrupted on your device. Search the forum for instructions on how to do this.
Cheers,
B.D.
You literally don't have to do anything special. Boot TWRP, flash Magisk zip in TWRP, reboot. Done.
stompysan said:
You literally don't have to do anything special. Boot TWRP, flash Magisk zip in TWRP, reboot. Done.
Click to expand...
Click to collapse
Works great. Thanks!
BostonDan said:
I booted into TWRP and took a backup of the device. I then transferred the backup to my local PC and took the boot file from the backup, renaming the extension to .img. I then put this boot image on my device and downloaded magisk manager and set magisk manager to install magisk by patching a file. Once completed, I downloaded the patched file to my PC and booted to fastboot. While in fastboot, I flashed the magisk_patched boot image to both boot slots (boot_a, and boot_b). Upon rebooting, I had root. One thing, as soon as you have root, I recommend taking an image of your persist file (for fingerprint) to prevent any issues if the persist partition gets corrupted on your device. Search the forum for instructions on how to do this.
Cheers,
B.D.
Click to expand...
Click to collapse
Post below yours worked for me but I appreciate the advice on backups and what to watch for. I haven't installed TWRP yet, just booted it and installed.
SilverZero said:
Works great. Thanks!
Click to expand...
Click to collapse
I should state one thing that I didn't in my original post. Booting TWRP and flashing that way ONLY works if you are still running Android 10. Since you have a T-Mobile variant, I knew this was a non-issue (we STILL don't have official A11). For those running Android 11, you do have to patch the boot image and flash it like stated above. Also note that this will likely change if we get TWRP on A11. Once we have that working, flashing Magisk from it should work fine.
stompysan said:
I should state one thing that I didn't in my original post. Booting TWRP and flashing that way ONLY works if you are still running Android 10. Since you have a T-Mobile variant, I knew this was a non-issue (we STILL don't have official A11). For those running Android 11, you do have to patch the boot image and flash it like stated above. Also note that this will likely change if we get TWRP on A11. Once we have that working, flashing Magisk from it should work fine.
Click to expand...
Click to collapse
Following up on this just in case you know anything new. My IN2017 just updated to A11 without any action on my part, and I lost root. Is there a TWRP or patched boot img that you know of for us on TMo now?
There is no working twrp for us on Android 11. I also haven't seen a patched boot image of 11.0.1.3.IN55CB around yet. I have that firmware extracted on my laptop so I could grab the boot image and patch it for you, but I won't be able to do that until later tomorrow. If no one else has it out or if you don't find it before I can get to it, I'll post it up.
Edit: Here's the patched boot image: Magisk Patched Boot IMG TMO 11.0.1.3