ok so, today my phone dropped and cracked the top of my screen. i filed my insurance claim and will recieve my new phone tomorrow. atm im rooted, running stock and beanstalk on rom1. theres rly nothing to backup on my rom1 slot as i just finished setting it up yday. i ran through titanium backup and hit most apps i thought a good idea to backup and i think i did a full backup from cwm of my stock. just wondering if theres a better way to make sure i dont miss anything that i may need for the new phone. thanks ahead of time for all input.
Sent from my DROID RAZR using xda app-developers app
also. what shpuld i do to unroot and factory reset for the return of this phone?.
Sent from my DROID RAZR using xda app-developers app
Related
Right now I just have root using The torpedo method through TE because my laptop is dead. Gonna go buy another one today and was thinking about using it to be able to get into and real recovery and then being able to flash the 1.4 kernal just to try.
but I don't want to have to reinstall everything on my phone once I do this so I'm just wondering if i have a backup from bootstrap would I be able tto use that once I root using another method?
Sent from my MB855 using XDA App
There was a guy on here who had to exchange his phone for a new one and when he loaded his backup from his old phone it bricked the new one (I think). I don't know for sure but I wouldn't advise it.
Sent from my MB855 using Tapatalk
Hmm that sucks. Thanks for the info. Glad I asked first.
Sent from my MB855 using XDA App
RAZR Maxx - Verizon Wireless CDMA
I have my settings to vibrate on touch but for some reason it randomly stops vibrating and comes back randomly.
For instance, right now as I write this there is no vibration when I press the keys on the keyboard.
I noticed it after the first time I rooted the phone. After rooting everything was fine. Decided to go back to stock 211 and unroot for the time being. I was using Matts utility and it froze for some reason. It got stuck on writing the webtop part for over an hour so I knew something was not right.
I turned the phone off, closed the utility and started all over again and it went through fine. From since then I've been able to root, flash roms, revert back to stock 211 all using the utility but my vibrations act funny.
I never had the vibrations on touch turned on when I was on gingerbread so I don't know if it's just my phone or if it was the unrooting freeze or what? I never really complained about it but I would like to know if anybody else's phone does this?
try slapping the bottom of your phone against your palm (kevlar against palm) a friends razr did this and that seemed to work, it went awway after a few days
I might sell this phone and roll with something else.
Sent from my DROID RAZR using xda app-developers app
I'm experiencing the same issue as well....if didn't start until I Began using motomizer which could just be coincidence
Sent from my DROID RAZR using xda app-developers app
I have the same issue but I have not rooted it. Also, to get a temporarily fix which lasts for a minute or so, I have to shake the phone. I think the vibration motor is failing.
Sent from my DROID RAZR using xda app-developers app
It's good to know others have the problem too. I thought my phone may have been defected or else I messed it up trying to unroot it the first time round. I might try to get the Maxx HD. But then again it's better off to wait lol, this phone game is moving too fast.
Sent from my DROID RAZR using xda app-developers app
Thank Me Later said:
It's good to know others have the problem too. I thought my phone may have been defected or else I messed it up trying to unroot it the first time round. I might try to get the Maxx HD. But then again it's better off to wait lol, this phone game is moving too fast.
Sent from my DROID RAZR using xda app-developers app
Click to expand...
Click to collapse
I know. By the way can u use a headset with your phone without disconnecting or getting stuttering sounds if you move the headset connection?
Sent from my DROID RAZR using xda app-developers app
migpol08 said:
I know. By the way can u use a headset with your phone without disconnecting or getting stuttering sounds if you move the headset connection?
Sent from my DROID RAZR using xda app-developers app
Click to expand...
Click to collapse
I never attempted to use a headset with my phone. I've used headphones for music and movie listening and they were all fine. I don't lose data at all when using headphones.
Sent from my DROID RAZR using xda app-developers app
I had this problem too. I reloaded Arctic from scratch making sure to format cache and Dalvik and that still didnt help.
What fixed mine was booting into Safestrap Recovery, going into Advanced, and selecting Fix Permissions.
I realize this won't help the non-rooted folks.
Sent from my DROID RAZR using xda premium
I'll keep that in mind if I root again.
Sent from my DROID RAZR using xda app-developers app
FReQ Z said:
I had this problem too. I reloaded Arctic from scratch making sure to format cache and Dalvik and that still didnt help.
What fixed mine was booting into Safestrap Recovery, going into Advanced, and selecting Fix Permissions.
I realize this won't help the non-rooted folks.
Sent from my DROID RAZR using xda premium
Click to expand...
Click to collapse
I tried this and it didn't help. The suggestion above (slapping the back of the phone) seems to be working, though. I wonder if my telephone (Razr i) is defective, this started after rooting and unlocking the bootloader. I tried with the GB and EU JellyBean stock ROMS, and I'm currently using this one, all with the same results, does anyone have a similar issue?
I've dealt with two buddies' RAZR phones (Original, and MAXX) and they both have failing vibrator motors. Seems like a hardware design issue. Good thing I went with the Note 2
same issue
motorola razr max
rooted
boot menu manager
tested on all my custom rom (CM10.1 , AOKP , JB 4.2.1) and same issue
anybody have this issue in OTA update and updated bootloader (JB 4.1.2) ?
Since the 4.0 OTA my phone has just been doing random crap.
1.) Locking up and rebooting at least once a day.
2.) In the middle of a phone call it will disconnect the call with whomever i was talking to, and connect me with a random person from my address book.
3.) one of the verizon junk apps (Emergency Alerts i think it is) will go off on its own, and i have never used it or set it up..
so i take it in and Im not sure if i am the only person who has been having these problems (from what the verizon rep noted, i was not the only one). they are sending me a new one , they said that the OTA made a mess on some phones, bricked others and the ones that are from the factory or newer ones are working much better.
now for the part that surprised me..take this with a grain of salt as usuall but she said that the 4.1 Jelly bean was going to be ota in about another month..
anyways, anyone else had the listed problems?
ps central us for those that are going to ask, no longer vat/city
If I do a lot of browsing, my phone will randomly scroll through random apps and open them, almost like the screen is stuck. Only way to stop is power volume down. Then it is good for a day or two, then it does it again. I am completely stock, never rooted or installed custom rom.
Sent from my DROID RAZR using xda app-developers app
cmraymond said:
If I do a lot of browsing, my phone will randomly scroll through random apps and open them, almost like the screen is stuck. Only way to stop is power volume down. Then it is good for a day or two, then it does it again. I am completely stock, never rooted or installed custom rom.
Sent from my DROID RAZR using xda app-developers app
Click to expand...
Click to collapse
I got my phone yesterday, and so far not a single problem and there is a difference from a phone that received the ota and one that was shipped with 4.0. one that has been shipped with it is defiantly smoother has a quicker response. im happy i sent mine in.
Do a factory reset and you will have no more problems.
Sent from my DROID RAZR using xda premium
Adauth said:
Do a factory reset and you will have no more problems.
Sent from my DROID RAZR using xda premium
Click to expand...
Click to collapse
I'll second this: the sound on my Razr cut out at times. I did a factory reset last week, and have had no problems since then.
Sent from my DROID RAZR using xda app-developers app
I have done two resets since I received the update. Didn't install any apps for a few days in case that was the culprit. Still have the issue.
Sent from my DROID RAZR using xda app-developers app
I can vouch for what cmraymond is saying, i tried repeatedly using the factory reset and nothing it would still do it. i even deleted everything i had on my sd card and even tried a diff one. no change. new phone is running great.
phrite said:
I can vouch for what cmraymond is saying, i tried repeatedly using the factory reset and nothing it would still do it. i even deleted everything i had on my sd card and even tried a diff one. no change. new phone is running great.
Click to expand...
Click to collapse
So how does returning the phone work if I bought it on new egg.com. Do I go through them or can I call Verizon to do a warranty exchange. I've had the phone since March this year.
Sent from my DROID RAZR using xda app-developers app
cmraymond said:
So how does returning the phone work if I bought it on new egg.com. Do I go through them or can I call Verizon to do a warranty exchange. I've had the phone since March this year.
Sent from my DROID RAZR using xda app-developers app
Click to expand...
Click to collapse
If it's under factory warranty, Verizon will send you a refurb. My previous phone was a Incredible 2 that I purchased at Radio Shack, and when my LCD stopped working after about 5 months, Verizon sent me a replacement at no cost.
As a last ditch effort, you can try flashing the stock fastboot files. I'd recommend a factory reset and format of the cache partition before doing so. That way, if there was something that didn't update properly with the OTA, you're starting off with a fresh, clean install. Instructions to flash are here http://theunlockr.com/2012/01/24/how-to-restore-the-motorola-droid-razr-using-fastboot-files/, and the fastboot files are found here: http://sbf.droid-developers.org/cdma_spyder/list.php
Hey guys my screen went out yesterday. I took it to Verizon and I am getting refurbished rezound under the total protection plan.
I am rooted...unlocked....custom boot loader...and Rom...c
Do I need to try to relock and factory reset every thing?
Since the screen went out due to bad hardware...does me having custom Rom and software screw me when they put a new screen in the old phone?
Sent from my KFTT using Tapatalk 2
ninjabeaver said:
Hey guys my screen went out yesterday. I took it to Verizon and I am getting refurbished rezound under the total protection plan.
I am rooted...unlocked....custom boot loader...and Rom...c
Do I need to try to relock and factory reset every thing?
Since the screen went out due to bad hardware...does me having custom Rom and software screw me when they put a new screen in the old phone?
Sent from my KFTT using Tapatalk 2
Click to expand...
Click to collapse
Better safe then sorry re lock s on
Sent from my Infected Rezound using xda app-developers app
ninjabeaver said:
Hey guys my screen went out yesterday. I took it to Verizon and I am getting refurbished rezound under the total protection plan.
I am rooted...unlocked....custom boot loader...and Rom...c
Do I need to try to relock and factory reset every thing?
Since the screen went out due to bad hardware...does me having custom Rom and software screw me when they put a new screen in the old phone?
Sent from my KFTT using Tapatalk 2
Click to expand...
Click to collapse
Its hard to do without a screen. But if you use the rezound toolkit you can run the ruu and that will get you back to stock. the progress will show on the command prompt so you will know when its done. Like the post above said, better safe than sorry. Chances are they won't even check though.
Sent from my Nexus 7 using XDA Premium HD app
Best to unroot if not and they see its rooted they can deny your claim and charge you full price. Not worth the risk
Sent from my ADR6425LVW using Tapatalk 2
Didn't unroot. Didn't S-ON. That's just me, though. Mainly because I forgot. I had no problem with it from Asurion. Though, as others said, better safe than sorry. You never know.
Sent from my ADR6425LVW using xda app-developers app
I currently own a DNA, and I just received another brand new in the box. I would like to keep the new one and give my old one to my wife. Can I take a nandroid of my current DNA and then restore it on to the new DNA? Thanks!
Sent from my Nexus 7 using Tapatalk
You should be able to, but I'll defer to more knowledgeable members. I know I've used a backup on other phones of the same model. To be safe you can use titanium backup and restore apps to the new phone and not the rom.
Sent from my HTC6435LVW using xda app-developers app
If your motherboards are the same, everything will be fine. If they are different, there might be some odd bugs. To see what motherboard you have, go to about phone, phone info and look at the "serial number" most HTC devices the first 4 numbers are the motherboard identifier.
In short, yes you can, just do not report bugs if any arise.
Sent from my DNA using my mind.
My current phone's serial number starts with FA2B, while the new phone starts with FA3B. Is that going to cause me grief? I've spent so much time getting my phone "perfect" that I was hoping to avoid doing all the setup again. I guess I could use TiBu to do it, but it seems like a nandroid would be much quicker!
Take a nandroid of the new phone before trying the one from the old phone. If there are issues you can then go back to the original nandroid
Sent from my HTC6435LVW using xda app-developers app
TiBu and flash new. Save yourself any possible issues
Sent from my DLX using xda app-developers app
Just figured I'd come back and let everyone know it worked like a charm. I did a quick nandroid backup with TWRP on the new phone to create the correct folder structure, then copied the nandroid from my old phone into the appropriate folder. Restored it, and it fired right up and worked with no issues.