Hello everyone, I'm having an issue with my phone where when I try to boot Into twrp-3.3.1-24-I01WD-Q-mauronofrio.img, It just crashes on the fastboot screen and I'm not able to interact with It at all. I tired Installing the stock ROM back onto and when I did, It wouldn't let me past the android set up menu.
The plan was to boot Into twrp-3.3.1-24-I01WD-Q-mauronofrio.img, flash the LineageOS ROM with all the extras, Then flash the Installer
If anyone knows how sort this out It would be a massive life saver, I've been at this for months.
Related
Hi guys! I am stuck with a dilemma if I should format my phone. I am quite aware of the dev tools as an IT student but this is the first time I've experienced this problem:
First I stupidly installed Nexus 5's Ambient Display mod without making a backup of the apk's affected resulting for I guess maybe a coincidence but I cannot install the 5.01 OTA as when I went back to the original recovery, I get the green Android logo and "Error" under.
So I flashed via the flash-all.bat the 5.01 stock firmware from Google but removed the userdata.img as I don't want to lose any of my files. It worked seamlessly. No lags, no crashes, bootloops, nothing.
Now, my problem is I want to get the Ambient Display 5.01 to run again, but this time when I tried installing CWM/TWRP via fastboot, it says okay then when I select recovery, it goes back to the Google logo then it boots normally.
What do you guys think is the problem? Should I re-flash the whole firmware? BTW I was able to root my phone the other day. So I don't know what's up. Any suggestions would be great. Thanks!
Remove the scripts in the ROM that flash stock recovery on boot. Then, fastboot flash the recovery of your choice.
http://forum.xda-developers.com/google-nexus-5/help/flash-recovery-stuck-dead-android-t2978052
The issue:
Phone is boot looping regardless of ROM. Additionally, if I use the torch, I have to reboot the phone to turn it off, and the camera is unable to load. -- The boot looping isn't always during the boot cycle, but sometimes a few minutes after the phone starts.
Backstory:
A few days ago my phone started to randomly boot loop. I was running one of the OTA of cm 12.x with TWRP at the time. After the issue started, I originally thought it was due to the upgrade to cm 12 and tried reverting to cm 11. This did not correct the issue, so I've tried a few other things since.
First I tried the method in this thread: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 however, while the batch job was running, the device became unresponsive. After an hour of waiting I unplugged the device which sort of hard bricked it.
To recover from this brick, I tried the method in this forum: https://forums.oneplus.net/threads/solution-recover-from-hard-bricked-oneplus-one.104943/
This allowed me to boot my phone into color OS with no apparent issues (I didn't test extensively). Following this, I tried using fastboot to put XNPH22R on it by flashing the files individually following the first guide.
I am currently left with XNPH22R, and the phone appeared to be working fine - the flashlight bug was fixed, and it wasn't boot looping. Unfortunately, while I was setting it up (I didn't do it at first because I wanted to test first), it began to boot loop again.
Does anyone have any advice? Additionally, while flashing the individual image files, I erased and formatted them first to give myself a clean install. Are there any other ones I may have missed that could be cleaned to fix this issue?
Thanks.
EDIT: Now my phone is freezing up in twrp as well. Additionally, the bootloader is locked and fastboot oem unlock is not unlocking it, and there is no OS because it froze during the flash from twrp.
Naturally the first I would ask you to do is:
1. Flash a Custom Recovery
2. Update firmwares to the latest ones (I guess May)
3. Update your ROM to latest Stock ROM or a Stable Custom ROM.
I have a strong feeling that mismatched firmware version could be causing this problem. I had a bootloop problem due to that.
Sent from my A0001 using XDA Free mobile app
tr.supradeep said:
Naturally the first I would ask you to do is:
1. Flash a Custom Recovery
2. Update firmwares to the latest ones (I guess May)
3. Update your ROM to latest Stock ROM or a Stable Custom ROM.
I have a strong feeling that mismatched firmware version could be causing this problem. I had a bootloop problem due to that.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I agree that it is likely a mismatched firmware given the issues I have seen with the torch and camera. However, I think I may have a misunderstanding of what the firmware is on Android. I thought it was the underlying linux kernel, which from what I'm seeing is the boot sector. If this is the case, wouldn't the fastboot flash boot boot.img replace the firmware with the appropriate version for the ROM? If not, can you please explain this further? Usually my experience with custom roms stops at loading a custom recovery and then simply flashing zip files from that.
Additionally, I have twrp as my recovery.
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 am struggling with my new Nord (AC2003), basically I have OEM unlocked fine, I have managed to boot TWRP etc... without issues and I can flash the phone this also works. I have tried the Lineage OS install flashing the IMG files, that left the biggest mess! TWRP couldn't even read my system partition anymore so I had to restore via EDL, I then tried PixysOS-v4.0.3 followed the instructions to the letter twice through, both times same result the phone boots straight to fastboot screen! If I hit start or tell it to boot normally it just does it again,
I have been on Samsung for a few years and to be honest haven't flashed an Android phone for about 4 years now but prior to that I was flashing custom ROMS nearly every day, so am no stranger to these processes albeit just a little rusty.
Anybody got any ideas what I could be doing wrong? Getting bored of going through system setup over and over again! All I want is a custom ROM with no Gapps in it
Thanks
My Phone was running Android 11 perfectly fine. Has been for about a week and a half, and I've decided that I don't like the OS. I was going to flash a custom ROM and went to create a nandroid before flashing. Literally all I did was boot into recovery and TWRP got stuck in a bootloop, the TWRP splash screen appears, crashes and then reappears about 2 seconds later, now when I try to boot back into system, TWRP appears instead and continues to bootloop. I can enter fastboot mode but that's all.
So far I've tried
Booting TWRP through fastboot. Failed another bootloop.
Rebooting through ADB. Boots into TWRP.
Rebooting Bootloader. Seems to do nothing.
Does anyone have any ideas on how to fix this ? It seems strange to me that something as simple as booting recovery could do this much harm. I also have a nandroid backup stored on the device from about a month ago, so the data loss wouldn't be THAT major, but I'm also not sure how I could access it without system or recovery access.
Hi , Which version of TWRP use? I think there is an update a new version TWRP 3.5.2 , Try to flash it. if its still not booting try to boot the original Boot of OOS11.
May be this threads will help you.
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
humood96 said:
Hi , Which version of TWRP use? I think there is an update a new version TWRP 3.5.2 , Try to flash it. if its still not booting try to boot the original Boot of OOS11.
May be this threads will help you.
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
Click to expand...
Click to collapse
New version does not work as well. Flash the stock boot img to get out of bootloop.
Jacobo123 said:
My Phone was running Android 11 perfectly fine. Has been for about a week and a half, and I've decided that I don't like the OS. I was going to flash a custom ROM and went to create a nandroid before flashing. Literally all I did was boot into recovery and TWRP got stuck in a bootloop, the TWRP splash screen appears, crashes and then reappears about 2 seconds later, now when I try to boot back into system, TWRP appears instead and continues to bootloop. I can enter fastboot mode but that's all.
So far I've tried
Booting TWRP through fastboot. Failed another bootloop.
Rebooting through ADB. Boots into TWRP.
Rebooting Bootloader. Seems to do nothing.
Does anyone have any ideas on how to fix this ? It seems strange to me that something as simple as booting recovery could do this much harm. I also have a nandroid backup stored on the device from about a month ago, so the data loss wouldn't be THAT major, but I'm also not sure how I could access it without system or recovery access.
Click to expand...
Click to collapse
Did your problem got solved?As i updated to A11 a few days ago and am facing the same problem since.Did flashing the new version of twrp worked for you?
Jacobo123 said:
My Phone was running Android 11 perfectly fine. Has been for about a week and a half, and I've decided that I don't like the OS. I was going to flash a custom ROM and went to create a nandroid before flashing. Literally all I did was boot into recovery and TWRP got stuck in a bootloop, the TWRP splash screen appears, crashes and then reappears about 2 seconds later, now when I try to boot back into system, TWRP appears instead and continues to bootloop. I can enter fastboot mode but that's all.
So far I've tried
Booting TWRP through fastboot. Failed another bootloop.
Rebooting through ADB. Boots into TWRP.
Rebooting Bootloader. Seems to do nothing.
Does anyone have any ideas on how to fix this ? It seems strange to me that something as simple as booting recovery could do this much harm. I also have a nandroid backup stored on the device from about a month ago, so the data loss wouldn't be THAT major, but I'm also not sure how I could access it without system or recovery access.
Click to expand...
Click to collapse
At first.- Stable TWRP is not available til now for OOS11
For TWRP to work your device must be decrypted.
This link will help you, will get full details
- https://forum.xda-developers.com/t/...-oneplus-7-pro.3931322/page-152#post-84727891
For more questions and help, please post in that twrp thread only
Regards