In preparation for upgrading to a Moto X I had them replace my wife's old D3 (with another D3, if you can picture the dusty warehouse that must have THESE spares..) Anyway, what's the more straight-forward way to move from the old one to the new one? The only thing wrong with the old one was a flaky keyboard, so it's accessible for the process.
The old one is rooted and has a 32gb microSD card. Both the old & new are running 5.7.906
The one thing I haven't done yet is activated the new phone (did the four corners green guy skip). The SIM card is not inserted in either phone at the moment. I'm loathe to spend the likely HOUR on the phone it'd take with Verizon and then if the new phone "doesn't work" I'd have to do the dance all over again. Let me get the phone set up first...
I thought I was headed in the right direction by first rooting the new one (via the motofail method) which seemed to work. I then bought and loaded the $3 CWM tool. I used that to create a backup on the old phone to it's SD card. Also, seemed to work. Also downloaded the CWM app onto the new phone, powered off, brought the SD card over, powered up, used the app to reboot into recover and reloaded the backup. Seemed OK. Lots of stuff 'looked like' it was present and usable. I wanted to then go and whack out the bloatware.
But now the new phone reboots. Not right away, it takes a few minutes but then, with no messages on the screen, it just spontaneously reboots. It only seems to do this if the USB cable is connected and USB debugging mode is selected.
It does not reboot unless USB debugging is enabled.
Ok, so perhaps I've missed some critical steps or something. It's been a while since I had to do this sort of thing and this is a pretty old phone. I'm inclined to think there's and ADB driver issue here. But I'd like to be sure to head in the right direction before making a bigger mess.
Suggestions?
Random reboots after moving CWM backup to new D3?
Just when I thought everything was done... bam, it reboots randomly.
I had a D3 with a flaky keyboard. Got a replacement since it's been covered. Going to decommission it next week with a Moto X.
Got the replacement D3 (hoped for a D4 but they STILL have stock of replacement D3's). Old one was rooted and had the D3 Bootstrap app on it. Booted into CWM and made a backup to a blank 4GB microSD card.
Rooted the new D3 using motofail. Loaded the D3 Bootstrap app and restored the backup made from the old Droid3. Seems to 'take'.
But then I started getting random reboots. Thought it might be just related to the USB debugging, so I turned that off. Seemed to stop rebooting.... for a while. STFW said WiFi networks can be problematic, so I deleted all the old networks and turned off WiFi. No love, still reboots.
In fact, while I've been typing this it's rebooted twice.
Ok, so before I subject myself to the utter nonsense that is Verizon support, what steps should I take to narrow down whether it's an issue with the phone or the way I did the restoration to it?
HELP!
I'm thinking I would have taken the old motherboard, and slapped it in the new phone. Just an idea....
Dougnsalem said:
I'm thinking I would have taken the old motherboard, and slapped it in the new phone. Just an idea....
Click to expand...
Click to collapse
Given it was insured there wasn't really any need, other than the possible quicker turn-around. They sent the replacement's replacement in just two days more, so it wasn't a big wait. That one has been fine.
Meanwhile the Moto X was shipped Fedex signature-required, and the driver didn't wait long enough for me to get out of the shower. Nor did they respond to a phone request asking the truck to circle back around later. So presumably it'll be delivered later today.
Related
So I have this old g1, it's been through 5 owners and over the summer it got crunched in a recliner chair mechanism, and it stopped booting up. In short, I took it apart, determined that the slight bend in the daughter board to motherboard connector was the culprit. However, a month or so ago it started booting again, and the only 2 serious issues with it that I have found is that if you press too hard on the back, the daughter board becomes disconnected, which causes the processor to be cut off, crashing the phone, requiring a battery pull, etc etc., and also that the sd card controller no longer works. (Also for some strange reason rebooting won't actually reboot the phone, it just does this odd interlace fade to a black screen and you have to do a battery pull to even get it to turn off, only power off works)
Anywho, the issue about the daughter board connector becoming disconnected temporarily on pressure wasn't a huge issue as long as you were careful with the phone. The sd card controller wasn't an issue either until I wiped /system without knowing the sd card slot was dead.
The phone boots into fastboot and recovery, it has clockworkmod. However, I can't really flash a new rom onto it without an sd card, and I have tried every way fathomable to mount a folder in /system/ or somewhere on the nand as the sd card so I could adb push a rom and flash it, but it never worked.
I tried flashing something from fastboot, but it gave an error about the signature verification or something rather. Any suggestions for flashing through hboot/fastboot? Have I just not found the right htc signed zip yet or what? Help much appreciated. Its not a huge deal since I have a mt3g slide now but it'd still be cool to **** around with the g1 ya know? First android phone ever manufactured and its still kickin. But if its done, its done. It lead a good life, 5 owners haha.
Thanks in advance!
Sent from my T-Mobile myTouch 3G Slide using XDA App
My nook was rooted and I was happily using it for about 3 weeks.
It was a ver. 1.0.0 model.
One night I went to turn it on and it wouldnt come on. I thought somehow the battery must have drained out. I plugged it in when I got home, but after a while I tried to start it and it still wouldnt.
What I have noticed is that the backlight comes on, changes intesity a couple times, goes off and then comes back on, like some sort of loop.
There is no message screen or N screen. There is no booting from SD, as far as everything I've tried to burn to SD and boot from.
I've tried all the key combos, some result in different variations of the backlight sequence but nothing else.
I think it is caught in some sort of loop before looking for any bootable system.
I want to try everything I (and everyone else) can think of before I go to the trouble of shipping it back to B&N.
Can you put the original stock system on an SD, even though I doubt it would boot from that either, but just a thought.
Thanks,
Phil
Looks like you are going to be enrolling in the NC advanced class. I really can't help on this but this weekend I plan one doing a the group install internally and I should be knowledgable afterwards.
Start by looking into creating the froyo image one a sdcard. There is a thread. The NC should be able to boot from that card. If it does great. Now look for thread about recovering images and using dd to write images. Someone did post the stock images 1.01
have you tried booting Nookie Froyo through an SD card? Then you could probably flash a stock rom (zip is in the forums) and restore.
Froyo
Yeah, I have Froyo on an SD card right now. Doesnt make a difference.
I have pretty much run out of things to try, unless there is some new, secret key combo that fixes everything.
I really don't think its even getting to the OS, I think I must have some real hardware failure that has nothing to do with the stock or rooted OS.
Sounds like it may be time for a warranty claim...
spiicytuna said:
Sounds like it may be time for a warranty claim...
Click to expand...
Click to collapse
i agree, if its not even getting to the point where it can boot from sd then theres nothing that i can think of that will work, at the point your at i dont think it can recognize any button input or usb data as there literally is nothing it knows how to do
Is this possibly the first successful Bricking?
I hope not!! Keep us posted on what works and what doesn't work.
Good luck, mate.
Cheers!
Received new Nook Color.
Well I did a warranty claim.
It was a very long wait on the B&N help line. I hung up and used the online chat window. That was a very long wait as well, about 25 minutes, but I finally got through.
After explaining all the things I tried and what the nook was doing, she wanted me to hold the power button for 10 seconds. I was like, "Ok, I've tried holding it for several minutes at a time, several hundred times, but what the hell." Then she wanted to know if I dropped it or not. Mine was pristine though, not even a scratch.
So finally she said I qualified for a replacement.
The deal is they give you a ups shipping label and they ship you a new Nook. If they determine that your nook got wrecked because of your own stupidity or whatever they bill you for the new one. She said the new one would ship the next day, but it didn't ship for over a week. I shipped mine the next day with the label they sent me.
So now finally I have my new nook. I haven't rooted it yet, though I probably will. I don't believe my problem was ever related to the software things I did, I dont believe that could wreck the hardware.
Also I never mentioned rooting it or anything.
Did you try burning CWR onto a SD card and seeing if it boots?
Hey guys!
I'm having some serious issues with my HD7... the other night I put it on my charger and went to bed. When I woke up the next morning my device was unresponsive, for one the alarms didn't go off on it. The charging indicator led was lit... I pushed the power button to wake it up and nothing happened (I thought ok, strange) I unplugged it from the charger, indicator light went off and still nothing, it was at this point that I noticed our cat chewed the crap out of the devices USB cable in the middle of the night. (Ugh!!) So I removed the battery and rebooted it and everything seemed fine. A little while later I went to use it and I pushed the power button to wake the screen and again not responsive, remove the battery and reboot and it seems fine. Later I was on it on XDA and I set it down for a min and it starts to go into sleep mode and freezes on a partially dark screen and none of the buttons work, power, volume up/down, camera or the soft keys, pull the battery and reboot its fine, this continues throughout the day so I did a hard reset and the problem still persists. So this continues on for 2 days, so I flashed back to stock rom and perform a hard reset before the first boot and i run stock for a day to see if this helps and unfortunately not it still has the problem. I'm back on DS v7.8 and have performed numerous hard resets now but I think there is a definite hardware issue from when the cat chewed on the cable while it was plugged in!
I have the insurance on the device and can make a claim but the chances of me getting a brand new one from Asurion are slim to none and will probably end up with a refurbished one and I would prefer to just keep mine!
So I'm turning to my great and knowledgeable friends here at XDA for any advice or suggestions on how to fix this problem.
Many thanks in advance!
you do understand that your v7.8 is a betta version and has a lot of bugs, right?
http://forum.xda-developers.com/showpost.php?p=17735584&postcount=3
so try a mango rom and let me know!
Meivoon said:
you do understand that your v7.8 is a betta version and has a lot of bugs, right?
http://forum.xda-developers.com/showpost.php?p=17735584&postcount=3
so try a mango rom and let me know!
Click to expand...
Click to collapse
I do understand that it's buggy and isn't the most stable rom... That's obviously a sacrifice with running a beta version!
As stated in the OP, I flashed my device back to a stock/shipped 7392 rom and ran that for a full day and a half. Then after my post yesterday I flashed back to 7720 Mango rom for a day now and still continue to experienced the exact same problems.
I was actually experiencing the problem before I ever flashed to DS v7.8... Just to clarify between flashing 7392, 7720, DS v7.78 and DS v7.8 the device experiences the issues evenly across the board... Unfortunately no one rom made it any better.
Thanks for the idea though!
I think I've just come to accept the fact that when the cat chewed the USB cable it caused some short circuitry which in turn caused some hardware damage.
After talking to Asurion earlier today, they have informed me that I'm not the first person to experience an issue with their device after a pet had chewed/damaged the USB cable while it was plugged in... They have had multiple claims for the same reason. I will be receiving my replacement device sometime tomorrow, well technically today now!
well, initially, my thought was a bad flash... but you reflashed.
so, my thoughts go to either battery or microSD card.
maybe try re-XSPL-ing.
if still same issue, would try another battery or microSD card.
honestly, though, unsure of a definitive solution.
regards.
I know this ones been a tough nut to crack... I've been racking my brain on it for a week now!
I've re-XSPL-ed twice now and have flashed it more times than I'd like to admit...lol
I have a backup battery and have tried that too with no success.
I haven't tried a different SD card yet - Good idea... It had crossed my mind but is such a pain in the "you know what" to unlock the SD card card and swap it out.
I am preparing for it though, I just downloaded Cab Sender and Storage Lock Cab. Guess I'll have to flash it again to a rom that supports Cab sender and since I'm getting my replacement device today, I need to unlock and remove my 32gb SD card anyway and that will give me the opportunity to try a different SD card in it and see how it performs.
I'm debating on whether or not to send mine back... I have 15 days to return mine after I receive the replacement, if I don't they only charge me $75 for it.. I didn't think that was bad at all and it's almost worth it to keep it for $75 and see if I can get it functioning like normal.
BTW Shadow... love your new avatar/forum pic!
xdrc45 said:
I know this ones been a tough nut to crack... I've been racking my brain on it for a week now!
I've re-XSPL-ed twice now and have flashed it more times than I'd like to admit...lol
I have a backup battery and have tried that too with no success.
I haven't tried a different SD card yet - Good idea... It had crossed my mind but is such a pain in the "you know what" to unlock the SD card card and swap it out.
I am preparing for it though, I just downloaded Cab Sender and Storage Lock Cab. Guess I'll have to flash it again to a rom that supports Cab sender and since I'm getting my replacement device today, I need to unlock and remove my 32gb SD card anyway and that will give me the opportunity to try a different SD card in it and see how it performs.
I'm debating on whether or not to send mine back... I have 15 days to return mine after I receive the replacement, if I don't they only charge me $75 for it.. I didn't think that was bad at all and it's almost worth it to keep it for $75 and see if I can get it functioning like normal.
BTW Shadow... love your new avatar/forum pic!
Click to expand...
Click to collapse
only $75 for a new, refurb HD7? that is a steal!
they still for about $150 on eBay.
good luck on your venture and don't forget to report back.
and thanks.
This is the exact same issue I've been having with my HD7s. And I was running stock Mango since AT&T had never pushed any updates when this started. Since it started happening I tried the manual upgrades to 8107 and 8773 and it's still happening during the charge, and a few times it's locked when I didn't lock the screen and it was attempting to auto-lock. Anyone figure out if it is indeed hardware or if it's just something else happening?
So, I think I located the source of the crashes. After I've disabled WI-Fi for three days I haven't had a crash. Would upgrading to the Mango v2 drivers possibly fix this? It's not a huge issue to turn on Wi-Fi as needed, but it did work for months without me having to disable Wi-Fi to get a reliable phone.
mancide said:
So, I think I located the source of the crashes. After I've disabled WI-Fi for three days I haven't had a crash. Would upgrading to the Mango v2 drivers possibly fix this? It's not a huge issue to turn on Wi-Fi as needed, but it did work for months without me having to disable Wi-Fi to get a reliable phone.
Click to expand...
Click to collapse
Did you ever get your HD7 working properly and did you try the v2 drivers?
Here's the update for my device....
I flashed Dynamics 7 to my old HD7 and installed Storage Lock cab via cab sender, (which Storage lock ran very well on D7 and didn't cause any problems with the rom) unlocked the 32gb SD card I had in it and removed it from the device. I re-installed the original 16gb SD card (that I was locked out of completely) and put the device back together, booted the device, performed a hard reset and what do you know... the device unlocked and recognized the SD card.
I then flashed it back to stock 7392 rom and ran the device on it for the next 2 days and the problem still persisted. So I flashed it to stock 7720 Mango to see if maybe the Mango rom would help...no luck still having problems. So I came to the conclusion that a new SD card in the device was no gonna solve the issue. I Then downgraded the SPL and XSPL-ed the device and re-installed D7 and Storage Lock cab, unlocked the SD card and removed it from the device.
Now I had already received my replacement HD7 and all new accessories. I downgraded the SPL from 5.xxx to 3.xxx via the goldcard method. XSPL-ed the device and installed D7 and Storage Lock cab, unlocked the 16gb SD card in the device, removed it and then installed the 32gb SD card. Put it back together booted it, hard reset and the 32gb was acknowledged fine in the new replacement device. I then flashed Deepshining 7.8 to it.
Since I just removed my 16gb SD card from my new HD7 and the old one was still disassembled, I figure I'd give this SD card a try in it. I installed the 16gb to the old HD7 and put it back together, booted it, hard reset and the SD card was acknowledged just fine but the problem still persisted.
I though well for the cost of keeping the old HD7 it might be worth it, I inserted the SIM card in the device and it wouldn't work... Once you activate the new replacement device Asurion deactivates the old device, so that you can't use it or sell it to someone, so the device becomes useless other than WiFi. So I unlocked the 16gb SD card, removed it and the SIM card. Flashed the device back to stock Tmous rom, removed the battery and back cover plate. They only want the device and none of the accessories. I shipped off the old HD7 to them and have been enjoying my new device ever since... Plus I have 3 batteries, 2 - 16gb SD cards, 2 back battery cover plates, 2 USB wall adapters and 1 USB device cable now. Not bad for the cost!
Hello all,
Firstly, I hope this is the right place to put this thread. I did a search and did not find anyone else having this issue so I decided to put my post here. I am having a problem with my note 4 randomly restarting a few times every hour. It goes through its shutdown procedure and turns right back on. Occasionally it will shutdown and stay off. It seems to be software related, but I'm no expert on these things. I did however download 'Device Temperature' from the play store to check to see if it might be overheating. As far as I can tell it has stayed a cool 24-25 degrees Celsius (77 Fahrenheit) the entire time.
It does this at unpredictable times, whether or not the phone is in my pocket, in my hands, or laying flat on a desk with or without the charger plugged in.
I don't think I can take it back to Tmobile to have it replaced as I bought it from a friend a few weeks ago to use on cricket. This just started 2 days ago.
The device is SIM unlocked, but not rooted with stock everything. It's still in mint condition and to my knowledge has never been dropped.
Can anyone help?
More Information
I did a Google search for "Galaxy Note 4 Random Reboot" and I found some information saying to reformat my SD card or try doing a factory reset on the phone.
I tried both (I actually removed the SD card completely instead of just reformating it), and about a half hour later... boom restart again. FML.
Once again I turn to the wonderful folks at XDA for help. Thanks to all in advance.
Sounds like it could be bad eMMC flash memory. Go with your friend and have Tmobile replace it. Also get Square Trade insurance if you can.
Got it fixed
I called Samsung about the issue and after some brief troubleshooting they recommended having it reflashed at a samsung experience center. The closest one to me was in a Best Buy. I dropped it off, after explaining what was happening, and an hour later it was ready to be picked working good as new. I haven't noticed it restart even once since.
Samsung offered to replace the entire unit but it would cost me $28 for 2 day shipping (assuming that they had my model in stock). I will go that route if the issue returns. I'm hoping not to go this route because I already paid for this phone to be unlocked once - I'd rather not pay again if I don't have to.
I'll keep you guys updated if the rebooting issue returns again.
Also check to make sure the battery is properly seated and contacts are not bent/damaged.
railshot said:
Also check to make sure the battery is properly seated and contacts are not bent/damaged.
Click to expand...
Click to collapse
This. I kept having this issue with my Note 3 and could not figure it out. Eventually I just took out the battery, cleaned the contacts, put it back in, and it never had a random reboot after that.
Are you guys running any custom roms, or is it still stock?
Hello everyone,
I'm experiencing a pretty tough issue mith my beloved (and, so far, flawless) Nexus 6. It had root and a stock rom on it, 6.0.1 (MMB29V). I had unlocked the bootloader and rooted the phone right after buying it more than a year ago and I've been flashing new factory images a couple times (specifically when 6.0.0 and 6.0.1 were released). I usually do everything via Wugfresh's NRT, not because I can't use adb and fastboot, just because it works fine and I'm lazy.
Yesterday, while I was working, I used "Tiny Scanner Pro" to scan a document (legit copy bought on the store, as any other premium app in my phone) and it got stuck for a while, then a popup about Google Play Services came up. I dismissed it and another appeared, and it kept going like that. I was at a client's and I was in a hurry, so I took the pic with my tablet and forced the phone off. Later I turned it on, it seemed to boot regularly, but when the SIM unlock screen appeared and I entered the (right!) PIN, it said that no SIM was found, then the home screen appeared but after a while the screen went black and it started rebooting. Recovery (TWRP) and fastboot were working, so I decided to take it home and re-flash the stock rom: it had been a while since the last time anyway, a new version was out and the OTA update notification was getting annoying. I connected to my PC in recovery mode and transfered my pics and data via adb while I downloaded the latest stock rom (6.0.1 MOB30D). Then I user NRT to flash it (selecting "Soft-bricked/Bootloop" as current status). It appeared to work fine as it went through the usual copying and unpacking. Then, when the phone was supposed to reboot, it just blacked out. I waited a long time, in fact I went out and came back a few hours later, and it was still that way. Now it doesn't power up, no matter how long or hard I press any combination of the three buttons, adb and fastboot do not detect it in any way, of course, and it doesn't seem to charge either (i.e. I left it plugged to its original charger overnight and it still feels dead cold). By the way, the phone warranty shouldn't have expired, but I'm afraid it wouldn't cover this since it should still have the custom recovery and unlocked bootloader in its comatose body.
I've taken a look at similar threads but none of them describes the very same situation. Is there something, anything I can try to do before giving up? I hope somebody can help me. I thank you all very much in advance.
lupus
lupusyon said:
.... I'm afraid it wouldn't cover this since it should still have the custom recovery and unlocked bootloader in its comatose body.
Click to expand...
Click to collapse
Bricked!. When the phone is still under warranty send it for repair. Do not use arguments.
Just: phone will not switch on and does not charge.
Because this is a Nexus device, the custom recovery shouldn't affect your warranty. It is however, a moot point. The device is totally dead, and a call to Motorola is in order.
lupusyon, I had a discussion with Google about an 18-month-old Nexus 5 on which the radio had died - the "no SIM found" error that seems very popular. They asked me what I'd done to try to fix it. I told them that I'd tried several different radios, half a dozen different ROMs (not just Google stock), in short I'd messed around with it over a long period (it had been rooted with custom recovery pretty much since I bought it).
Response? No quibbles. "Here's a refurbished N5. Just send the broken one back in the enclosed pre-addressed pre-paid bag."
Go for it...
dahawthorne said:
lupusyon, I had a discussion with Google about an 18-month-old Nexus 5 on which the radio had died - the "no SIM found" error that seems very popular. They asked me what I'd done to try to fix it. I told them that I'd tried several different radios, half a dozen different ROMs (not just Google stock), in short I'd messed around with it over a long period (it had been rooted with custom recovery pretty much since I bought it).
Response? No quibbles. "Here's a refurbished N5. Just send the broken one back in the enclosed pre-addressed pre-paid bag."
Go for it...
Click to expand...
Click to collapse
I bought it on Amazon Italy Marketplace, I'm not sure if they're supposed to handle the thing or if I should contact Motorola. I'll just check with them first. Thank you everybody for the kind advice, I'll let you know how this turns out. :good:
I confirm what dahawthorne wrote above: it took them about a month but Motorola repaired my Nexus under warranty, no questions asked. It seems they replaced the Mainboard PCB.
Thanks everybody!