Please someone help me or tell me who I can PM to help please.
Yesterday my razR M was just randomly rebooting, it stop doing this after about 5 reboots. I then proceeded to fully charge my phone twice to do the radiocomm edit and root, using DROID RAZR M Utility 1.20 since i'm on 4.1.2 *I did not factory reset*, the phone so that the battery wouldn't die while doing either and mess up the phone. I was trying to do the entitlement edit with all free file managers with root permissions which didn't work and I realized my phone was freezing while doing simple tasks (during boot animation, inputting password to unlock phone, switching between homescreens and opening app drawer) and rebooting.
It wasn't turning on or showing any indication of being plugged in, but while I was writing this it just magically went to the battery percentage indicator and I was able to turn it on and after about 20 seconds of being booted the led indicator is flashing green again.
I can't have this happen next week when I'm on my trip, I won't have the time and my access to computers and internet will be limited. If anyone knows what could be causing this and or how to fix it PLEASE TELL ME
Update (3:25 AM): IT HAPPENED AGAIN, ready to cry want to try to flash back to stock but don't know how
Update #2 (4:13AM): So after a lot of button pressing I got it stuck on the red m then eventually into the bootloader; saw that the random reboots is not unusual for razr hd/maxx hd users on 4.1.2 with the only way to fix being to flash to CM10. Also realized that i'm not the only one whose phone requires a soft reset to charge/boot, no longer contemplating flashing back to stock seeing as i'll probably still have the reboots
ccdsatt said:
Please someone help me or tell me who I can PM to help please.
Yesterday my razR M was just randomly rebooting, it stop doing this after about 5 reboots. I then proceeded to fully charge my phone twice to do the radiocomm edit and root, using DROID RAZR M Utility 1.20 since i'm on 4.1.2 *I did not factory reset*, the phone so that the battery wouldn't die while doing either and mess up the phone. I was trying to do the entitlement edit with all free file managers with root permissions which didn't work and I realized my phone was freezing while doing simple tasks (during boot animation, inputting password to unlock phone, switching between homescreens and opening app drawer) and rebooting.
It wasn't turning on or showing any indication of being plugged in, but while I was writing this it just magically went to the battery percentage indicator and I was able to turn it on and after about 20 seconds of being booted the led indicator is flashing green again.
I can't have this happen next week when I'm on my trip, I won't have the time and my access to computers and internet will be limited. If anyone knows what could be causing this and or how to fix it PLEASE TELL ME
Update (3:25 AM): IT HAPPENED AGAIN, ready to cry want to try to flash back to stock but don't know how
Update #2 (4:13AM): So after a lot of button pressing I got it stuck on the red m then eventually into the bootloader; saw that the random reboots is not unusual for razr hd/maxx hd users on 4.1.2 with the only way to fix being to flash to CM10. Also realized that i'm not the only one whose phone requires a soft reset to charge/boot, no longer contemplating flashing back to stock seeing as i'll probably still have the reboots
Click to expand...
Click to collapse
not sure if your situation has been resolved, but it appears that the battery just drained all the down. from that point, you need to plug in your phone (into an outlet, not computer), and leave it alone for a good 30 minutes (don't even look at it).
from that point, you should be able to enter the Rom by powering up or recovery via volume up + volume down + power.
if you are still having troubles, you might be best to simply perform a hard reset (I think you can do that from the stock recovery menu).
after you are able to do that, I would suggest to root, unlock bootloader, install TWRP. then setup your phone settings to your liking, then go back into recovery and make a backup. i have soft-bricked my phone several times, and entering TWRP recovery and restoring my previous setup has helped every time.
Its OK now
jco23 said:
not sure if your situation has been resolved, but it appears that the battery just drained all the down. from that point, you need to plug in your phone (into an outlet, not computer), and leave it alone for a good 30 minutes (don't even look at it).
from that point, you should be able to enter the Rom by powering up or recovery via volume up + volume down + power.
if you are still having troubles, you might be best to simply perform a hard reset (I think you can do that from the stock recovery menu).
after you are able to do that, I would suggest to root, unlock bootloader, install TWRP. then setup your phone settings to your liking, then go back into recovery and make a backup. i have soft-bricked my phone several times, and entering TWRP recovery and restoring my previous setup has helped every time.
Click to expand...
Click to collapse
My phone was always 100% percent charged as I wanted to do stuff with the utility. After getting it into safemode, where it still froze and rebooted twice each time I booted into the mode, I got to power off then turn off then back on the regular way and left it on and has been fine since then. I currently have safestrap and cm10 zip on the phone in the event it acts up again. I backed up using safestrap like suggested. I haven't unlocked the bootloader yet, I have the app installed though, as I saw something from one of the devs for my previous moto device that said that if your bootloader is unlocked and we get another OTA and install* it our phones could get messed up.
*I know I can just install a stock 4.2 ROM*
ccdsatt said:
My phone was always 100% percent charged as I wanted to do stuff with the utility. After getting it into safemode, where it still froze and rebooted twice each time I booted into the mode, I got to power off then turn off then back on the regular way and left it on and has been fine since then. I currently have safestrap and cm10 zip on the phone in the event it acts up again. I backed up using safestrap like suggested. I haven't unlocked the bootloader yet, I have the app installed though, as I saw something from one of the devs for my previous moto device that said that if your bootloader is unlocked and we get another OTA and install* it our phones could get messed up.
*I know I can just install a stock 4.2 ROM*
Click to expand...
Click to collapse
well, most folks are going via the TWRP recovery route now (and I believe that all custom ROMs going forward will be flashable this way only, and not SS).
you will find that using TWRP is much easier than SS
jco23 said:
well, most folks are going via the TWRP recovery route now (and I believe that all custom ROMs going forward will be flashable this way only, and not SS).
you will find that using TWRP is much easier than SS
Click to expand...
Click to collapse
I realized that while looking at roms this afternoon. Before I go down the custom route though do you know if it affects the usage of gsm there are no CDMA carriers in Jamaica so I can't flash to anything?
Sent from my XT907 using xda app-developers app
ccdsatt said:
I realized that while looking at roms this afternoon. Before I go down the custom route though do you know if it affects the usage of gsm there are no CDMA carriers in Jamaica so I can't flash to anything?
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Most of the ROMs need a gsmfix zip flashed, but they'll work on GSM with that
Sent from my Nexus 7 using Tapatalk HD
Related
Ok, so I was playing around with the new Root Tools app and made a few, what I thought were safe, tweeks to the system and rebooted the phone. It gets past the M screen, runs the boot animation and then starts the boot animation again. No way out except to pull the battery.
How can I get it out of this endless bootloop? If I have to factory reset and start again from scratch, so be it. I would just like to know how.
I've tried holding down different button combinations on boot but haven't come up with the right sequence I guess.
I've also tried pulling the battery as the animation starts, then putting it back in and rebooting which is supposed to call up the recovery mode, but it doesn't. I'm not sure what to try next? I wish these things had a reset button
It's a Droid 2 Rooted with the stock rom running Froyo 2.2. I have the Bootstrap recovery loaded and did a backup with the clockwork recovery. I also have, and use, Titanium Backup Pro for Root.
After bootlooping pull the battery and put it back in. Then plug the droid 2 in with the cable either wall or USB will work. Then turn it on and it should get you recovery. The phone has to be completely off when you plug it in though.
Sent from my DROID2 using XDA App
EDIT: I tested it and USB won't work (at least for me) better off just using the wall plug.
Thanks, but that not working either. When I plug in the cable after the battery pull it starts up automatically and goes to the battery charge screen. I then shut it off and start it back up with no battery but plugged in and it goes right back into the boot loop after the M screen.
The batter charge screen is what you want. Just press the power button after you get the charge screen and you'll be booted into clockwork.
But in order to factory reset from a bootloop you have to flash an .sbf theres a few different tutorials. One in Windows, Another in linux/mac, and another in linux but for windows machines through an Ubuntu livecd(that I made).
Oh, OK I thought it was going to go right into recovery mode. Good to know.
I finally figured out how to get into the stock recovery and bootloader, so I tried to run the stock restore but after it wiped the data, it couldn't find the recovery file! So then I read in another post about using RSDlight 4.9 to do an sdf restore so I used that method. Of course while it was flashing I did come across your Ubuntu method and that does look like it would be a simpler process. I'm going make one of those CD's to have for next time.
Anyway, I was able to get it back to stock. It looks like most of my stuff is still on the SD card, so that's a bonus! I'll have to re-root before I can restore everything via Titanium, but that's going to be tomorrow's project. As for now just happy to to have my phone back. Especially before the wife (who has been telling me for weeks to stop F'in with it) found out .
I really appreciate that you took the time to help, thanks again!
No problem.
Could you change your Thread title to include [SOLVED]. Thanks
Can you please explain to me how you fixed this problem? I am currently having this problem now.
Please do not open/post in multiple threads for the same issue. This is a waste of time as we can see you have an open thread. Please reply to my response in your original thread for further assistance. (http://forum.xda-developers.com/showthread.php?t=824254)
newk8600 said:
Could you change your Thread title to include [SOLVED]. Thanks
Click to expand...
Click to collapse
Ok, your wish is my command! ;-)
Sent from my DROID2 using XDA App
Can I close this?
Yes. This issue has been resolved.
theecho said:
Yes. This issue has been resolved.
Click to expand...
Click to collapse
Ok, thanks
Okay, I've searched and searched and no one seems to have the specific problem that I'm having with my phone, so I'm taking to the forums myself. I've been rooting since the G1, I know how to adb push things, I have used google and multiple forums to try to fix this problem. So here goes, anyone that can help I thank you in advance.
1-My phone, like some other MT4G users, reboots itself each time it's plugged in. Initially I thought this was because I was using a Kindle cord to plug it into the pc, so I bought an MT4G usb cable from tmobile, and still it boot loops (just the first white screen for maybe 4 seconds, then black then again and again). The only way to charge it is to let it start boot looping, take the battery out, turn it on, and if I'm lucky enough that it begins to boot up correctly I plug it in mid boot. If I wait til it's fulled loaded it just starts rebooting again.
2-It will not at all from any angle go into Recovery mode. If I try to go to recovery from Rom Manager, or from the screen you get when holding power and lower volume key or by flashing a rom through Rom Manager, it just boot loops just like mentioned above, until I pull the battery for a while (it is currently sitting next to me with the battery out) and then put it back in.
3-If by chance it's on, and plugged into the computer, it is not at all recognized. Ever. While it's booting up my computer finds something, but doesn't know what it is, and doesn't allow me to view any folders on the SD card. Yes I've installed the HTC drivers file. I've adb'ed things to this phone before, now it says device not found. I don't know when it stopped being recognized...
4-I've even tried to fastboot something over to it, but to no avail, still not found.
If I try to do a factory reset, it boot loops. If I sneeze it boot loops.... I don't know what to do, and if I trade it in under warranty, I have to reset it to stock rom, or they're going to charge me for a new phone. Any ideas!?
I have Cyanogen mod 7 on here.
have you tried a fastboot wipe? or have you tried to reboot to recovery from adb?
First, I don't trust using the actual ROM Manager app to do the flashing/installing.
Since you've been flashing since the G1 days why not use Clockwork Recovery? Just go into recovery and do the necessary wipes.
So I suggest to do a complete full wipe in Clockwork, meaning wipe data, cache, and dalvik cache. Install the newest CM nightly (Which is working wonderfully BTW) and see if your problems still persists.
Edit: I didn't realize you tried to enter recovery, oops. But yeah try what the buy above me said. Try re-installing the latest CWM recovery, if that still fails then try heading into there via ADB.
mackster248 said:
First, I don't trust using the actual ROM Manager app to do the flashing/installing.
Since you've been flashing since the G1 days why not use Clockwork Recovery? Just go into recovery and do the necessary wipes.
So I suggest to do a complete full wipe in Clockwork, meaning wipe data, cache, and dalvik cache. Install the newest CM nightly (Which is working wonderfully BTW) and see if your problems still persists.
Click to expand...
Click to collapse
I second that, flashing ROMs from ROM Manager a terrible idea.
Well...if all else fails and if you are really thinking about returning it and still under warranty...few seconds in the microwave method should work just fine. They wont be able to see that its rooted if the phone wouldn't turn on, would they???
glimmer of hope...
So by the grace of god I did get it flashed back to unrooted, stock 2.2 by putting it as pd15img.zip on my sd card and going into bootloader. Once that was done I thought I would be out of the woods... I even plugged it in last night and no boot loop!! but this morning I unpllugged it (and I'm using a tmobile cable for the phone attached to my pc) and here it sits, next to me again with the battery out of it because everytime I try to turn it on (for over 40 minutes now) it boot loops to that stupid white screen (that is honestly driving me insane at this point). I know that it isn't rooted (because I dl'ed rom manager and it won't let me do anything without being rooted) so do we think that I'm safe to go to the store today to request a new one be sent? Thoughts? And thanks for the help thus far!
yeah I would send that back
Bad emmc chip? I'm sorry man, that's a terrible story.
Sent from my HTC Glacier using XDA App
Guys please I know this is the wrong forum but no one is answering help. At all. Alright, I went to flash the ICS Sense alpha, and needed to restore a backup. I went into hboot, and restored the PD98IMG.zip. Afterwards it said "Press power to reboot" so i did. The phone turned off, and now nothing. After a LONG time the phone turned on to the White HTC Splash and vibrated CONSTANTLY, until the battery was pulled. I tried volume down + power but nothing. Except for the occasional white screen, nothing. Please, anyone/.
You're bricked
Sent from my Desire HD using telepathy...
I think your phone had a bootloop. Did you already installed custom recovery? Can you enter it through fastboot menu (vol down + power)?
I doubt he's bricked,why are you restoring that zip? You restore your back up....from clockwork?
Sent from my Desire HD using XDA Premium App
It won't enter into fastboot. Occasionally the white HTC screen comes on with a constant vibrate and the only way to stop that is to pull the battery. No fastboot, no recovery, nothing.
It wouldnt enter into recovery so I had to take the long way, by using the PD98IMG
HTC_Phone said:
It won't enter into fastboot. Occasionally the white HTC screen comes on with a constant vibrate and the only way to stop that is to pull the battery. No fastboot, no recovery, nothing.
It wouldnt enter into recovery so I had to take the long way, by using the PD98IMG
Click to expand...
Click to collapse
I am confused. So what exactly happens when doing this:
remove or rename the PD98IMG on the sd card
pull the battery from the DHD
re-enter it and hold volume down and power until the hboot starts
navigate by volume down/up to Recovery and press POWER
If you had to restore back to factory, why bother flashing ICS?
You should get away by installing one of the RUU using PC. here is a guide on how to install RUU and you'll have to search this section to find a RUU or google it.
Though firstly i would ask you if you can go into the recovery mode anyhow since you're saying that your phone can get the HTC logo. For that, hold down POWER + volume DOWN key to get you into hboot (IF YOU CAN) and choose recovery from there, once in recovery, go to option where you wipe your data + cache, wipe both of em and try restarting again...If you can't even get into recovery then do the RUU way of getting the rom working.
EDIT:
I'm not sure what in the world happened, but it booted into the ATT stock ROM. After 30 minutes of vibration and idk what else, it finally booted.
Lol least its on
Sent from my Desire HD using XDA Premium App
HTC_Phone said:
EDIT:
I'm not sure what in the world happened, but it booted into the ATT stock ROM. After 30 minutes of vibration and idk what else, it finally booted.
Click to expand...
Click to collapse
Gratz, suppose this thread's unnecessary now?
Anyway take care of what you do: always do a nandroid backup prior to flashing everything. Better spend 5min for backup than 5 days without a phone.
I think know what happens. If I remember correctly you had your phone replaced. And it came with gb. The pd98 you flashed was the froyo one. Hence the crazy vibration and long boot time. If Im right thisvwill happen each time you reboot Until you get the gb bootloader back on
Also spamming the threads is a pretty good way of getting banned. Maybe zel or Andy will be nice about it
marsdta said:
I think know what happens. If I remember correctly you had your phone replaced. And it came with gb. The pd98 you flashed was the froyo one. Hence the crazy vibration and long boot time. If Im right thisvwill happen each time you reboot Until you get the gb bootloader back on
Click to expand...
Click to collapse
That sounds somewhat correct. I DID get it replaced, but had a GB PD98 on the SD card. Anyway, it vibrated for quite some time, and eventually the vibration stopped. So I let the phone sit as I figured out some way to salvage the phone. And the the next HTC splash booted, and the phone proceeded into the stock ROM. Idk what happened, but I'm not complaining.
Dear Lord, it just turned off and is doing it again. But, I'm praying for the best again. Thanks guys.
HTC_Phone said:
Dear Lord, it just turned off and is doing it again. But, I'm praying for the best again. Thanks guys.
Click to expand...
Click to collapse
When you succesfuly back in your phone, just root it with AAHK and install some custom ROM and you should be fine.
motherninja said:
When you succesfuly back in your phone, just root it with AAHK and install some custom ROM and you should be fine.
Click to expand...
Click to collapse
The phone itself is already rooted, but I tried booting into CWM, and it did the same thing as it did before. So I have to run the RUU, and then S on the phone, and run the hack kit again. I already ran the RUU once, and nothing.
Probably best just to start over and do everything again,even if you've already done it,maybe the root didnt work?
Your phones a nightmare mate
Sent from my Desire HD using XDA Premium App
So you intentionally created a thread in the wrong section?
I guess the rules don't apply to you then.
Oh crap, here goes:
I loaded up the Energy Rom from NRGZ28 in my kindle and booted into recovery. I hit the "Wipe Data" option and noticed after a couple of minutes that the application froze (it wans't doing anything) and would not respond to anything I did. So figuiring it was only data and not a system wipe I held the power button down for the 10 second reboot expecting it reboot into the current rom since all it was missing was data and I would just sign in and set up like I always do. How wrong was I, it is now off and will not turn on no matter what I do. Crap, after flashing roms for the last 3 years on phones and my Kindle since roms were available for it I think I made my first brick
I did not get to flash the new ROM so I know it wasn't that and Iv'e been using this recovery since Hash put it out for us so not sure what went wrong.
Anybody able to bring theirs back to life, I'll be trying the fire_fix tonight to see if that might help via USB.
did firekit sort it for you?
sent from my new non bricked kindle
Jdom58 said:
Oh crap, here goes:
I loaded up the Energy Rom from NRGZ28 in my kindle and booted into recovery. I hit the "Wipe Data" option and noticed after a couple of minutes that the application froze (it wans't doing anything) and would not respond to anything I did. So figuiring it was only data and not a system wipe I held the power button down for the 10 second reboot expecting it reboot into the current rom since all it was missing was data and I would just sign in and set up like I always do. How wrong was I, it is now off and will not turn on no matter what I do. Crap, after flashing roms for the last 3 years on phones and my Kindle since roms were available for it I think I made my first brick
I did not get to flash the new ROM so I know it wasn't that and Iv'e been using this recovery since Hash put it out for us so not sure what went wrong.
Anybody able to bring theirs back to life, I'll be trying the fire_fix tonight to see if that might help via USB.
Click to expand...
Click to collapse
What recovery did you use-TWRP or CWMR 5.5.0.4? See herehttp://forum.xda-developers.com/showthread.php?t=1651413
Ok, I'm new at this, here's what I've got, hopefully someone can shed some light:
-My RAZR M is fully encrypted
-It is successfully rooted
-I have installed Rom Manager with CWM 6 as the custom recovery
-I want to make a NANDROID backup (to eventually install Carbon), but whenever I try to reboot into the backup/recovery mode, it won't, it goes to what I think is the ADB screen? Not sure tho, this screen says "Connect data USB." Then, when I do, it just changes state and says USB connected, nothing else happens. Then I just reboot the phone normally and everything still works.
So after googling and researching a lot, I'm assuming since my phone is encrypted it won't access the CWM because it never asks me for my password to decrypt the internal storage. Ok cool, but here's my question now tho; if I perform a Factory Reset from the settings menu, will it actually do the reset and reinstall itself since I have CWM installed??
Thanks for any help.
Anyone got any ideas??
Is your bootloader unlocked?
Sent from my XT907 using xda app-developers app
Hmm. Is this screen where it says "Device is LOCKED" mean that my bootloader is locked? Btw, this is the screen that I referred to in my first post. It comes up whenever I try to select "Recovery"
Your bootloader is locked and on that version it can not be unlocked... So... unfortunately you can not install a custom recovery... Well you can use safestrap but the ROM selection is very limited...
Sent from my XT907 using xda app-developers app
So you say I cannot install a custom recovery, do you mean a different ROM that I would "recover" to install it? Or do you mean ClockworkMod (and its various counterparts)? Because in the ROM Manager app, it says I have CWM 6.0.4.4 as my "current recovery" (see attached screenshot)
Please forgive me if this is a dumb question lol but like I said, I'm new at this whole thing
It does say that huh unsure as to why... i do have a locked M around here somewhere ill see if it does the same thing to it...When I say custom recovery I do refer to cmw n twrp... With a locked bootloader you can not install those... we have for safestrap as a recovery for locked bootloaders it's been a year since I used it but I believe you can make backups on it... I would just sit tight and.wait on kit kat it shouldn't be to much longer... till then just freeze all the bloat and use xpossed to your liking... When kk comes out I'm sure development will pick up for locked bootloaders again..anyone else with more experience care to provide more in depth assistance..
Sent from my XT907 using xda app-developers app
So any further advice on what I can or can't do?
I would like to perform a factory reset on my device to get rid of this stupid encryption (it slows everything down), but with CWM installed (supposedly?), can I still do a factory reset? I guess what I'm trying to get at is what does the factory reset option use to re-flash everything from? The recovery partition where CWM is now supposedly installed? Will that affect the factory reset?
I hope this makes sense, I don't want to brick my phone...
Alrighty, for anyone interested:
I never tried the factory reset. What I did do is try the OTA KitKat update just like 2 hours ago. That was a mistake; upon downloading and automatically rebooting to start the upgrade, my phone would not reboot, it got stuck at the AP Fastboot screen with the error code 0x56 (see attached picture).
So, I powered off and powered on my phone, at which point it powered up normally, until after about 2 minutes on the home screen, it automatically rebooted itself (to presumably "continue" trying to install the OTA). Then it got stuck again on the AP Fastboot screen. This continued over and over and I soon realized I soft bricked my phone.
Did some further research, found the House of Moto program (http://www.droidrzr.com/index.php/topic/28162-house-of-moto-22/) which saved my life. If anyone is having any issues similar to the situation I was having, or just issues with the KitKat OTA, this House of Moto program will restore your phone to completely stock. Just follow the instructions on that web page exactly. Kudos to the dude who developed that.