Hello,
My unrooted 1+1 got stuck in recovery mode after running out of battery. I have no bootloader and no access to internal memory. The only ADB command working is sideload. I have tried wiping my device and side loading more than 20 different builds from complete OTA cm11 to cm13, all goes well until 47% and then eventually exists, sometimes without any error but rebooting the device afterward always goes back to recovery mode. I also tried to sideload the google apps after it with the same result. forcing a reboot to the bootloader is showing me a quick error before going back to the recovery menu. Perhaps my method is correct but I'm unlucky to find the right builds. Googling this issue it seems that I'm not alone.
Related
Hi everyone,
So today I came home from a trip as my HTC One S, that for like.. 2 months was on CyanogenMOD 12, was working all perfectly fine, showed up that there's an update available (usual stuff, these updates come often). After it finished downloading the update, it restarted and installed it.. after that the only thing that was showing up was the loading screen from CM (pulsing logo). I waited for more than 1 hour and still nothing happened. So then I decided to open the recovery and install the update again. As I did that, I restarted the phone but still it stopped at the loading screen and nothing happened. After that I decided to Factory Reset everything and download the update from the official CM website.. I tried to apply it from the fastboot through the
Code:
./fastboot flash zip *file*
but it showed me an error: FAILED (remote: not allowed) After reading countless threads and forums about why this might happen and stuff like that I figured out that it might be caused by the adb and because my device is S-ON, and I can't make it S-OFF because adb doesn't see my phone connected to the computer (using a mac). And so I'm stuck in a situation I can't find answer to. I have to make the adb work because I can't do anything through the fastboot, it just doesn't want to copy the zip.
Also, yes:
I did unlocked the bootloader through the HTC's website
I have TWRP installed (v.2.8.1.1)
I tried to delete the cache/dalvik. Advanced wipe through the TWRP
It says "tempered" in the bootloader
I tried to switch the cable (as I read that that might work)
I tried to stop/restart the adb server – still nothing
Edit: I managed to make the adb work through recovery. I sideloaded CMod again and Gapps. I went all back to the original problem – booting animation. I still can't figure out how to make it work.
I've got quite a peculiar problem with my Nexus 5.
Last night, I left my phone on charge. It was working normally and the software was functional etc. However, once I woke up, the phone was constantly restarting itself, and wouldn't load past the boot animation. I tried to load up fastboot to enter the TWRP recovery, however, the phone froze on the load screen. I should also add that my custom boot animation was replaced by the CyanogenMod mascot.
This problem has never occurred before, and I really haven't got a clue how to fix it. I tried to use WugFresh's NRT to flash a factory image of Android 6, however, the command terminal indicated that each process had failed. This did not restore the phone to its original condition.
I should also point out that I have been running a CM 12.1 nightly, which has been very stable and I have been using this nightly, without major problems (bar the infrequent system UI crashes) for a couple of months. It is obviously rooted and I have a Nandroid backup, which I can't access for aforementioned reasons.
Please could you help me with resurrecting my phone? I would be happy to clarify and elaborate upon any point of information.
Kind regards,
Sami
Have you tried manually wiping cache in fastboot or manually flashing a stock ROM in fastboot mode?
audit13 said:
Have you tried manually wiping cache in fastboot or manually flashing a stock ROM in fastboot mode?
Click to expand...
Click to collapse
I actually have tried to flash stock Android ROMs, from KitKat to Marshmallow, however, this didn't work as there was a 'write failure' and CyanogenMod wasn't removed. I did erase the cache, but to no luck.
Sounds like the memory module on the phone is defective. I had a Nexus 5 that would constantly re-lock the bootloader after I reboot. I had another N5 where the bootloader remains unlocked and a full wipe in recovery would finish in about 3 seconds which is far too short.
I could only solve both problems by replacing the motherboard.
Hi,
I've got a Oneplus One that's stuck in a twrp recovery boot loop, and I'm wondering if anyone can help. I just had my screen replaced and when I got it back it was stuck in a twrp recovery bootloop, and I couldn't boot into fastboot mode- not via recovery, and not via holding the power/volume buttons down. By wiping the system in twrp I was able to get into fastboot mode, and flash the latest stock Cyanogen rom cm-13.1-ZNH2KAS254-bacon-signed-fastboot-d194f46bee. Everything booted up fine, and at that point the phone had been restored to stock. After that, I installed the latest cyanogenmod snapshot cm-13.0-20160419-SNAPSHOT-ZNH0EAO2O0-bacon, and everything booted up fine. Next I flashed the latest twrp 3.0.2-0 and rebooted the system. At that point everything seemed to be okay. I took the back cover off again to try and line up the speaker grill a little bit better, and now I'm stuck in a recovery bootloop again, except this time I can't get back to fastboot mode by wiping the system, and I don't have consistent internet access to research how to fix this (I'm posting this from the library). I was able to install the cm snapshot again via twrp thinking that it would just undo whatever it is that was causing the problem, but the phone still boots into twrp every time. Twrp does detect that I have indeed installed the zip, it's just I can't boot into anything other than twrp. Even when I plug the phone in powered off as if to charge it, it boots straight into recovery. I am able to put files on the phone via mtp, and it shows up under adb devices as serial# recovery when I mount mtp, so if there is a magic file that I can install, or an adb command that I can run, or if you know of the solution please lend me a helping hand.
Apparently the issue is that I wiped data via twrp instead of formatting data, and that wipe data is a feature of the stock recovery that twrp doesn't carry out, and as a result there is a command written somewhere on a partition that is forcing the phone into an endless twrp bootloop. Apparently this command <dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1> worked for a person that had a asus tf700 that was doing the same thing. How would I modify this command to get it to work on the OPO, or should it work as is?
This didn't work. I WAS able to use the colorOS flashing tool to install colorOS onto the phone, but it's still stuck in a recovery boot loop, and still can't get to fastboot, or get to the lock screen. I think that it may be a problem with the volume button since the colorOS boot seems to work, except for the recovery boot looping part. Any ideas?
I flashed TWRP through Minimal ADB and Fastboot. It said the install went fine. Now my phone is stuck in a bootloop at the "your device is booting now" screen. What do I do?
I had the same issue with twrp-3.2.1-1-berkeley.img. Using twrp-3.2.1-0-berkeley.img flashes fine but reboots into fastboot after about 8 seconds. Either I'm doing something incorrectly (??) or maybe a bit more work needs to be done with our twrp images.
EDIT: You need to use the "unofficial" TWRP image. Complete solution here.
I have made an OTA update yesterday to my rooted phone by following the usual steps installing magisk to inactive slot etc.. The only difference from other updates I did before this one was from android 10 to android 11. The phone worked fine, until today I wanted to check if TWRP is working and as soon I booted to it now I can't get out. It keeps flashing the twrp loading screen on and off. When I connect my phone to my PC it shows up in ADB in recovery mode when I try "adb reboot" it still boot to recovery when I do "adb reboot bootloader" it goes to fastboot, but no matter what I try I cant boot to the phone system.
UPDATE: I tried to use the patch and method from this post https://forums.oneplus.com/threads/rooted-oxygenos-11-on-my-oneplus-7-pro.1408175/#post-22986849 by Raven6681 then my phone went to stock recovery and I used wipe cache then my phone rebooted and only show a black screen. Then realized it keeps rebooting then black screen then reboot etc..
UPDATE 2: I tried to follow the previous step but now the phone didn't go to the recovery options as before and seems to be only in black screen. Tried to load in recovery and managed to then I used reset phone settings, but still nothing.
UPDATE 3: I tried to use the unpatched boot image from the first update as maybe some of the magisk modules are causing this issue, I tried clear cache and reset system settings and still nothing changed.
Probably an encryption issue. As twrp doesn't support encryption in A11. I don't know what's causing the black screen. The best way out is using msmdownload tool, I believe.
CodeRida said:
I have made an OTA update yesterday to my rooted phone by following the usual steps installing magisk to inactive slot etc.. The only difference from other updates I did before this one was from android 10 to android 11. The phone worked fine, until today I wanted to check if TWRP is working and as soon I booted to it now I can't get out. It keeps flashing the twrp loading screen on and off. When I connect my phone to my PC it shows up in ADB in recovery mode when I try "adb reboot" it still boot to recovery when I do "adb reboot bootloader" it goes to fastboot, but no matter what I try I cant boot to the phone system.
UPDATE: I tried to use the patch and method from this post https://forums.oneplus.com/threads/rooted-oxygenos-11-on-my-oneplus-7-pro.1408175/#post-22986849 by Raven6681 then my phone went to stock recovery and I used wipe cache then my phone rebooted and only show a black screen. Then realized it keeps rebooting then black screen then reboot etc..
UPDATE 2: I tried to follow the previous step but now the phone didn't go to the recovery options as before and seems to be only in black screen. Tried to load in recovery and managed to then I used reset phone settings, but still nothing.
UPDATE 3: I tried to use the unpatched boot image from the first update as maybe some of the magisk modules are causing this issue, I tried clear cache and reset system settings and still nothing changed.
Click to expand...
Click to collapse
in that case reflash twrp,root and the os you were using(in the order you did it the first time and, when you get your next ota update
extract it and edit to remove code which makes it look for stock recovery
select all the decompressed files and compress to ota zip file again
then in update area choose local update and use the file you just edited