I have been running my a7 with dexter's mod 1.4 for about 1 1/2 weeks...everything has gone well. This afternoon I turned on the device and it failed to complete boot. The word Android would come up and then nothing. I tried to reboot, reset, but device would do neither...nor would it turn off completely. I kept trying to take it into recovery mode and then after several tries was able to wipe, do update again, and get everything back as before. What would cause this and should I look for this to happen again? deepmagic
My a7 was running well for about a week since it quit...but today when I booted up device, it failed to recognize sd card...same card used for updating to mod 1.4...same card I've been using to listen to my music, etc...but now won't recognize...I've tried two different micro sdhc cards..formatted, reformatted, but device continues to display mount sd card...all else works fine! Does anyone have any new ideas? I can't even reinstall mod since a7 can't read my cards. Thanks for any input that would be helpful. I understand these issues are ongoing for many out there...what to do?
deepmagic said:
I have been running my a7 with dexter's mod 1.4 for about 1 1/2 weeks...everything has gone well. This afternoon I turned on the device and it failed to complete boot. The word Android would come up and then nothing. I tried to reboot, reset, but device would do neither...nor would it turn off completely. I kept trying to take it into recovery mode and then after several tries was able to wipe, do update again, and get everything back as before. What would cause this and should I look for this to happen again? deepmagic
Click to expand...
Click to collapse
Mine has hung on a black screen on me. Seemed that it didn't fully come out of sleep mode.
I was able to recover by holding the power button for 15 seconds to hard power down. No data loss.
deepmagic said:
I have been running my a7 with dexter's mod 1.4 for about 1 1/2 weeks...everything has gone well. This afternoon I turned on the device and it failed to complete boot. The word Android would come up and then nothing. I tried to reboot, reset, but device would do neither...nor would it turn off completely. I kept trying to take it into recovery mode and then after several tries was able to wipe, do update again, and get everything back as before. What would cause this and should I look for this to happen again? deepmagic
Click to expand...
Click to collapse
Exact same thing happened to me this morning. Tried to reset - not happening. Hard powered down. Don't have time to try anything else right now. I'm new to the forums and new to android. Wish me luck! I've been loving my A7, and much appreciation to Dexter and all the other knowledgeable hackers/modders/posters.
hey the same thing happened 2 me twice. Once the first day after i got it, since i had only had it for 1 day i wiped it reinstalled dexter's mod 1.41 and it worked. First app i installed was backup root. Now, a week later the exact same thing is happening. This time i dont want to wipe it because of all of the apps i have installed, games ive played etc. Any ideas? Could we just try reinstalling dexter's md without wiping? Or wiping reinstalling and recover from a backup?
Also have you installed busybox? I had just installed it both times before it failed to turn on. Maybe its just coincidence but you never know..
-D
Thanks to anyone who can help! and also thanks Dexter for all your hard work as well as everyone else that has contributed to the elocity, im lovin it! (when it works )
success!!!!
I got it to work! I don't have a permanent fix but if it happens again just boot into recovery and reinstall the dexter's mod update 1.41 and it works again! No wiping required. This isn't a permanent fix but it will work until we find one
-Dylan
Hasn't happened to me (yet) but I didn't upgrade to the newest ROM. I'm still using 1.3and it has been very stable. Only issue I've had was when I tried to use Killswitch to go to sleep mode when the cover is shut (great idea) but it didn't work and froze all except the live wallpaper. Weird.
Good luck, guys.
in the event it does happen to you, you might want to check out my apx thread for reflashing the factory firmware if you can't get your tablet unstuck. theres alternatives if you don't want to get stuck again.
The method you outline seems so complex...way above my abilities, but makes me wish I had followed though on some early programming training opportunities. That was the road not travelled.
okantomi; while i wouldn't encourage others to follow thru with procedures they fear would cause more harm, i would mention that if you google up my nick you'll find i've been able to do much w/ android software and devices while not knowing anything about programming. if i can do it, anyone can. i just wanted some themes for my phone.
i'm just an android hobbyist by night (and when i get a chance during the day), and a computer tech by day. no programming expertise, but i can reasonably reverse engineer and port software and components using simple file managers like ztreewin(trialware).
don't be mistaken that the folks out there providing you solutions necessarily know anything about programming or software development. just how to chef up files at different levels. i understand this doesn't go for everybody.
Thanks for the encouragement. I'm impressed with what you've been able to do. It is also nice to read upbeat comments about the A7. There is something sort of special about a device that you really almost have to build yourself... putting so much into it... biting your fingernails to nubs with each ROM flashing. You don't get as attached to any device that is 100 percent complete right out of the box, though of course there would be a lot less aggravation.
Last night I Unrooted and restored to bnn 1.3. Now when I plug in the nook to my windows 7 pc it doesn't recognize it. Last week I installed ADB and drivers (even though I never got it to recognize my device on cmd). I thought maybe this is the problem, but yesterday I took my friends stock 1.3 and did the update from my pc for her, which is what made me want to convert to stock and test out 1.4
any ideas? the threads I found with this type of thing happening were rooted still.
cancel that, after messing around i figured out to uninstall adb interface and that worked. hope maybe this will help someone else.
Hi all. I used to mess with my Nook Color a lot around a year and a half ago but recently was just using it to read and occasionally browse. I'm 99% sure I was working with just a nook which was used with manual nooter, so that I had the Google Play store and Zeam launcher with stock B&N as well. I was having issues with things "not being able to update" so I tried to mess around, only realizing too late that I wasn't really interested in cm10 and wanted to stick with zeam. Since then I've been trying to get back to how I started but I'm failing miserably. I've so far tried wiping/factory resetting my device. Installing cm7 from zip, resetting everything using the guide here and installing 1-4-1 cam oc zip from here and still I fail. I can get into the set up screen, but when the device will not find any wifi signal and then freeze without allowing me to type it in under "other". Honestly I'm not sure what else to do now. I just want my nooted device back -__-.
Please let me know if I can submit any more information that can help solve this problem. Thank you for your time.
I'm literally infinitely stuck staring at this screen.
Managed to fix everything. Used section A15. Enjoy anyone who ran into similar trouble.
Hey everyone. I got my replacement N6P in the mail today, and I am needing some advice. I went through the typical setup for it. Bootloader unlock, decrypt, root, etcetc. However, I am running into an issue where I cannot copy anything from my computer to the device. I am getting an error that states "The device has either stopped responding or has been disconnected." I dug around XDA a bit and found a bunch of possibilities, but none of them resolved my issue. I have tried just about everything I can think of except for reflashing to stock and starting again. I am hoping it is an easy fix, but I think a reflash may be needed. Has anyone else seen this before, and does anyone have any ideas for me to try?
EDIT: I have done literally everything I can think of, including flashing back to stock. Tried machines running Windows 10, 7, and Ubuntu. Tried three different cables. Absolutely nothing is working. However, I can push and pull files fine. No clue what is causing this.
EDIT2: It has something to do with MTP. Certain filetypes transfer without any issues, but most do not. I can get around this by changing the extension of the file before sending it over, then changing it afterwards. My previous N6P never had this issue. Is there anything that I can do to resolve this, or am I stuck with network transfers and renaming junk?
So I was given a Samsung I337 from a friend and upon Kingrooting it I noticed the stability started to degrade.
So I performed a factory reset, and then jumped back in. Noticing google no longer allowed access to the play store.
So I rooted again in an attempt to sort out my Host file, with the intention of "Unrooting" later on.
Everything seemed to work fine, then my phone reset, and stopped at the AT&T logo.
Is it salvageable, or should I just toss it in the bin?
I would love to be able to get to a point where I could just use it, my intention was to eventually put Cyanogen on it.
It's running Android 5.0.1 that was the last thing I remembered while in my About Phone settings. I do not believe USB Debugging is enabled, considering how many times I've factory reset it trying to solve the problem.
I also for some reason can't get MTP Device drivers to install on my PC. 64-bit Windows 7.
ToastyOats said:
So I was given a Samsung I337 from a friend and upon Kingrooting it I noticed the stability started to degrade.
So I performed a factory reset, and then jumped back in. Noticing google no longer allowed access to the play store.
So I rooted again in an attempt to sort out my Host file, with the intention of "Unrooting" later on.
Everything seemed to work fine, then my phone reset, and stopped at the AT&T logo.
Is it salvageable, or should I just toss it in the bin?
I would love to be able to get to a point where I could just use it, my intention was to eventually put Cyanogen on it.
It's running Android 5.0.1 that was the last thing I remembered while in my About Phone settings. I do not believe USB Debugging is enabled, considering how many times I've factory reset it trying to solve the problem.
I also for some reason can't get MTP Device drivers to install on my PC. 64-bit Windows 7.
Click to expand...
Click to collapse
It is salvageable.
You can find your answers in here and here.