[Q] Nexus 5 MultiROM bricked? phone - Will not load out of bootloader/recovery - Android Q&A, Help & Troubleshooting

When i first installed MultiROM on Cyanogenmod, I would have to go through the bootloader to get anything but a black screen. From there, I could select Start, and then usually it would work. A pain, but it worked.
I just used MultiROM to install Android L preview and when it told me to restart, I got the same black screen I had gotten before. No biggie - I've been here before. When I went through the bootloader, I just went straight back to the black screen. I repeated the process a few times before I gave up.
I can still load into the MultiROM recovery menu, but the phone just wont show up in Android File Transfer or ADB. 
If possible, I'd like to keep the pictures that are on the phone, but if not, it's fine. I can't flash a new ROM because the phone wont show up in ADB.
It seems that there is a factory reset on the MultiROM recovery menu - does this work like a regular factory reset where it would reset to a version of cyanogenmod?
Any advice would be GREATLY appreciated.

Related

[Q] Stuck in recovery boot loop midflash upgrading to KitKat 4.4.2 on dtmo SGS3

My device details: SGS3 T999, rooted, running Jellybean 4.3 on a liquid smooth ROM. Its a year old and has been a solid performer up until now.
My device is stuck in a cycle where it gives a quick vibrate, then SGS3 splash screen with white letters, then black screen, then tiny blue "Recovery booting..." words in upper left of screen, then black screen with couple vibrations, and around and around it goes in the same repeating cycle.
Just before it started I had taken the following actions: Dumped the following 2 files onto my EXTSD card (cm-11-20131217-NIGHTLY-d2tmo.zip, gapps-kk-20131119.zip) from my PC, booted phone into recovery mode using TWRP, did a factory reset wipe (success), cache wipe (success), dalvik cache wipe (success), flashed the NIGHTLY file (failed), flashed the gapps file (failed). At this point I should have sought some support. Fool! I next did a reboot step still in recovery mode. Without the reboot happening a message came up stating Superuser permission had been broken (the best I can remember) and the option to have TWRP repair the permission. I opted "yes" to repair. Then the loop started that I can't escape.
I have pulled the battery multiple times, tried a regular boot up, tried a recovery boot up (up volume+power+home) dropping the home button after a few seconds. Nothing is working. Prior to the above steps I backed up everything on the device. So I have backups to use if it can be done. My best guess is that I failed to update my CyanogenMod or TWRP to the very latest versions and it caused this hang up. Otherwise, I don't know what to do and need any help I can get.
Has anyone had this issue or heard of anyone who has and have any helpful suggestions, tips, ideas, etc..?
Thank you in advance. This is my first XDA post. Please forgive and offer tips if this thread needs any scrubbing.
I've had a few similar events for a few different reasons.
I would suggest booting into recovery but it seems you have tried that already.
If the device is plugged into a wall or pc, unplugg it, that has seemed to cause and fix boot issues for me before.
Other than that, I dunno, if you can't get to recovery or fastboot, I dunno...

[Q] XT910 stuck on Cm11 blue logo

So I have a droid razr that has (Safestrap 3.73 with TWRP 2.7.0.0)
I flashed a custom rom onto it; a 4.4.4 version and it was working fine for a few days. The phone died overnight, and I charged it to full battery yesterday. After doing so it will no longer boot to the operating system.
The phone can boot to recovery, and the options can be fiddled with there, however I cannot get the phone to get past the blue logo with the spinning arrows. It will stay there indefinitely...
I do not have an external SD card for the phone, and my pc will not recognize the phone in spite of having the drivers for the phone installed before hand. I have tried to wipe/factory reset multiple times and yet it will always get stuck at the blue logo. The option for the stock rom is greyed out in the boot section, and I really need my phone to get some functionality back to it.
I do not have any other image for recovery installed on the phone, only the current rom and gapps are on the install section. I have wiped and tried to reflash but I always get the same result.
Where do I proceed from here? I am very confused and could use some help as to what to do to restore functionality... personally id prefer to go back to stock image but am having a hard time locating the us verizon factory image online, not that I can even get it onto the phone.

Disabled Encryption now just boot look in recovery

Hey Guys,
So i used the nexus toolkit to disable encryption. All went well for the process itself but after it told me rebooting tablet, all i get it a flashing TWRP screen (as shown in video below). If I try to long press power, i see the google logo but it basically just boots back into TWRP and all it does is flash that screen. I'm sort of new to Nexus devices, what could I have done wrong? And how could I get out of this?
https://youtu.be/zbSwUAn_ylU
EDIT: I restored back to stock. I will wait to try this again when 5.1 will come out

[Q] Factory reset from settings --> boot loop

My daughter's i9300 started resetting itself without control. Today it got unmanageable and a successful boot became impossible.
Looking around, I found a thread suggesting that the power button switch is the culprit.
Indeed, after removing the switch, everything worked fine. Had major issues starting the phone, but eventually it started, so I was good to go.
I rooted it, installed latest TWRP and Resurrection ROM. The ROM was a random pick more or less, I had it on my LG G3 at some point and I wanted lollipop.
All fine and dandy, I was able to get into the phone. However, data wasn't wiped even though I selected it for wiping in recovery (probably didn't select the right thing...). So I went to settings and chose factory reset with wiping all data.
This lead to phone rebooting to recovery, but TWRP logo just flashes every few seconds without ever getting to recovery itself.
How can I make this phone work again? Any ideas?
Boot into download mode then flash a full stock rom with Odin. If that works then factory reset in recovery before testing.
You may find the firmware won't flash, as it sounds like your nand memory is worn.

I've bricked my T820

Was trying a factory reset with the idea that I'd give my Tab s3 to my wife upon receiving my S4.
The s3 was rooted but had the stock ROM.
I booted into recovery (TWRP) and did a wipe to factory reset. I had used TWRP a lot and didn't take my time. Just as I was moving the slider i read something like "sure you want to do this you have no OS installed." Too late.
Now it is stuck on the splash screen. I can't even turn it off.
Thoughts?
Thanks
4Nails said:
Was trying a factory reset with the idea that I'd give my Tab s3 to my wife upon receiving my S4.
The s3 was rooted but had the stock ROM.
I booted into recovery (TWRP) and did a wipe to factory reset. I had used TWRP a lot and didn't take my time. Just as I was moving the slider i read something like "sure you want to do this you have no OS installed." Too late.
Now it is stuck on the splash screen. I can't even turn it off.
Thoughts?
Thanks
Click to expand...
Click to collapse
You can either flash stock firmware from download mode (vol down+home+power). You can force reboot with this combination even if it's stuck at samsung logo (after screen gets dark, keep pressing them to get to download mode). Then you can flash with Odin a stock samsung firmware.
The other option is to use this rom https://forum.xda-developers.com/galaxy-tab-s3/development/rom-sm-t820-tweaked-t3659433.
Copy it to the microsd, boot to recovery (in this case you have to use the same 3 button combination, but as soon as the screen goes off, you leave the vol down and press vol up along home and power buttons.
That would take you to TWRP and then you could flash that rom.
The first option is the natural one but both should work.
Also, for the second option you need the actual bootloader to match the custom rom.
So if you're in Nougat, flash the Nougat rom. The same for Oreo.
Thanks. Worked perfectly.

Categories

Resources