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.
Related
Hi everyone,
I am stock at boot on my atrix 4g, it keeps rebooting when it reaches the home screen. This happened after I tried to change the font with motomizer app.
The phone is rooted, using stock motoblur 4.9.12(I am not sure of version maybe 4.5.12) I have cwm recovery up to date but android recovery is unresponsive, I am not familiar with the fastboot and rsd lite (which I already bricked one before with) I booted in to recovery several times with and without sd card it just doesn't go after loading the adroid man and the warning sign. There is no progress bar it stays in that state forever.
Does anyone has any idea what might be the problem here, any help would be appreciated to get it working again.
Thank you.
I attempted to flash MIUI.us V4 2.6.8 Atrix ByTeamMotoTegra today, and was almost successful, but I found out that I shouldn't have wiped the phone before flashing. I lost the touch functionality, and couldn't select my language. I flashed my old ROM (Neutrino) to try to flash back to MIUI, but still could not seem to get the touch funcationality.
After a few times of taking out the battery and trying to get the MIUI ROM working, I ran into a boot loop. The screen will not go past the screen with the red logo, no matter what I do. If I hold the volume up/down buttons, "starting RSD protocol support" appears, but nothing else happens. The phone just keeps turning off, then returning to the screen with the red logo. Any ideas on how to get past this screen?
i have a similar problem, i rooted and unlocked a friend atrix today on 2.3.6 version 4.5.141
it went fine and booted normally. i then went into cwm and made a mistake by not making a backup, cleared data cache and dalvik then proceeded to flash aokp. it booted but didnt go past the motorola dual core screen while still displaying unlocked. i can still go to fastboot and even into cwm as i have attempted to flash other roms after clearing all things out again but nothing is going past the boot screen.
any suggestions?
I can scroll through the other CWM menu options, but I can't boot up or anything else. Anytime I select one of the options, it will either just restart and go back to the red logo screen, or say I don't have enough battery life to flash. My battery is now completely dead and doesn't seem to be charging at all, even though it's been plugged in all night.
I need help. I came across a Galaxy Tab 2 10.1" WIFI only GT-P7510 recently and was trying to flash AOKP 4.2.2 to it after rooting it with Odin. I was originally on 4.0.1. Now I can't get it past the boot screen, the colorful X. I can still access CWM(I'm using 5.8.3 I believe). I've tried multiple times to reflash the recommended US Bootloader and always wipe the data/cache/dalvik cache. To no avail. I stupidly didn't create a backup of the original OS image; therefore, I can't put another OS on it. There's no external SD slot on the tablet and can't get the tab to boot to use the usb cable to do it. I also have the option to get to download mode, but when it asks me if I'm sure whether or not I'm sure I want to go into download mode, I click the volume up button, it doesn't work. It just shuts back off. I can still get into the recovery, but that doesn't help if i can't put any zip files on it to reflash to stock or another rom. the tablet just stays on the boot screen until it dies. I've tried a lot of google searches but nothing directly helps me. I really hope someone here can help.
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...
This is the problem I am having with my Samsung Galaxy Note 3 (SM-N900P). This problem just popped up out of the blue on a stock ROM a few days ago and nothing I have tried has gotten close to fixing the issue
Description:
a) The boot sequence repeats in a loop with no more sound. The phone would reboot at the Sprint splash screen
What I've done so far:
a) Pulled the battery and depleted the capacitors
b) Installed TWRP and did a complete wipe
c) Tried installing a custom ROM to see if the issue persisted. ROMs failed to install as /system was being sketchy (at times it was reporting 0MB for partition and then an actual value after repair). When I managed to get a ROM to install still stuck in the boot loop
d) Used Odin to do a full restore to a stock NC5 ROM. The phone got up to initial configuration page and then rebooted, now only gets to the Samsung splash screen before rebooting
Items that I can get into:
Recovery mode
Download mode
I have a 30 second video of it rebooting but cannot post it currently due to the forum rules
Question:
Is this issue fixable or is it a sign of internal memory failure?
Try an older version of TWRP, i.e. 2.8.5.0
Or, try a different recovery.
I'm not sure that it will work, but it's worth a try.
Good luck!
Are you doing it this way?
http://forum.xda-developers.com/showthread.php?t=3069667
rbeavers said:
Are you doing it this way?
http://forum.xda-developers.com/showthread.php?t=3069667
Click to expand...
Click to collapse
I didn't notice that but I just installed TWRP 2.8.0.0 through Odin (like a few minutes ago). Phone actually managed to get to the stock recovery image config screen and was working as long as the cable was still attached to the computer.
As soon as I removed the cable it went straight back to the boot loop
SubRyan said:
I didn't notice that but I just installed TWRP 2.8.0.0 through Odin (like a few minutes ago). Phone actually managed to get to the stock recovery image config screen and was working as long as the cable was still attached to the computer.
As soon as I removed the cable it went straight back to the boot loop
Click to expand...
Click to collapse
Here is what you need to do. First pull battery, reinstall. If you can boot into twrp recovery, fine wipe everything i.e. caches, system, data, etc. If you are on a stock recovery do a factory reset. Pull battery, reinstall and boot into download mode.
NOW let's go to work. First use odin to flash stock NC5 tar. Chances are it will bootloop, STOP !!!! don't panic. Just reflash with odin again. The second time it should take. Remember that your device is setting up for first time use. This will take 3-5 minutes, sitting at the Samsung logo. Since didn't list the most important thing which is what OS you where on where the device Borked, or what you where doing with the device when it Borked. I'm going to assume it was on 4.4.4 and you tried to downgrade to 4.4.2 NC5. In which case a bootloop on the first bootup after a downgrade is normal, you have to flash twice to reset the bootloader. For more info click on rom flashing basics in my signature. Enjoy !!!
Problem solved. I started getting suspicious when the phone would boot up with the charging cable attached to the computer today
The issue was an aftermarket Mugen Power battery that developed a fault. Put the stock battery back in and problem resolved
Thanks for the help guys