Database Users

[Q] eLocity just quit...won't boot up

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.

[NST] can't root after update to 1.1.2

In short: After update to 1.1.2, rooting methods don't work for me. Each time after root, Nook stuck on «nook» screen with 5 circles below (dot continue running until battery discharges completely, screen refreshes non-regularly), except 1st boot with MinimalTouch, which asked about signing-in and location services.
Any help appreciated.
Long story:
Some time ago, I've been beginning with NST 1.0.1, and rooted is successfully with TouchNooter. After it updated to 1.1, and I re-rooted it, successfully again, now with «Market & Setup Script Kit» (which uses uRamdisk-replacing method).
But I didn't turn off OTA update, just not to miss new firmware.
One day about a week ago, it ceased to boot, not going beyond «nook» screen with running dot in 5 circles. I did reset with holding left & right bottom buttons, but it didn't help.
When I booted noogie, I found apparent uRamdisk.old (left from prev. rooting) near uRamdisk, and renamed it to uRamdisk. Nook booted normally, allowed me to register, and let me use it as reader.
But still, I wanted to root.
Tried both touchnooter-2-1-31 and MinimalTouch, both with same result (not loading beyond running dot). Tried installing 1.1.2 in non-rooted mode, and updating again. With MinimalTouch, it boots to sign-in 1st time, but reboots when it should go to home screen. 2nd time an on, it does not boot beyond running dot.
Currently my nook is working, non-rooted, with 1.1.2 firmware. Each time I began from this state.

http://nookdevs.com/Nook_Simple_Touch_restore_to_stock
Haven't tried these but supposedly can revert you back to original firmware then maybe upgrade to 1.1, root, and turn off updates?
I tried the 3rd method on my unrooted nook that had 1.1.2, it claimed to work but version still showed up as 1.1.2.
Regardless I used touchnooter to root and haven't had any issues since. Still shows 1.1.2 in version info but it's rooted and running fine.

Well, I've used methods #2 and #3 several times, and it doesn't help (surprisingly).
I don't think there will be any difference with #1.
What helped me to go back is n2T-Recovery_0.1.img from that post, which initiated full restoration (and it worked). Once I also used full initial backup, from which I retrived some files to undo rooting. I didn't flash it back ever, because I am not sure it's done correctly, as its size differs from one stated in backup article, and is 1'962'934'272 bytes long (exactly same as size on disk).

funny, I've just rooted with uRamdisk_wireless_adb_init_1.1_1.1.2.zip. Now will try to install google apps.

[Q] Stuck on boot loop

I used manual nooter over weekend, everything has been working well, but I did have a hard time figuring out soft keys. For reasons I'm nott sure when I tried to use Nook color tools I could only get to BN tools, not the option for all settings which was originally there. I decided to power Nook off an turn back on as that often helps on my Bionic. Well, upon turning on I had the orange menu askin if I wanted to reboot, restore etc. I tried rebooting, was stuck on loop, powered back on and off, did a back up, tried to reboot again and stuck on loop. Do I need to do a complete wipe and start over? SD card seems to be working fine. Any thoughts? Everything else seemed fine, could use play store etc. I did download Firefox last night. thanks.
Updating, through another thread on this forum I went into CWM recovery, did a factory reset, cleared cache, wiped dalvik and rebooted. I think I am getting back to stock, Nook is trying to connect to WiFi, but my office router isn't showing up. Once I get past this, hopefully I can connect somewhere and try Manual Nooter again. Crisis averted, I think.
Last update, sorry for the panicky post. Was able to connect to Wifi, re-register Nook, then reinstall ManualNooter from SD card. Bootloop is gone, CWM recovery worked. After searching deep enough with the posts, everything is working as it should. Thanks for all of the info here and tolerating my Nooby panic.

[Q] stuck in android gear logo...any easy fix?

