Related
When I try to boot my nook, I get past the "Touch the Future of Reading" screen but get caught up on the "n" loading screen.
I've tried to interrupt the boot process physically 8 times to no avail.
I've tried to SSH in the 8 failed resets script, nothing.
I can't boot the nook far enough to be able to shell.
I tried to do a factory reset but it tells me "install failed", and has an image of a nook with a red circle and while exclamation point.
I installed Nookie-Froyo from flash and tried to use that but soon realized I was over my head.
So finally I called BnN to see if they could do something and they offered to replace it. If I send them this wonky device, will it raise some red flags in their system?
I would say try some other methods before returning it if possible. I have read others on the forum in the same situation as you and they have gotten it working again. It will take some time for someone with more knowledge to respond, but I think it is worth it.
If you return it it seems like you might have a high chance of getting one that has hardware/software issues from what many have posted. I would try to stick with what I had even if it took a week of getting help from the forums.
Have you tried booting the AutoNooter 2010-12-25 ? I have heard some boot the sd card and then they can ssh to 192.168.2.2 and do some recovery work on the nook, like I said I am not experienced in this but I have read other's posts on success stories
I've tried the ssh method and it would never make it past the n screen. I've also searched the forums and haven't seen anything about an "Install Failed" screen. If someone has seen something about that and could point me to it, I'll try anything.
If you see an N on the screen it means it is not booting from the we card. Maybe the we card wasn't written correctly? Was this rooted previously?
Sent from my NookColor
It was rooted and then stopped working after I left it in a very cold car all night long. I don't know if that's what caused it, but until I figure it out, correlation will equal causation.
As for the card, I reformatted and re-imaged it 3 times in the process of trying to re-root it; once with auto-nooter for 1.0.0 and twice with 1.0.1.
This is crazy, I have the same issue right now....it's stuck in the boot screen. Mine rooted perfect today, apps installed from market with no problem, I noticed the battery was low but wanted to reboot it after I noticed Youtube stopped working, I shut it back down and restarted it before I put it on a charger.....it hasnt rebooted since.
I did get it to boot into clockwork a few times, I did a factory reset from there but it still didnt help. Anyone have an idea? Did I permently brick this thing?
hey guys, I don't know what's going on with my S7 but yesterday was working fine and out of nowhere everything started to FC! From twitter to "Google Services Framwork", Gmail, browser, tweetdeck, calendar, voice, I can't pretty much use it anymore, I haven't done any new app installations so i don't know what's wrong! is it just me, or anyone else having this problem??
Any help will be much appreciated!
Thanks
That has happened to me 4 or 5 times. It's like half of the device gets erased but the apps are there. Everything force closes. I end up having to erase the device and re-install everything. Reboot into recovery if you can't figure it out and format the system and data. For some reason when i do that, i keep root. Not entirely sure how that happens, but one less step for me. I think root is power and one of the volume buttons.
djdanska said:
That has happened to me 4 or 5 times. It's like half of the device gets erased but the apps are there. Everything force closes. I end up having to erase the device and re-install everything. Reboot into recovery if you can't figure it out and format the system and data. For some reason when i do that, i keep root. Not entirely sure how that happens, but one less step for me. I think root is power and one of the volume buttons.
Click to expand...
Click to collapse
ha! i remember I already did that. After the Update we had, and I exchanged mine for a new one I decided to stay with no root (i don't know why! lol) so I guess I'll reset everything and go back to root I figured at the end I was gonna do that, but I was trying to see if it was just me or there was a fix
thanks man!
ok, so since yesterday I've been trying to factory reset the DS, and when it boots back on, everything stays the same!
I'm a little confused now, if I take a picture and I turn the tablet off, when I turn it back on, the picture disappears. Same thing happens if I move widgets, delete or create new ones on the screen, they go back to as the configuration was on friday night! GV not working, and the last message that shows there, same thing, shows the last one on friday. I don't know what can I do.... should I call dell??
duck tape and dynomite
stupid thing started crashing yesterday FC this and FC that ....cant restore it as i no longer have write access to the internal sd card
1) tried nv flash
2) tried restoring from clockwork
3) tried pushing files through adb
4) tried fastboot ....
if i didnt just dump money into this thing id blow it up ......
any help would be appreciated.......any tips to fix it or kill it completely so i can get another one
actually deleted all of the files on internal sd card and uninstalled every program on the device looked completly stock ....rebooted it and it went back to how it was yesterday ......theres gotta be a reason why other are having the same problem that started on the same day .....maybe dell pushed an OTA update and screwed us ......just a thought cause mine was fine till i went 4g yesterday so my sis could post facebook pics ....not sure but hope we can figure this out
Samething happened to me
Hi, did you ever find a solution? my streak 7 was ran out of battery, before it shut off, the screen started flickering and then it turned off. after it came back on, it looked like it was fine, everything looked normal, but then everything started force closing, haven't found a solution
jz83 said:
Hi, did you ever find a solution? my streak 7 was ran out of battery, before it shut off, the screen started flickering and then it turned off. after it came back on, it looked like it was fine, everything looked normal, but then everything started force closing, haven't found a solution
Click to expand...
Click to collapse
I'm running stock, and I discovered the hard way that you can't let the S7 battery run all the way down. The S7 will not power itself down in time. I had the same issue, and the only way around it was to do a complete factory reset, using the menu button from the main screen. I think the reset is in the "About" section, but I don't have my S7 with me now.
Being used to WM6, which powers the device down at 5%, I was not expecting the device to do this, but there it is.
dell streak 7
im not sure if I am the only one with this issue you but becareful with the streak 7 mine well both of mine wont charge properly and the newest one wont charge at all. i have to send it back to dell for them to fix it. Im not sure what cause this but my only advie is to never use a different charger for it only dell chargers. Im guessing that it messes up the battery callibration and then it gets really hot when charging
Sharing time!!
I did something quite stupid today and, in the interest of both comedy and warning, want to share it with the world.
In my rooted glory I began to think back to the V6 supercharger script that my Droid1 loved so much.
Long story short it did not do well on my droid and I ended up with a boot loop at the "Droid" soundbite. Hard to hide your mistakes when your phone is screaming every 5 seconds. All of the boot loop fixes failed.
Factory reset cleared up the boot loop but thanks to some .apk cleaning I am now stuck with no home screen. Installing a home screen replacement has not helped yet, but at least I have adb and still have root so some .apk moving from the backup directory should get me running in an hour or so.
Feel free to laugh knowing I have been hacking phones since my old xv6800. Also make sure you know the risks when you play with the file system on your phone.
Thanks mate, I feel for you. Yesterday I tried to update my Droid to 5.6.890 but first I had to Unroot it with Petes Motorola Root Tools and restore the /system/app folder. Unfortunately I left the downloaded apk zip in the restore folder which has been also restored to /system/app.
Then bootloop. And drooooooooooooid, drooooooooooooooid, droiiiiiiiiiiiiiiiiiiid. ^^
I had to manually root it, this thread helped http://forum.xda-developers.com/showthread.php?t=1236465
Then I restored /system/app again, but correctly this time.
Finally I could start the update and everything was working again...
Anyone who has a bricked DROID 3 phone (Verizon only), I may have a solution for you.
Requirements:
Windows platform
7-zip installed (and know how to extract files)
ability to follow all instructions exactly
willingness to factory reset/lose data on their phone
This unbrick method is NOT guaranteed to work, but it's very hopeful for most situations where other methods aren't working. If you are in desperate need of a fix, send me a PM and I'll link you some files to try.
Lastly: I will not be walking through anyone step by step on how to run this procedure -- the included instructions should be more than enough for most people. If you read the instructions and are thoroughly confused, then this fix isn't for you.
Almost back up and running now. Thankfully Marketplace pushed some apps and then notified me about it so I could open up the marketplace and install ADW. Once I got home back it was just a matter of reinstalling and rebuilding.
Oddly my Social Networking widget is no longer working correctly. A shame but only a minor issue overall.
Oddly the bootloop fix instructions you listed did not work for me. ./adb devices showed an entry but no info and told me I did not have any permissions on the device. I am running on Linux so it may have been a driver issue of some kind.
I'm sure what happened to the damn thing the other day, but.
I put my phone into Sleep Mode during a morning of hunting and when I tried to wake it back up it wouldn't respond. It had actually done this before, so I wasn't too concerned. It seems to be an issue with the leaked OTA.
So I pulled the battery, powered it back on, and stuffed it back in my pocket and drove 20 minutes back home. When I tried to check it afterwords it wouldn't wake up again; stuck at black screen.
Pulled the battery again, powered on and waited... and waited... and waited. After several minutes it would reboot again.
Sooo I plugged it into my computer and started to try to figure out what the hell happened. The logcat gave me no good indication as to what might be the issue, it just seemed to hang right after booting.
I deleted my replacement home (Launcher Pro) and that got me a little further. It would boot to the lock screen! But it would never respond to my inputs.
I resorted all system apps. Same thing, not responding, stuck on lock-screen in airplane mode.
I unrooted then re-installed the OTA leak. No change.
So I finally caved and decided to try a factory reset, which if failed, could almost totally screw me out of ADB access or worse.
But thankfully it totally worked! It booted right up and I was able to complete every setup screen without issue. Rooted, Titanium restored my apps and a pinch of data and I was back in business in 30 minutes!
Now I make sure that I never put the phone into Sleep Mode.
I have Safestrap installed so I know that is a BIG no no... I have been using Safestrap, ROM manager premium, and ROM toolbox pro with Eclipse 3 ROM for a long time now and have done countless backups, and have never had that happen.
I also have been getting the triangle with "!" and have to reboot from the blue menu to get to safe strap and then from there I do a backup. I have also noticed that while I am navigating in Safestrap, the curser overshoots, ie I will click 3 times to get to lets say "reboot" and it overshoots by a couple menu items.... no biggie but new behavior and seems odd.
Lastly for the past couple weeks, starting out of the blue, my battery % is not acurate and I have tried EVERY battery calibration app in the book, I have erased batt stats and deleted battery.bin file to no avail.
I have done a complete SBF wipes(twice) with 906 leak and then do the OTA update with no problems, I have done 2 factory resets.
I have a feeling I need to swap phones but I don't think Verizon is going to have anymore Droid 3's and I can not afford another phone. This one is about 9 months old. PLUS I would like to FIX the problems and learn. Not just trade it in and not learn what was wrong...
OH yah, I forgot, about 4 weeks ago, my signal/radio would go out and it would say I was in airplane mode but there was no airplane icon showing..
Other then that, I really do love this phone!...really!.. and yes I have done several factory resets and have 3 batteries...
A million thank you's for even just reading this...
The triangle with the exclamation point lets you get to stock recovery.
Calibration apps don't do anything to calibrate the battery, nor does deleting the battery files. The way you calibrate is to fully charge it then let it run down to the 15% warning then charge it fully again. If it still shows wrong after that, it's probably a bad battery or something.
Sent from my DROID BIONIC using Tapatalk
Hi Linuxgator,
Thank you for reply. The thing is I have never been taken to that screen via trying to do a nandroid. It used to, on many occasions, take me to the Safestrap option screen(left side recovery/right side reboot). The only way I have ever gotten to the triangle was with a power button/M key combo.
**Update on the ROM manager issue... I saw that there was a "manual flash override" in the settings that let me be able to use safestrap... whew for at least one issue...
Hi hello howdy!
I'm going to skip the foreplay cose the action here is pretty weird and you'll want to get right in, trust me.
I've a Galaxy S3 Mini GT-8190L, that reboots itself, after it has booted up, and I entered the sim pin and lock pattern I've from seconds to 5 min of grace before the phone restarts itself. I have tried two different batteries and the problem persists. I went and decided to rule out hardware problems (power bttn) and after some tinkering, ruled that out too. So now my best guess is firmware.
The phone is not rooted, does not have recovery mode installed, and is running stock 4.1.2 jelly bean with TouchWiz, no mods, no hack-y stuff, your old regular samsung s3 mini.
I tried installing CM11 with odin, and didn't work. But not because odin threw an error, no, that went on perfectly according to the program. But when the phone booted up, the rom was still stock, nothing changed, and it rebooted itself briefly. Weird. So then I thought "well, maybe at least the recovery mode is there now" since it supposedly was a package install. But no, when I tried to boot onto recovery the phone gets stucked on the boot screen with the samsung brand and model of the phone, and then restarts itself, this happens like four times and then the phone boots normally, the OS starts, everything loads and then goes on to restarting. So this was not a solution either.
Next I though, well lets just install the recovery, no, that didn't work, odin said that the install was successful but it was not. Tried with odin 3.04, .07 and .09, tried CW and TWR, neither of them load, as before, when trying to boot to recovery the phone displays the splash and the reboots itself like four times before starting up the OS.
Next I though well, lets try to root this thing, at this point I was just trying anything to see if anything sticked, but nothing, tried SuperOneClick, and no. Wanted to try TowelRoot but that uses an apk. I tried vRoot against my best judgement, but that didn't work, but not because of the reasons you might think, it did install, the phone managed to stay on for enough time for it to get running, but when it restarted, there was no app there, it was as if nothing was installed just a few second ago. I thought "huhh? That's really weird". So I went and did some testing on this matter.
It turns out that no matter what I do, I can install an app, delete 5 apps, change settings, and nothing sticks, when the phone restarts it goes back to the way it was, its like the phone lost the short memory and its like that Adam Sandler and Drew Barrymore's movie, 50 First Dates. The phone rollsback to the state it was when everything began.
I even tried to change something quick, and restart myself the phone to see if that would make the change stick, but no, that didn't work either.
So, I came up with a brilliant idea, look up a similar case on internet, 'cose you know, it has to have happened to someone else before me. But this is so weird that looking it up is a challenge by itself. I tried a few things here and there but nothing does it. So now I'm here writing my sci-fi story looking for some feedback on how can this story be ended without killing any of the characters, I want everyone to survive and work again. You know, happy endings.
Any ideas on what can be the problem? Seen anything like this before?