Related
Not really sure what I'm doing wrong. Last rooted phone was a Nexus 5, and that was of course painless to root and flash ROMs to...
I'm using a Verizon XT1096 with 5.1 on T-Mobile.
So I was able to get the bootloader unlocked via Motorola's website, now that Verizon is allowing them to do so. No problems there. My problem now is that I can flash a recovery, but if it reboots, the recovery is gone. And I can't get any recoveries to flash anything. I can't push an apk, root zip, or even a ROM. Says Installation Aborted, with no other error codes. Even tried CWM and disabling Signature Checking, which gives me more info, saying that the footer is mismatched. Phone does say the bootloader is unlocked though so that shouldn't be it...
Honestly, I'd just like to get it on CM12 until I can get a Nexus 6P.. Can anyone tell me if I'm doing something wrong? Or is there just no way to root yet? I figured even the XT1095 CF-Auto-Root method would work for 5.1, but no dice..
Not sure what to do here. Please move my thread if need be. Don't post here much...
I followed the instructions on the TWRP website (link below) and it worked flawlessly. One thing you have to do is, after running the "fastboot flash recovery twrp.img" command, make sure to manually scroll on the phone and reboot into recovery. Hope that helps...
https://twrp.me/devices/motorolamotox2014.html
There is a partition mismatch. So do this. Download supersu and place it in the phones memory. Boot to fastboot mode and then fastboot boot recovery.img rather than fastboot flash recovery.img. You will boot to twrp, install SuperSU then download twrp from the playstore and install thru the app. It works, that's how I did it. Also when booting to recovery from the fastboot menu choose recovery with the vol up key rather than power button.
RepeatUntilTheEnd said:
I followed the instructions on the TWRP website (link below) and it worked flawlessly. One thing you have to do is, after running the "fastboot flash recovery twrp.img" command, make sure to manually scroll on the phone and reboot into recovery. Hope that helps...
https://twrp.me/devices/motorolamotox2014.html
Click to expand...
Click to collapse
I thought I tried that but maybe not. I've read that some stock ROMs can and will overwrite the recovery upon booting, but I could be wrong. I'll look at that when I get home tonight.
oraixearl said:
There is a partition mismatch. So do this. Download supersu and place it in the phones memory. Boot to fastboot mode and then fastboot boot recovery.img rather than fastboot flash recovery.img. You will boot to twrp, install SuperSU then download twrp from the playstore and install thru the app. It works, that's how I did it. Also when booting to recovery from the fastboot menu choose recovery with the vol up key rather than power button.
Click to expand...
Click to collapse
Thank you, I'll try this tonight when I get home. This may solve it. I think I remember the bootloader spitting something out about a partition mismatch.. Will report back as soon as I try it.
So I went ahead and tried both your guys' methods.
Oraixearl, I figured your solution would work, but it actually didn't, to my surprise. It returned no results, as the root zip didn't end up doing anything.
RepeatUntilTheEnd's solution worked here. I guess I didn't try rebooting the phone after flashing the recovery, before going into it..
So here's what I did.
1.) Boot into bootloader
2.) Fastboot flash recovery [recovery.img]
3.) adb reboot bootloader
4.) Used keys on phone to go into recovery,
5.) Flashed root.zip
6.) Booted into OS, and ran root checker. Worked.
7.) To my surprise, TWRP stuck around, too.
Thank you guys!
TsarProdigy said:
So I went ahead and tried both your guys' methods.
Oraixearl, I figured your solution would work, but it actually didn't, to my surprise. It returned no results, as the root zip didn't end up doing anything.
RepeatUntilTheEnd's solution worked here. I guess I didn't try rebooting the phone after flashing the recovery, before going into it..
So here's what I did.
1.) Boot into bootloader
2.) Fastboot flash recovery [recovery.img]
3.) adb reboot bootloader
4.) Used keys on phone to go into recovery,
5.) Flashed root.zip
6.) Booted into OS, and ran root checker. Worked.
7.) To my surprise, TWRP stuck around, too.
Thank you guys!
Click to expand...
Click to collapse
Strange as it worked for me. I'm glad you got it sorted out tho. Cheers.
Hello,
I am new to this forum, but have done a bit of unlocking and installing custom roms on other phones (mostly OPO's, both my old one and friends). But this new OP 3T I just got is giving me some troubles I have not encountered before. I would LOVE to put this into the correct forum, but of course with my being new to this forum...rules...
I am following the standard install over on the TWRP site and on the OP3T, the install finishes and then I reboot and I get a screen that says:
"Your device has been unlocked and can't be trusted. If you don't want to see this screen, please lock your device by "fastboot oem lock" an erase userdata..."
I have never seen this before. Can someone give me a idea what could be going on here? Do I need to re-lock it? What did OP do to their phones!!?!
Oh and also, I am planning on installing LineageOS. Any reason I shouldn't?
Thanks!
Blenderite said:
Hello,
I am new to this forum, but have done a bit of unlocking and installing custom roms on other phones (mostly OPO's, both my old one and friends). But this new OP 3T I just got is giving me some troubles I have not encountered before. I would LOVE to put this into the correct forum, but of course with my being new to this forum...rules...
I am following the standard install over on the TWRP site and on the OP3T, the install finishes and then I reboot and I get a screen that says:
"Your device has been unlocked and can't be trusted. If you don't want to see this screen, please lock your device by "fastboot oem lock" an erase userdata..."
I have never seen this before. Can someone give me a idea what could be going on here? Do I need to re-lock it? What did OP do to their phones!!?!
Oh and also, I am planning on installing LineageOS. Any reason I shouldn't?
Thanks!
Click to expand...
Click to collapse
Is nothing wrong with your device ..What you get is a warning that your bootloader is unlocked ...
You gonna get this every time you want to boot to your ROM or to twrp....
You can proceed further to install any ROM that you like...
I think you can find a guide on XDA forums to disable this warning if you want...
cultofluna said:
Is nothing wrong with your device ..What you get is a warning that your bootloader is unlocked ...
You gonna get this every time you want to boot to your ROM or to twrp....
You can proceed further to install any ROM that you like...
I think you can find a guide on XDA forums to disable this warning if you want...
Click to expand...
Click to collapse
Ok I tried that and a new problem came up!! When I try to reboot into recovery, I do not get TWRP, but the stock recovery that was there originally! Unless they have completely changed the look of TWRP. I will try to upload a picture of it if that helps.
You can't get rid of the bootloader-unlocked warning without re-locking your bootloader, which you really should not do while you have a custom recovery installed.
Are you sure you've flashed TWRP and not just booted it it from a local file on your computer? Try using fastboot to wipe recovery first before flashing TWRP.
Anova's Origin said:
You can't get rid of the bootloader-unlocked warning without re-locking your bootloader, which you really should not do while you have a custom recovery installed.
Are you sure you've flashed TWRP and not just booted it it from a local file on your computer? Try using fastboot to wipe recovery first before flashing TWRP.
Click to expand...
Click to collapse
I followed the Fastboot method on this page (rules won't let me post the link normally): twrp. me/devices/oneplus3t.html
Blenderite said:
I followed the Fastboot method on this page (rules won't let me post the link normally): twrp. me/devices/oneplus3t.html
Click to expand...
Click to collapse
Right on that page (last paragraph of fastboot install method), you will see:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
I had a heck of a time with this myself (even reading the above). Even rebooting (after flash TWRP) to recovery (power+vol down), the TWRP install would still not "stick". Had to try multiple times. I also rooted with SuperSU 2.79 at some point in that process, which may or may not have helped TWRP to finally "stick".
redpoint73 said:
Right on that page (last paragraph of fastboot install method), you will see:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
I had a heck of a time with this myself (even reading the above). Even rebooting (after flash TWRP) to recovery (power+vol down), the TWRP install would still not "stick". Had to try multiple times. I also rooted with SuperSU 2.79 at some point in that process, which may or may not have helped TWRP to finally "stick".
Click to expand...
Click to collapse
I tried this once before, but after your suggestion to try it several times, it finally worked! Thanks!!
Flash TWRP, reboot, press the volume down key before the phone boots, go into recovery, you should see TWRP flash screen, that usually works but I'm glad you got it going
Hi,
I'm having a bit of trouble. I had a brand new Redmi 4X, and I was advised to install TWRP, root it, and install the Xiaomi.eu rom until LineageOS is released. I unlocked the bootloader, flashed TWRP, managed to get into it once and now I can't do it again. When TWRP loaded it asked me for a password for decryption but it let me just skip it it seems (not sure if that is the problem) but now I can't boot normally, I can't boot into recovery, but fastboot seems to work okay. How do I go about fixing this?
I've tried reflashing TWRP but I still can't get to it, and I don't really know enough about this stuff to know where I've gone wrong.
UPDATE - I think this is to do with dm-verity and having the stock kernel installed. Now it's too late to undo what I've already done, so I hope to god that someone knows how to fix this.
UPDATE - Right, the problem is solved I think. I had to do an awful lot of googling, and I'm not entirely sure what it was specifically that fixed it. But I found a guide that taught me the fastboot command "fastboot boot twrp.img" which saved the day. Even when my phone wouldn't let me into recovery, it allowed me to flash a no-verity.zip which i think is what allowed me to boot, and it allowed me to flash superSU.zip and then the ROM I was aiming for. And now I've booted into the ROM successfully and hopefully I am rooted and all is well. Plus I can access TWRP as normal now.
Any help would be greatly appreciated
Can you boot into TWRP by pressing the buttons so that you boot directly to TWRP??
Have you tried Command Prompt to boot with commands in to recovery??
And if you get into TWRP you should have everything on the SDCard and then just
format all things except SDCard and then flash from SDCard everything
That is what I would try..and yes it ask for a password but just skip it to get to it
If you can get into TWRP to flash from SDCard then you good to go..if not
Google all the commands for CMD..and plug your phone to the PC and flash everything with the
commands.....
Let us know what is working and what not and what steps exectly you are doing
EDIT
Turn off your device > Press and hold “Power” and “Volume +” buttons at the same time.
After short vibration signal release the power button and wait for TWRP to start.
To boot in stock recovery open “Update” app.
In the setting select “Boot in recovery”.
brljak83 said:
Can you boot into TWRP by pressing the buttons so that you boot directly to TWRP??
Have you tried Command Prompt to boot with commands in to recovery??
And if you get into TWRP you should have everything on the SDCard and then just
format all things except SDCard and then flash from SDCard everything
That is what I would try..and yes it ask for a password but just skip it to get to it
If you can get into TWRP to flash from SDCard then you good to go..if not
Google all the commands for CMD..and plug your phone to the PC and flash everything with the
commands.....
Let us know what is working and what not and what steps exectly you are doing
EDIT
Turn off your device > Press and hold “Power” and “Volume +” buttons at the same time.
After short vibration signal release the power button and wait for TWRP to start.
To boot in stock recovery open “Update” app.
In the setting select “Boot in recovery”.
Click to expand...
Click to collapse
Thanks for the reply. I can't get into TWRP. Even if I could get into TWRP how would I get files on the phone to flash them?
Is it possible to flash any rom from the pc directly and if it is will this possibly help? I think it's not booting because the kernel is still stock.
I'm not sure what you mean in the edit, how do I boot into stock recovery without being able to boot the phone (and when I have already flashed TWRP)?
brokemyG2 said:
Thanks for the reply. I can't get into TWRP. Even if I could get into TWRP how would I get files on the phone to flash them?
Is it possible to flash any rom from the pc directly and if it is will this possibly help? I think it's not booting because the kernel is still stock.
I'm not sure what you mean in the edit, how do I boot into stock recovery without being able to boot the phone (and when I have already flashed TWRP)?
Click to expand...
Click to collapse
Hii
I just have been reading about this bootloop
Go over here and read all of the 6 pages..will not take much time but could help you out much
https://forum.xda-developers.com/xiaomi-redmi-4x/development/official-twrp-3-2-1-0-xiaomi-redmi-4x-t3718217
Hey, I have exactly the same problem. Latest stock rom, flashed twrp in fastboot and got into the boot loop. Nothing works. I can only enter fastboot. What exactly did you do then? What is this no-verity.zip? I can't find anything about it.
I had a problem
I unlocked bootloader then installed redwolf recovery and took a nandroid backup. After that i rebooted to system but stuck into bootloop, could not boot to recovery, could not boot into system, So the only thing worked was that i flashed fastboot rom with mi flasher. And syccessfully rebooted to system with bootloader locked and stock recovery. So, if anyone have same problem you can do the same. How do i install recovery safely again? Should i use TWRP only? Should i flash v3.1.0 with lazy flasher or v3.2 directly without lazy flasher? I don't want to stuck into bootloader again, have to get all data deleted.
Hello guys!
Yesterday I tried to flash the newest Lineage-built to my new G7+ (XT1965-3, bought in Germany via Amazon), but something went wrong and now I'm afraid, I bricked my phone.
It's not my first flash of Lineage, as I did this in the past already on some older Phones (SII, SIII, S5), but it's the first time, that I have a major issue.
So I followed all the steps on the Lineage-Wiki (on Win10).
After flashing the recovery (the lineage-recovery, not TWRP) I wasn't able to enter the recovery-mode, so the phone booted to StockRom. And probably this was the problem: As it didn't react to VolumeDown+Power, I reflashed the recovery a second time. After that the touch-screen is not working any more.
I am able to enter the recovery-mode and I can boot to Stock-Rom, but in both modes the phone does not react to touch, so I can only use the Volume- and Power-Buttons.
Probably I made more mistakes after that: I thought, that a factory-reset would help, but It didn't. I also relocked the bootloader, but as I saw, that it also did not bring any solution, I unlocked it a second time.
Conclusion: I have a brand new phone, with lineage-recovery, an unlocked bootloader but without touch working.
I also tried to flash Lineage, but the sideload got stuck at 47%. So Lineage is not installed and it boots into Stock, where I can not get any further without touch.
Has anyone any idea, what could be the issue and how I can fix it? I would like to start from scratch, but I don't know, what is the exact problem and if i can for example return to stock recovery.
Thank you!
---- EDIT ----
If it helps: I am able to boot TWRP via "fastboot boot twrp-xxx.img". And in TWRP the touch works!
I could flash lineage directly via TWRP from external sd-card, but i am afraid that after that I won't be able to return if something goes wron.
probably your best bet is to go right back to stock using the LMSA tool and starting fresh. I've seen others encounter similar issues on different devices and always the cleaneast solution was just to role back everything and start over.
Thank you so much. With LMSA I managed to restore everything to stock and touch is working!
So I'm going to start from scratch and finally install Lineage.
Is is indicated to use the Lineage-Recovery, as the Lineage-Wiki says, or would it better to use TWRP?
TWRP gives me the option to flash from sd-card, which seems to me better than via sideload.
joglxv said:
Thank you so much. With LMSA I managed to restore everything to stock and touch is working!
So I'm going to start from scratch and finally install Lineage.
Is is indicated to use the Lineage-Recovery, as the Lineage-Wiki says, or would it better to use TWRP?
TWRP gives me the option to flash from sd-card, which seems to me better than via sideload.
Click to expand...
Click to collapse
Glad your back up and running. Take a look in the lineage thread, but it does appear most people lean towards using twrp, shouldnt have an issue with either however.
digitaljeff said:
Glad your back up and running. Take a look in the lineage thread, but it does appear most people lean towards using twrp, shouldnt have an issue with either however.
Click to expand...
Click to collapse
I'm having a similar problem. At first touch was fubar but I was able to return to stock using LMSA and now touch works. I can load TWRP with fastboot and even install a custom ROM and TWRP, but installing any custom ROM results in a boot loop during the finding and installing updates part of the phone setup during first boot. I'm tried Evolution X which I was running previously(for about a month, and then a boot loop started yesterday), PixelOS 10, and AncientOS, but all result in the boot loop on first boot after connecting to wifi.
Fixed
I fixed this somehow by manually flashing the latest stock firmware to slot a, and then extracting the evolution x Rom and manually extracting the IMG files inside and manually fastboot flashing those to slot b. I then set b as the active slot and booted up, patched the boot image with magisk, flashed that, and everything works. Not sure why twrp wouldn't do the trick.
Finally had the time to install Lineage. Now everything works.
I followed the instructions someone posted in the [ROM][OFFICIAL] LineageOS 17.1 [nightlies]-thread and the instructions of the lineage-wiki:
1. fastboot boot TWRP
2. sideload the copy-partitions.zip from lineage-wiki
3. factory reset via TWRP (wipe cache, dalvik and data)
4. sideload lineage
5. reboot bootloader
6. fastboot boot TWRP
7. sideload magisk
8. reboot system
Had a little bootloop the first time rebooting the system, but that was because I forgot to wipe data-partition in step 3. Wiping data and rebooting did it for me.
So I have a working Lineage17.1 with root via Magisk.
Thank you for the help!
I had exactly the same problem like you had. Bought a brand new moto g7 plus and after recovery flash, Touchscreen was not working anymore. I could manage to go back to the bootloader, sideloaded TWRP, but side loading lineage worked for me then. It seemed to be stuck on 47 percent, but this seems to be a normal issue, the file was there and after installing, touchscreen worked normally.
Since I never had a problem with an update in years, and I'm also a very stupid person, I didn't backup my data before my latest custom rom (Pixel Experience Plus) update.
I got the notification for the November security patch updates, and I downloaded the zip as usual. For the actual installation I usually reboot my Mi 9T Pro into TWRP, flash both the OS update and Magisk, etc. and reboot. Everything seemed to go smoothly as usual: TWRP asked me to input my unlock sequence, then the usual stuff. Problem is, when I tapped 'Reboot system', it didn't reboot normally: it went into Recovery mode again, and from that moment on there's been no way to do otherwise. But now TWRP doesn't ask me the unlock sequence anymore and looks like there's no way to access the data. I tried injecting the recovery from fastboot, I wiped everything except internal storage (I don't give a damn about the OS anymore at this point); I also tried to reinstall the same old rom from OTG after wiping System, but nothing. Whatever I do, it always boots up in Recovery, and it doesn't ask me the unlock sequence. I know my stuff is still there, it's just that the contents of sdcard aren't accessible and look like random alphanumeric sequences from the TWRP file manager. And yes, that's the whole point of encryption, but I was used to TWRP asking me to unlock/decrypt so in the worst case scenario I would be able to access my data and copy via OTG. But now, with the system unable to boot and the recovery not decrypting my stuff, I'm starting to losing hope. I'm sure here on XDA there are much smarter / knowledgeable people than me, and I hope somebody can help me find a way to break the cycle and return in possession of the data that I stupidly didn't backup.
Any help would be greatly appreciated!
Try reflashing the boot image. Failing that, you should be able to ADB sideload the update via TWRP.
V0latyle said:
Try reflashing the boot image. Failing that, you should be able to ADB sideload the update via TWRP.
Click to expand...
Click to collapse
I think I tried both. I say 'I think' since my knowledge could fail here.
I tried re-flashing the TWRP img from OTG, nothing changed.
I successfully sideloaded the OS through ADB, but I'm still stuck.
Should I try both? (In which order)?
Thanks a lot.