well here we go again. i push installed "gl tron" from the play store on my pc to my tablet. it showed it installed successfully. i then went to play "samurais vs zombies" and it crashed as it sometimes does for me. so i went to restart my tablet and now its stuck on the android logo with gears moving. last time it did this i tried random fixes and just made it worse and practically bricked it and some good guys here helped me get it up and running again. is there any easy fix for this not to lose all my data or make the issue worse? if not, what should i do to get it to work even if i lose my data? from what i understood last time was i had an issue in the data/media directory causing the issue. is that the case most likely this time? was it from the push install as i suspect, because it is very similar to what happened last time? i never got to do a proper cwm backup of my rom and data as i got an error and never fiddled with it again. some ideas or pointing in the right direction would be very helpful. i also would like info on how this could happen and how android works in order to avoid this in the future. thanks so much.
specs:
acer a500
skrilax_cz bootloader v8
cwm 5.5.0
lightspeed 4.8
i also have my cpuid and sbk info saved.

Can you go to recovery. "clean up tab" then reinstall your ROM?
This won't touch your data and - may - get you running again.
raotheconqueror said:
well here we go again. i push installed "gl tron" from the play store on my pc to my tablet. it showed it installed successfully. i then went to play "samurais vs zombies" and it crashed as it sometimes does for me. so i went to restart my tablet and now its stuck on the android logo with gears moving. last time it did this i tried random fixes and just made it worse and practically bricked it and some good guys here helped me get it up and running again. is there any easy fix for this not to lose all my data or make the issue worse? if not, what should i do to get it to work even if i lose my data? from what i understood last time was i had an issue in the data/media directory causing the issue. is that the case most likely this time? was it from the push install as i suspect, because it is very similar to what happened last time? i never got to do a proper cwm backup of my rom and data as i got an error and never fiddled with it again. some ideas or pointing in the right direction would be very helpful. i also would like info on how this could happen and how android works in order to avoid this in the future. thanks so much.
specs:
acer a500
skrilax_cz bootloader v8
cwm 5.5.0
lightspeed 4.8
i also have my cpuid and sbk info saved.
Click to expand...
Click to collapse

i went to recovery but could not find a "clean up" selection. am i missing something? last time this happened, i tried to do a factory reset and all i got afterward was a droid with exclamation mark on his chest. from what i understood is that my a500 did not have a proper recovery partition which left my tablet nearly bricked. that's what i surmised from the info i read. thanks ta-wan.

wiped data/media and it set me back to honeycomb. i rebooted into recovery and installed lightspeed 4.8. lost all data but whatevs, my fault for not backing up. wont happen to me again...

Will a Stock Update Brick a Rooted Device?

So in the ongoing saga of my nook having a wonked screen that won't respond to outside stimulus I have to ask.
If I download the stock 1.2.1 update and have my nook try installing that. Would it brick?
Thought process is 'i haven't tried taking it back to stock. so maybe that'll trigger something.'

I was able to update my rooted device from 1.1.2 to 1.2. The after re-rooting 1.2, I was able to take it to 1.2.1. I lost root every time, but I did not brick my device. (Of course my device was functioning properly at the time of the upgrades.....)

I've been told that rooted Nook Simple Touch can't be updated, you have to restore official snapshot of the system (or factory defaults) to update it, then re-root.
I've also been told that rooted Nook Simple Touch can be updated, but you will have to re-root after updating.
Personally, i've updated first (to 1.2.1), then rooted with NookManager.

If your NST is rooted it will not run update_version.zip, you will have to restore to factory settings by 8-times disrupted loading, followed by loading and pressing and holding two lower buttons once you see the white circles at start-up screen. Once you've restored to factory settings the NST will be able to run the update_version.zip. Nothing to worry - it'll go fine just make sure NST has enough charge, more than 25%. The updating process may take some time, just relax and go have some tea (coffee, beer, cigarette etc.).

If you can get adb running a much simpler/more reliable way to trigger the factory reset is with echoing the value to the file. granted, I can't remember the exact command at the moment

Yeeeaaa My folks took the thing off to a shop. Honestly kinda doubt they can do anything, not without more or less replacing the main board and the screen (so might as well just get a refurb unit and be done with it.)
But thanks for the info guys!