Hello everyone ... I think I dun goofed, but perhaps someone knows something that I don't :\
So today I wanted to switch to a new Custom ROM... standard procedure I guess. Without doing anything, btw, apart from using my phone, I got several random reboots into bootloop today, especially while texting, which I didn't get at all, but didn't mind because they ceased after several times.
So I get home and get cracking ... backup my Contacts, try to make a NANDROID backup, which gets stuck while backing up /data ... which I didn't get, but unfortunately CWM didn't wanna react after this, so I had to hard reset, and lookie lookie, it rebooted into Android. Now, however, nothing works.
I put in the battery, the bootloop begins, not even a press of the Power Button is needed, I press the combination for Download Mode, actually SEE THE WARNING SCREEN, can't however proceed because the reboot begins immediately after, and CWM won't load either
Does this mean I'm pretty much f'd in the a?
EDIT: Welp, seems like removing the battery right when the loop starts makes it so that I have to press the power button again which makes me able to access both Android and CWM, I literally have no clue how this could have come.
Related
Hi all my phone has some how only boots in Safe Mode for some reason. I'm running CM7 and whenever I boot my phone it doesn't go past the LG logo unless I press a button. However, whenever I press a button it takes me straight to safe mode. I've used Xiaona custom recovery to fix the boot load but that doesn't work either. I'm quite confused and discouraged because I've tried everything I can think of to fix this. None of my buttons are stuck IMO. I've search endlessly for solutions but have forum none, for most people, rebooting their phone takes them out of safe mode, that unfortunately isn't the case for me.
I've spent probably 8+ hours fooling around, I only got this phone yesterday so you can just imagine going from a beginner who knows nothing to having to use ADB commands and stuff to try and fix their phone. I'm finally ready to ask or beg for help. Please help me
Just wanted to say I've fixed this issue by holding down ALL 4 of the face keys on the phone while it was booting up. You have to hold them down until the phone is completely booted up. However, this is the only way I know how to fix it, unfortunately I have to do this everytime I boot my phone but I don't turn my phone off much so I'm happy as long as it's working.
I'm absolutely new to the custom rom scene and I figured I would root my phone and install the rom from here:
http://forum.xda-developers.com/showthread.php?t=1759642
It went perfectly fine and I started the like the idea of being to install what I want onto a phone, so I decided to make the jump to install CM10.
I ran a nandroid + TB backup and copied the backup to my computer. Then I dragged my CM10 rom (from http://www.droidhive.com/forums/index.php?/topic/1470-cm10-unofficial-for-d2vzw/) to the root directory of my phone. Then I ran rom manager to install cm10. The phone reboots into recovery but gets stuck on recovery. It will constantly reboot and once it reaches recovery, the loading bar with the picture of the green android robot in the background loads about 20-25% of the way, and then the phone vibrates and acts as though I just boot it up (and this process cycles).
I can't get it to ever get past this 20-25% mark and it isn't recognized by my computer to flash it back to stock and I can't do a nandroid restore since I can't get past this state.
Is my phone bricked and if so/not so, what should I do?
redxv said:
I'm absolutely new to the custom rom scene and I figured I would root my phone and install the rom from here:
http://forum.xda-developers.com/showthread.php?t=1759642
It went perfectly fine and I started the like the idea of being to install what I want onto a phone, so I decided to make the jump to install CM10.
I ran a nandroid + TB backup and copied the backup to my computer. Then I dragged my CM10 rom (from http://www.droidhive.com/forums/index.php?/topic/1470-cm10-unofficial-for-d2vzw/) to the root directory of my phone. Then I ran rom manager to install cm10. The phone reboots into recovery but gets stuck on recovery. It will constantly reboot and once it reaches recovery, the loading bar with the picture of the green android robot in the background loads about 20-25% of the way, and then the phone vibrates and acts as though I just boot it up (and this process cycles).
I can't get it to ever get past this 20-25% mark and it isn't recognized by my computer to flash it back to stock and I can't do a nandroid restore since I can't get past this state.
Is my phone bricked and if so/not so, what should I do?
Click to expand...
Click to collapse
Hmm honestly the easiest way out of this is just to flash the stock rom of your carrier through odin (download mode and flash), easy fix. You could try messing around with the recovery and whatnot, ie try flashing a new recovery through adb somehow, but easiest and the most least painful way seems to be to just odin back to stock and try again. and also, i dont get why people use rom manager, heard too many horror brick stories about that. Just adb the recovery to the phone and flash the zip. Why even bother with rom manager.
good luck, hope i helped :good:
I can't get my computer to recognize my phone to use odin / adb.
redxv said:
I can't get my computer to recognize my phone to use odin / adb.
Click to expand...
Click to collapse
Did you put your phone in download mode? turn off, and then hold home vol down and power at same time.
Never mind..
I was asking same thing like Unleashed12
unleashed12 said:
Did you put your phone in download mode? turn off, and then hold home vol down and power at same time.
Click to expand...
Click to collapse
Like I said, when I book into recovery/download mode, it just boot cycles.
That is: phone turns on. Samsung boot screen, then android robot screen, loading bar goes about 1/4 of the way, then phone goes black, and starts at samsung boot screen again.
redxv said:
Like I said, when I book into recovery/download mode, it just boot cycles.
That is: phone turns on. Samsung boot screen, then android robot screen, loading bar goes about 1/4 of the way, then phone goes black, and starts at samsung boot screen again.
Click to expand...
Click to collapse
Sounds like you haven't actually entered the download mode... power off> hold at same time power, home and vol down... keep holding until the phone turns back on. you should enter download then.
I personally feel like you just have a dirty install without knowing more. Once you enter recovery I'd just data reset, cache reset, dalvik reset and reflash same rom... or a backup
Yeah, my bad. I didn't hold it down long enough. I'm such a noob.
Don't forget to hit thanks for those who helped you...
Sent from my SAMSUNG Captivate™ Glide i927
Aquethys said:
Don't forget to hit thanks for those who helped you...
Sent from my SAMSUNG Captivate™ Glide i927
Click to expand...
Click to collapse
haha Thanks for that!
well my phone is now stuck on the htc screen... help please
I was running meanrom 3.0 then dirty flashed 3.9. My phone would turn off randomly so i restored it to 3.0. Then my text messages wouldnt work couldnt send or receive. So then i full wiped, restored and still no text. Then I full wiped and hit reboot system. And now it is stuck. I guess it is stuck because i didnt restore or install a rom? I cant even get to the bootloader. So is this phone a paperweight now?
Hold power down, this will cause a simulated battery pull, the phone will turn off, wait a second or two then press and hold power button and volume down and you will boot to the boot loader. Be very careful next time
Edit so long as your phone responds there is almost always a way to fix it, you only worry when phone stops responding (screen off won't charge won't turn on)
I wish more people would read my guide I included problems (even this exact one) to help people avoid them
ok got to bootloader. THANKS
No problem I'm glad I helped.
Note: This exact problem and many others are in the troubleshooting section of my guide. (Sorry if I don't advertise no one will use it lol)
Yep.... you wiped the ROM and then tried to boot nothing.
yeah....this is clearly covered in my guide...lol
I have a Tmobile HTC One M7 that I paid $300 for. It was awesome! However, I wanted to root it. So I successfully unlocked the bootloader, installed TWRP and then proceeded to attempt to root. Something went wrong and now this thing is useless! I cannot tell you where it went wrong because when the first sign of trouble appeared I started doing all kinds of **** to try and fix it, none of which worked and I have lost track of what I did in the process of trying to root and then subsequently trying to fix. I know there were some wipe cache, wipe dalvik cache, install zip from SD, I may have even tried to flash a custom ROM without the thing being rooted. I have been reading for days, trying this, trying that to no avail. The phone is brand new, without a scratch. It will power up like normal, but when it gets to the lock screen where you swipe the little lock in the bottom tray to use the phone it will not respond at all! It recognizes the network because it is displayed in the notifications bar up top, it can see the signal strength, it knows what time it is, it knows what the date is, but it will not get past the damn lock screen. ADB sideload works. I was able to push a zip and flashed it, even said android is upgrading when I rebooted, but it did not solve my problem. It will not power off, but when I hold the power button down, to turn it off the back arrow < and home symbol flash and after about 10 seconds a dialog box pops up that says to restart your phone continue to press and hold the power button and starts a countdown. Once the countdown gets to zero it restarts. If I hold the volume down button while doing this it will go into the boatloader and I can get into recovery. Apparently there is no backup to restore because when I try a restore I get the same exact same thing. I thought I had done one, I must have erased it somehow. I have been trying to resolve this for weeks now and am at my wits end. Any suggestions please !?!? Will anyone on this forum take it if I ship to them and fix for a fee? Otherwise this things going in the trash.
How the problem occurred
So a year or two ago I bought a Jiayu G4A/T/Whatever they're calling it and safely got it here. I've used the stock ROM for a bit but I wanted to get rid of the bloatware that was still on it, so I eventually ended up with a properly rooted phone with a ROM from Jiayu.es (Everything worked, have ClockworkMod as recovery, accessible via Mobileuncle Tools), which was essentially a stock Kitkat rom made to work for the phone. Now I got sick of the ROM and recently saw the new EMUI version on Huawei's P8 Lite, so I figured I'd look around for a tailored ROM running that, and ended up at "jiayu-emui-3-0-stable" from Needrom.
What I did
1. I downloaded a ROM from Needrom with identifier "jiayu-emui-3-0-stable" (I can't post external links)
2. Backed up my important files following a guide from androidcentral titled "[Guide] How to Backup and Restore Apps and Data when installing new ROMs" that I can't link,and did a full backup using CWM
3. Placed the ZIP on my internal SD card, went into recovery, wiped data/cache (not dalvik, since it wasn't described in the instructions, I think this might be a probable cause) and installed the new ROM from ZIP
4. Rebooted the phone and now it's stuck in the boot loop I mentioned.
What the problem is
Bootloops aren't that much of a problem usually, except this one is... I can't get into recovery mode. From there on it'd be cake, since I made the right preparations, but I can't get into it. While connected to my PC it keeps powering on, showing a splash screen from Jiayu.es briefly (which shouldn't be present anymore) and powering off after 10 seconds, only to come back to the splash screen.
What I've tried
I've unplugged it, removed the battery, waited to get a full power cycle and tried to hold my buttons in these combinations: [power button + volume up], [power button + volume down] - but neither work. It just keeps going with the boot loop. I can succesfully power it down, and when I plug it in from there it shows the low battery image. At the moment of seeing that I thought I could connect to it using ADB / Fastboot, but no luck there either. It keeps saying no devices found, and with fastboot it keeps on <waiting for device>.
My questions
What exactly can I do if there is no way for me to get into recovery mode? Are there any alternatives? How can I get my device to be recognized by ADB? Is that even possible? Why is this bootloop any different from others?
Update from the massive Q&A thread:
ZipAddict said:
Is it booting up on its own too after being off? This happened to wifes phone and it turned out the power button was stuck. I took a pencil and hit the power button with the eraser a few times and it worked then. Her case mustve dislogded it. I will keep my fingers crossed for u. If not send me a private message and i will look for an answer tomorrow and get back with u
Click to expand...
Click to collapse
Thank you for the reply!
Yes, it does. I took the battery out and let it lay disassembled for a night, after which I cleaned it a little and re-inserted the battery. With the case back on, nothing happened, so the power button wasn't stuck for sure. When I powered it back on with the power button (no USB attached) it showed the emblem for ~8 seconds and powered off. It then buzzes to show it's powered on again and up comes the splash screen again. Could it be that the ROM was just a rebooting falsehood? Why would it disallow me getting into recovery mode? I really hope there is something that can still force the device into recovery mode / interact with it somehow while in this state.
Oh, I also tried to see if the volume down button was broken but all the contacts seem intact, plus, they worked an hour before I started switching roms.