Related
It says only ipl 2.25.0001 and spl 2.25.0001
I try a hard reset, but when it asks me to confirm by pressing SEND, I press SEND and nothing happens.. press any key and nothing happens, just sits there saying press SEND to confirm...
I tried flashing Cingular/AT&T's rom on to it, it was successful on the screen, but after rebooting, just went back into the 3 color screen...
Does anyone have any suggestions?
Additional info
I just wanted to add, I have searched threads here on xda-dev and other sites, and have found similar issues - normally the other issues have been resolved in one way or another involving a hard reset, which my phone will not complete. When it asks me to press send, the phone freezes at that point and does not accept any key entries (except reset). I would really appreciate any input. I also have a theory-that I may attempt this evening-If you hold the camera button down and reset, it brings up the boot loader screen (if my information is correct)... could my problem be caused by a faulty camera button? Maybe internally the button is remaining closed, which could prevent it from doing anything on a reset outside of the boot screen? Any engineers around that may know this? I am going to attempt (hopefully with low heat) to remove the button this evening... possibly even repair or replace it if the phone works with the button removed...(these thoughts are based on my phone being dropped in the sand at the beach...maybe a grain of sand worked it's way into the camera's button housing and is holding the contact closed)
problem's almost fixed
well thanks for no advice... i desoldered and removed the camera button (button 3). powered it on and the phone works. I reprogrammed the camera to button 5. (i also loaded a new WM6 rom and some other stuff) The last time I opened up the phone, I broke the itsy bitsy super micro tiny lock on the keyboard ribbon cable socket... so now my slide out keyboard doesn't work. I installed a full screen keyboard and set it to the messaging button (button 1) - the messaging button still brings up messaging with just a touch, but a long hold brings up a full screen touch keyboard that works fantastically!!! I am going to dismantle the very tiny micro switch and repair it, then resolder it back on the mainboard to make my camera work like it should again...and find a way to get the keyboard ribbon cable to lock into the socket...then my phone will be as good as new!
umm... thanks???
well congratulations on getting it working again.
tiny switch
I have taken the tiny little switch apart without breaking anything... one tiny grain of sand stuck under the button pressing on the switch plate... now i have to find a way to put the little switch back together... then attempt to solder it back onto the board without over heating nearby components. I have been playing around with Byka's cube... took a bit of tweaking to get it to work well.... not sure if I want to keep it or not... I have been trying to find htc cube, but no luck outside of a rom... which I may consider...but I just spent the past week reinstalling all of the software I use... Would like to just design my own windows for my phone if I had the time... Been working on an ion motor for an electric car...
I would like to thank everyone here at xda-dev. for all the information. Could not have learned so much, so quickly, if it weren't for this site.
oh... and I am using an 8125 (G4) with Faria Crossbow
Have the same problem...
Hi!
I have the same problem (but I don't have much tech know how).
It all started when phone got wet (inc. in battery compartment).
My phone would not soft reset beyond the Bootloader, unless I leave the battery out for a few hours. Then once it loads up, after a short amount of usage 2 things happen: 1) every time I would turn it on (or get a call) it starts in Camera (you didn't report it but you must have had the same experience). 2) the buttons don't work properly.
It finally dawned on me the camera button might be stuck, I set the button to "none", and no more more automatic camera. I still need to free the button altogether as still causing button freezeup and also allow soft resets.
I don't know much about soldering.
Any ideas?
Thanks
So, this is what happened:
Rooted it yesterday with Indirect's method, installed the gapps and Go Launcher. I modified my build.prop settings to have the 160 density to help more apps be compatible with my NT. Today I have been working on building my app library, then this happened!
I attempted to download a flashlight app to get the screen to come up completely white. It installed and I opened it, the screen came up blank and a pop up let me know the app had become un-responsive. I force closed it, then un-installed it. I went back to the market, and attempted to look at (not download) another flashlight app. Google market then became un-responsive and I force closed it. I re-opened market and tried twice to click on different flashlight apps to the same effect: google market would become un-responsive.
After FC'ing the market the last time, I tried to turn off the nook (to reset and clear the issues). It gave me the shut down menu and notification. The screen went to black, but the screen is still on. (lit) I have tried pressing the power button, holding it, and hitting any other buttons but it gives no response. I tried plugging it into the computer, but the drive does not show up. It does recognize it in my device manager, however.
Thats all I can think of for now. So a warning: Don't download a flashlight app.
Anyone encounter a similar problem? Anyway of hard-shutting down the device (like pulling the battery?) Any way of re-loading the device?
I've locked the NC in the same manner. Holding both the power and the n for up to ten seconds always shut it down, and it always came up functional afterward.
Mine has locked up on occasion as well. Hold down the buttons as described will indeed force ot off, then turn it on like normal. However, it sometimes seems like 20 seconds for me.
Mine is not rooted btw.
Sent from my Nook Tablet using Tapatalk.
bogatyr said:
Mine has locked up on occasion as well. Hold down the buttons as described will indeed force ot off, then turn it on like normal. However, it sometimes seems like 20 seconds for me.
Mine is not rooted btw.
Sent from my Nook Tablet using Tapatalk.
Click to expand...
Click to collapse
Mine has locked up like 5 times so far. It's kinda scary but it seems to always come back ater 5 mins or so.
I could go for some bricking. Do I just have to edit the value to 160 or is it more involved than that?
Sent from my BNTV250 using xda premium
It was hard to brick the Nook Color, so I think it is the same for the Tablet. Unless you drop it and the internal is damage, you can always do factory reset even if the screen look dead.
succulent said:
It was hard to brick the Nook Color, so I think it is the same for the Tablet. Unless you drop it and the internal is damage, you can always do factory reset even if the screen look dead.
Click to expand...
Click to collapse
How do I do a factory reset with a unresponsive nook? Do you have a thread Link?
tkwesa said:
How do I do a factory reset with a unresponsive nook? Do you have a thread Link?
Click to expand...
Click to collapse
First thing is to make sure your device is charged for 30 minutes.
Use soft reset if you can power on the Nook,
Turn off the device completely, and then hold down power and “n” button at the same time, until you see the logo.
Use hard reset if your Nook looks dead. Won't turn on and just display a black screen,
Hold the power button for 10 seconds and then release it. Wait a couple seconds. Repeat the steps until the screen turn on. It'll take around 18 times because it turn the the device on and off 9 times while interrupting the boot sequence.
JUST AN IDEA..
Its just an idea from me as i don't own the device..
I think your issue is not because of browsing some flashlight apps but is because of the modified build.prop file (I guess)
And if it is due to modified build.prop file, i'm not sure whether or not a factory reset solves that. But give it a try.. If it won't solve the issue then you might need to find a way to replace that particular file to stock in your device in its current state. Or giving the device to service center or flashing the stock operating system should solve it.
By gosh, It's alive! I let it discharge until it was dead, recharged it and its back!. If it freezes up again, I hope that forced power down will work. But so far, its all good. No problems. Thanks!
Ok I did something, and its got me worried. I tried to modify the build.prop file, rebooted, not it's stuck on the nook by Barnes & Noble screen, and it flashes & scrolls the READ FOREVER slogan, over and over. Seems stuck on something. Any ideas?
reverenddak said:
Ok I did something, and its got me worried. I tried to modify the build.prop file, rebooted, not it's stuck on the nook by Barnes & Noble screen, and it flashes & scrolls the READ FOREVER slogan, over and over. Seems stuck on something. Any ideas?
Click to expand...
Click to collapse
Reboot 10 times. Hold power button till it turns on and keep holding till it turns off. Rinse repeat 10 times then on the 11th let it boot normally and it should kick into factory reset.
I modified the prop.build as well and got that perpetual boot. A soft reset did not work so i had to to the N/Power/RepeatX10 for a factory refresh.
A simple reset will ask to wipe the data, where a factory reset wipes the device and it displays a large green down arrow in a box when you get to it.
I did the prop build thing as well.
I did a factory reset because it only goes to the read forever white screen then goes black. But factory reset does not help any. does the same thing. Is there any way to reset the build.prop file to the original? I do did leave a backup of prop.build I also did do a mod of the ro.sf.lcd_density to 160 that may have been the problem.
Will any reset set the original prop.build?
I seem to read that B&N has some kind of boot micro sd that can reset?
Would going the A B&N store help any?
bonusweb said:
I did a factory reset because it only goes to the read forever white screen then goes black. But factory reset does not help any. does the same thing. Is there any way to reset the build.prop file to the original? I do did leave a backup of prop.build I also did do a mod of the ro.sf.lcd_density to 160 that may have been the problem.
Will any reset set the original prop.build?
I seem to read that B&N has some kind of boot micro sd that can reset?
Would going the A B&N store help any?
Click to expand...
Click to collapse
If you do take it to a B&N store they will know that you have a rooted device, and probably will not help you.
Edit: Probably more like "may" know you have a rooted device.
bonusweb said:
I did a factory reset because it only goes to the read forever white screen then goes black. But factory reset does not help any. does the same thing. Is there any way to reset the build.prop file to the original? I do did leave a backup of prop.build I also did do a mod of the ro.sf.lcd_density to 160 that may have been the problem.
Will any reset set the original prop.build?
I seem to read that B&N has some kind of boot micro sd that can reset?
Would going the A B&N store help any?
Click to expand...
Click to collapse
There are two different kinds of resets one is a reset the other is a restore.
Please hold down the N and Power button on starting the devices, and do this 10 times. This will cause the device to power up and then power down after getting to the bootloader (the N screen). This will then trigger a factory RESTORE, which will wipe all data, including build.prop.
You don't have to cycle 10 times for a restore. You only hold down the power button until it starts up then release while continuing to hold the n button and it will take you to a restore menu and press the n again. I think by continuing to hold down the power it just continues to turn on and off.
I just had to do a reset because it was boot looping. I changed the framework-res.apk. The power+n button wipes data, but doesn't do a factory reset. Hold the power and volume up and down buttons together. Right as the black screen dims let go of the power button and it will wipe data then do a factory restore. I just did this and it worked. Hope this helps.
dds517 said:
You don't have to cycle 10 times for a restore. You only hold down the power button until it starts up then release while continuing to hold the n button and it will take you to a restore menu and press the n again. I think by continuing to hold down the power it just continues to turn on and off.
I just had to do a reset because it was boot looping. I changed the framework-res.apk. The power+n button wipes data, but doesn't do a factory reset. Hold the power and volume up and down buttons together. Right as the black screen dims let go of the power button and it will wipe data then do a factory restore. I just did this and it worked. Hope this helps.
Click to expand...
Click to collapse
This is only a factory reset, and will not wipe the /system folder, meaning any changes that you have made that are preventing your device from booting up will most likely be there still.
can someone post a regular build.prop file for download? i overwrote mine and now my backup is also the modified one.
tkwesa said:
By gosh, It's alive! I let it discharge until it was dead, recharged it and its back!. If it freezes up again, I hope that forced power down will work. But so far, its all good. No problems. Thanks!
Click to expand...
Click to collapse
Buddy, but how did you discharge the NOOK ?
I installed Indirect's method to gain root access and now the N button on my tablet won't work. I tried to post on the development board but since this is my first post it wouldn't let me. Any insight into how to get it to work or why it stopped working?
Because of home catcher, fix: 8 failed reboots
Sent from XDA premium using my Nook Tablet
what does that mean? how can i fix it?
What I mean is how exactly do you get 8 consecutive failed reboots?
twinfrey said:
What I mean is how exactly do you get 8 consecutive failed reboots?
Click to expand...
Click to collapse
when your NT boots up there will be a black screen with the n logo. right after that black screen disappears, hold the power and n button at the same time until the NT shuts off. repeat 8-10 times and you will be greeted with a factory software reset screen.
at that point, the NT will be booting into it's own recovery software. once that process is complete, you will be starting off with a fresh NT, assuming your original software was 1.4.0, otherwise it will be 1.4.1
hope this helps!
Do a factory reset. I had the same problem - N button stopped working. Password protection stopped working also. Only help was a factory reset. At the time, I didn't have home catcher installed - still don't.
when your NT boots up there will be a black screen with the n logo. right after that black screen disappears, hold the power and n button at the same time until the NT shuts off. repeat 8-10 times and you will be greeted with a factory software reset screen.
Click to expand...
Click to collapse
Let me think about this... N button doesn't work... Hmmm, hold down the N button... but, the N...
If the n button has failed in that regard, no amount of resets will repair it. That's a hardware failure and you would need to return the unit.
Try it. The n button may just not be working as expected from software.
Sent from my Nexus One using XDA App
So i was just forced to install Lollipop by Sprint. I was having a minor S-Pen issues and Sprints "FIX" was to update me to Android 5.0 Lollipop. Well now I have 500000000 other issue with my phone. Most i can live with, but there are 2 in particular that at driving me absolutely bonkers and I cant fix. I was hoping someone around here would have an idea how to fix it without me having to root, and go back to the previous OS. (The Sprint Root seems a little intimidating and I cant afford to brink my phone even for 20 minutes).
The main issues I am having are regarding the lock screen. I cant get the lock screen to stay open more then 3 or 4 seconds and if I botch my pattern or don't swipe fast enough, the screen will turn itself off. Then I have to turn the screen back on and try and unlock it again. Sometimes the screen even turns off in the middle of trying to unlock it. It is EXTREMELY annoying having to try and unlock my phone 4 or 5 times just to get to the notification screen ...... As for the Notification screen, once i finally am able to get my phone unlocked, then when i try and swipe my notification bar the phone will sometimes turn the screen off as well, then I have to go BACK to trying to unlock the phone and try and do everything faster then 2 jack rabbits banging in order to just get to my notifications. Its become a major problem in that sometimes I just cant get the sequence and speed right for 10 or 15 tries.
Anyone else having these issues or have a fix???
jcohenlv said:
So i was just forced to install Lollipop by Sprint. I was having a minor S-Pen issues and Sprints "FIX" was to update me to Android 5.0 Lollipop. Well now I have 500000000 other issue with my phone. Most i can live with, but there are 2 in particular that at driving me absolutely bonkers and I cant fix. I was hoping someone around here would have an idea how to fix it without me having to root, and go back to the previous OS. (The Sprint Root seems a little intimidating and I cant afford to brink my phone even for 20 minutes).
The main issues I am having are regarding the lock screen. I cant get the lock screen to stay open more then 3 or 4 seconds and if I botch my pattern or don't swipe fast enough, the screen will turn itself off. Then I have to turn the screen back on and try and unlock it again. Sometimes the screen even turns off in the middle of trying to unlock it. It is EXTREMELY annoying having to try and unlock my phone 4 or 5 times just to get to the notification screen ...... As for the Notification screen, once i finally am able to get my phone unlocked, then when i try and swipe my notification bar the phone will sometimes turn the screen off as well, then I have to go BACK to trying to unlock the phone and try and do everything faster then 2 jack rabbits banging in order to just get to my notifications. Its become a major problem in that sometimes I just cant get the sequence and speed right for 10 or 15 tries.
Anyone else having these issues or have a fix???
Click to expand...
Click to collapse
I can't say I had any problems like this. I was running Stock rooted OC5 for a while and had really no problems with it. I didn't have any pattern or pin unlock though, so maybe it would have been different? I would have stayed stock but my Flashaholic took hold and made to start trying out other ROMs.
As for rooting, I have found it very easy to root this phone. I haven't had a problem either using auto-root or flashing superSU.
Factory reset is easy.
w7excursion said:
Factory reset is easy.
Click to expand...
Click to collapse
before a factory reset, you might try doing a wipe of the cache partition.
turn your phone off
press and hold, Volume up + home key + power until you see the blue booting to recovery mode message
wait for recovery mode to display (the menu will show after the green robot)
use the volume rocker to move down to wipe cache partition and press the power button to select it.
now select the yes line and press power
now reboot your phone and see if that helps with the lock screen behavior
good luck
jdelano said:
before a factory reset, you might try doing a wipe of the cache partition.
turn your phone off
press and hold, Volume up + home key + power until you see the blue booting to recovery mode message
wait for recovery mode to display (the menu will show after the green robot)
use the volume rocker to move down to wipe cache partition and press the power button to select it.
now select the yes line and press power
now reboot your phone and see if that helps with the lock screen behavior
good luck
Click to expand...
Click to collapse
This seemed to work so far. Ill keep you posted as I use it more today. Thank you so much
jcohenlv said:
This seemed to work so far. Ill keep you posted as I use it more today. Thank you so much
Click to expand...
Click to collapse
Glad to hear that, I hope it stays that way
You should read more before trying to root
OK, here's the situation. sometime last night my phone decided it was going to play a late April fool's joke on me. I had set it down, and the screen timed out as usual. Only when I hit the power button again, it came right back to the home screen instead of the lock screen. Granted I only have it set to swipe, but that's beside the point (I think). I thought it's been a while since I rebooted, maybe that'll help. When it came back up, straight to the home screen again, only this time was way interesting! Not only did the lock screen get skipped, I had no haptic feedback like usual, the home button wasn't working for short press or long press, and with it plugged in and notifications waiting turning the screen off by the power button didn't do anything as far as the notification light.
Now here's the kicker: DOUBLE pressing the home button and bringing up the s-voice actually worked, and after that everything else worked too! Only thing is the problem comes back after every reboot so far. Oh and I've lost the ability to write to the external SD card. I've even tried reauthorizing it, no joy.
Anybody got any ideas about what I could try? If not, at least I hope I made some of you start or end the day with a chuckle and a solid Wtf? ?
My next step is gonna be clearing the dalvik/art from twrp.. Worst case scenario I factory reset and restore my week old backup..
I'm running stock rooted 5.0 with ph1 as my latest update. And if somebody is interested enough to want a logcat from boot to couple minutes in, I'll reboot now, capture the log and post it in a few.
Confused but amused,
I am
The Dude
The log.. I had Logcat Extreme running at info priority, and stopped it after around 8 minutes and just under 22,000 lines. Is that a lot? It seems like a lot. There are a couple power button hits, a menu and a back button press, and also at the end is where I double pressed home and got things back to normal..
Yes, I use xposed, minminguard, unbeloved hosts, and lucky patcher. You'll see them in the log, as well as my Wi-Fi ssid.. I dunno what else might be in there.. Hopefully nothing juicy though. Lol
If there's a way to filter stuff out, or just log the important things let me know and I'll give it another go.