Database Develop

[Q] Bricked Nook

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?

A friend opened up my Hero thinking he knew what he was doing...

A friend of mine took apart my hero thinking he was going to help get the dust out from under my screen. I said if it was a problem I would do it myself, well <sarcasm> big shocker, it took only a few minutes to open up</sarcasm> but then an hour to get back together properly -.-
It worked for a while afterwards. flashed fresh Hero. Then after a few hours mid-day after a few successful restarts it decided it didn't want to boot. Didn't do anything special but power off for a battery swap with my Evo. Now it only hangs on the "HTC" splash screen. It can get into the bootloader, but so far it won't flash and hercimg.zip's I throw on it's micro sd card with a card reader. I've only found 2 though. Recovery doesn't work, just hangs on "HTC" screen.
Any suggestions? It's not much of a big deal, but my Evo is cracked and I hope to be replacing it soon. Incase Sprint deactivates or blocks the Evo's ESN.
I've given the Hero hours and hours to boot or load recovery. One time, I let it hang until the battery died!
****Don't reply saying "they won't deactivate your Evo", I already know they most likely will not. That isn't my problem! I need help on fixing my Hero****

iff u can get into fastboot u could try an ruu

If you or your friend didn't properly discharge before you took the phone apart or put it back together you might have temporarily or permanently shocked the mb. Id say try letting it sit over night with the battery out and see if it at least you can boot into recovery. If not then like Bierce22 posted try to ruu. You can try the ruu in zip format or try to ruu from your pc by tracking down an ruu.exe. You can find all the info you need on duces thread about how to ruu. If you can't from your pc you can try the ruu in zip format. If you can't boot into recovery or if your not s-off I'd recommend looking at jm's thread on how to use fastboot without being s-off. Also you would need adb to try that out and if you don't have adb installed then you can hit my avatar and look for my thread on how to install adb on windows it takes like 10 or 15 min tops. Take in mind this is all just a guess. So this is not a guaranteed fix. If you manage to get into recovery I'd say backup all your data and format sd. Then put all the data back on and do a full wipe and a fresh install of the rom of your choice. Or restore a nand. If you get that far run your phone for a couple of days and see how it performs if its straight then your good. If it behaves wacky I'd say put a stock rom on and try to do an insurance claim due to hardware failure. ""TRY""
If you don't get it booted back up then pm me if you want to try a few more steps to attempt to resolve your issue. I've been a victim of a friends so called experience and the whole "I know how to do it but your phone was my first attempt at it thing" Well hope this helps Good luck.
Root/Hack-Mod-Always*

Well, I'd done it to his phone before, but "see what had happened was..." Erf
I think it might've been that I didn't ground myself :/
Daniel, I told you I'd make it up xD you'll get a Droid Eris "sometime" :3

Does anyone have a guide on how to take it apart and put back together successfully? I need to replace my faceplate and thought I'd hijack here.
Also, anyone have a link for the best place to buy the full faceplate and rear door?
Sent from my HERO200 using XDA Premium App

[Q] G1 wont boot... sometimes

Hello,
I have recently got my hands on old G1; got it as "bricked" - no matter what i did, it just wouldnt turn on. I could, however, get into bootloader (or whatever is that tri-colored screen called). Using goldcard, i was able to flash RC29 DREAMIMG, which would however result in same error (phone stuck at g1 logo).
Finaly got it "working" by flashing package from stem 3 of this guide; which enabled fastboot. Using fastboot i than flashed hboot and radio from this thread and RA recovery. Using recovery, i finally flashed (tried more, same problem on all of them) this rom ("FroyoByLaszlo Port" one).
Now to the problem; sometimes, phone just wont boot, or access the recovery. I am able to enter bootloader screen every time, even if it wont boot. Sometimes it boots straigt away, sometimes it enters some kind of bootloop (and might actually boot after several [g1 logo -> some time -> reboot] cycles. Also, what i noticed, is that phone sometimes has problems with waking up - buttons would light up and screen stays black. If i open keyboard, screen goes on, but digitezer wont react (trackball works).
Have to say I am not quite sure what might be wrong (one suspect MIGHT be battery, which seems to be quite weak). I will gladly accept any new idea.

Doubtful its the battery but it sure sounds like hardware, maybe a bad chip with some corrupt partitions. Flashing a new bootloader should take care of this but being you have done so.... maybe bad blocks in the chip?
What is you current bootloader and radio? Write down all from that screen
Sent from my HTC Vision using xda premium

DREAM PVT 32B SHIP S-ON
HBOOT-1.33.0013d (DREA11000)
CPLD-4
RADIO-2.22.27.08
Oct 21 2009,22:33:27
Than theres just fastboot and action selection stuff.
Edit: also, i have opened it up (everything except lcd part, which i might check later) to check for any loose cables (what i noticed, is that if i give the phone few harder knocks, it usualy boots - however i am still not sure if this isnt just an coincidence) and oxidation; everything seemed clean & in great condition (ie, no oxidation).

A strange one you have here, the intermediate problems always trouble me the most. Its possible you have a sometimes sticky camera button that keeps you from booting properly without banging it around...
Sent from my HTC Vision using xda premium

I will give these buttons a go later (will open it up once more, might check the lcd part as well), however they dont feel like they are geting "stuck" - and both of them works well for selecting actions in bootloader.
Also, would that explain the "wake up" bug? Just happened.
edit: However i think i may confirm the "bang a phone" theory. Just refused to boot, gave it bang right into the butons and there it boots.

Gentle Bang for The Win!
demkantor said:
A strange one you have here, the intermediate problems always trouble me the most. Its possible you have a sometimes sticky camera button that keeps you from booting properly without banging it around...
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
I recently pulled out my HTC G1 which has been out of commission for some time; it's long since had some battery issues - doesn't hold a charge (well, it does now, but not for long..), and I look forward to rooting it this weekend as it's far past warranty and I'm no longer w/ T-Mobile. Long story short, I forgot the screen unlock code and couldn't log in using a Google account (btw - still haven't found a way around this one yet). I used the pinhole reset and I'm pretty sure it got stuck as my phone wouldn't boot, take charge or anything. Was fairly convinced it was bricked - until I came across this post (many thanks) and gently whacked my G1 against the wooden coffee table and pressed over ALL the buttons on the unit to be sure nothing was stuck. During the process - there was light (literally)! Sure enough - I put power back to the unit, and it's taking a charge again. So today I being the journey to root, and wanted to throw this out there for anyone else stuck before boot with an apparently bricked phone. This is the first Android smartphone they made and certainly has it's share of bugs - sticky keys, etc. Give it a good whackin' and try again, hope this works for others as well!
~Sockum

[Q] Dropped HTC M7, now boot loop and no recovery

Hi there... new to the forum, but long-time reader, especially over the past two days since I dropped my AT&T HTC M7 (flashed to GPE) on cement and it pretty much died.
I'm out of ideas and could use some help. After the drop, it was stuck in a boot loop, but I was able to get to hboot with volume down. From there, I can access fastboot, but recovery or factory reset options just trigger the boot loop again. During the loop, it shows the Google logo (or HTC logo when flashed to stock) for 15-20 seconds and then reboots. Physical damage to the phone is not too substantial, and I have unfortunately extensive experience opening it up from repeated attempts to fix the purple tint issue with bad modules from eBay, so I checked inside and everything is intact.
Over the past two days I've flashed RUUs and recoveries like crazy, downgraded and upgraded hboot, changed CID, etc. I can oem lock and unlock... fastboot kicks out an error when I do it, but the status in hboot is changed when I reboot into the bootloader. Flashing ROMs and recoveries works like a charm, so does erasing cache. What I mean is that the process works exactly like before in fastboot, and I can see the splash screen logo change, so I know it's taken effect, but NOTHING gets past the boot loop. I am thinking the drop resulted in a corrupt partition, but since I can't get into recovery I haven't been able to find any way to do anything about that. If it was physically broken, it just doesn't seem like I would be able to do everything I can. I initially thought maybe it was a busted/stuck power switch, but that works perfectly navigating hboot menus and nothing ever auto-selects or anything like that, which I would expect.
Aside from the fact that I really like this phone, and that I really don't want to have to pay to replace it, I feel attached to it since I've dismantled it successfully to repair more than once and flashed ROMs many times in the past without issues. I've just run out of ideas, and of course I can't go on much longer without a phone.
Does anyone have any experience with this or hunches I can try out?

placebored said:
Hi there... new to the forum, but long-time reader, especially over the past two days since I dropped my AT&T HTC M7 (flashed to GPE) on cement and it pretty much died.
I'm out of ideas and could use some help. After the drop, it was stuck in a boot loop, but I was able to get to hboot with volume down. From there, I can access fastboot, but recovery or factory reset options just trigger the boot loop again. During the loop, it shows the Google logo (or HTC logo when flashed to stock) for 15-20 seconds and then reboots. Physical damage to the phone is not too substantial, and I have unfortunately extensive experience opening it up from repeated attempts to fix the purple tint issue with bad modules from eBay, so I checked inside and everything is intact.
Over the past two days I've flashed RUUs and recoveries like crazy, downgraded and upgraded hboot, changed CID, etc. I can oem lock and unlock... fastboot kicks out an error when I do it, but the status in hboot is changed when I reboot into the bootloader. Flashing ROMs and recoveries works like a charm, so does erasing cache. What I mean is that the process works exactly like before in fastboot, and I can see the splash screen logo change, so I know it's taken effect, but NOTHING gets past the boot loop. I am thinking the drop resulted in a corrupt partition, but since I can't get into recovery I haven't been able to find any way to do anything about that. If it was physically broken, it just doesn't seem like I would be able to do everything I can. I initially thought maybe it was a busted/stuck power switch, but that works perfectly navigating hboot menus and nothing ever auto-selects or anything like that, which I would expect.
Aside from the fact that I really like this phone, and that I really don't want to have to pay to replace it, I feel attached to it since I've dismantled it successfully to repair more than once and flashed ROMs many times in the past without issues. I've just run out of ideas, and of course I can't go on much longer without a phone.
Does anyone have any experience with this or hunches I can try out?
Click to expand...
Click to collapse
yeah try a new motherboard yours is broken, really it's hardware damage no amount of flashing will fix it

clsA said:
yeah try a new motherboard yours is broken, really it's hardware damage no amount of flashing will fix it
Click to expand...
Click to collapse
Thanks clsA. I'm surprised by that since in my experience a broken motherboard results in a much more substantial and obvious failure, but I guess the point is moot if I can't get into recovery to try anything else.
There isn't much of a market for new motherboards, and my experience with eBay sellers for oem components on this device makes me think trying to replace it there would be a fool's errand. I guess I could buy a used M7, but on the other hand the damn thing has basically been nothing but problems. The defective camera turned to garbage in under a year and one drop killed it? Unless anyone has another suggestion, I guess it's time to cut my losses on this thing. I may feel a sentimental attachment because I've nursed it along so much, but damn... a phone is a phone and this one has been a LOT more problematic than any other one I've had.

Gotta thank you again clsA! Your words of doom made me feel that extra bit wreckless, so I decided if the phone was cooked anyway I might as well tear it down and try whatever I could... firmly reseating cables and squeezing heatsinks, etc. Low and behold, I reassembled and the problem is fixed! I'm not sure what the exact issue was, and I won't be surprised if it comes back at some point down the line, but I'm back up and running tonight and that's a hell of a lot more of a victory than I was expecting.
So... it wasn't a motherboard issue, but it was hardware related.
I should have posted on here when this first happened. I love xda!

placebored said:
Gotta thank you again clsA! Your words of doom made me feel that extra bit wreckless, so I decided if the phone was cooked anyway I might as well tear it down and try whatever I could... firmly reseating cables and squeezing heatsinks, etc. Low and behold, I reassembled and the problem is fixed! I'm not sure what the exact issue was, and I won't be surprised if it comes back at some point down the line, but I'm back up and running tonight and that's a hell of a lot more of a victory than I was expecting.
So... it wasn't a motherboard issue, but it was hardware related.
I should have posted on here when this first happened. I love xda!
Click to expand...
Click to collapse
That's great, I'm glad you were able to fix it

Razr i xt890 - need HELP completely reinstalling firmware !

Hello guys,
I've been messing around with my Motorola Razr i XT890 the last couple of days, trying to get it "back to life".
It suddenly shut down and would get stuck on the red "M" logo, right when the animation would start (the white wavey-type of lines freeze and that is all it would do. I, myself, am not really much up to date on rooting, installing custom roms, you know; the whole developing thing (I find it interesting, it is just that I lack time to be able to learn more). Anyway, the phone got stuck and I've managed to factory reset it, after a while the phone would freeze and again get stuck on the red logo, this went on until it would not boot at all. All I got was a short vibration and the green led would light up for like one second. Using this forum I've found a solution to bring it back to the point it would get back into fastboot (Actually holding the camera button down with usb attached, install some specific drivers and then run a batch file).
At this point this is my situation:
I'm stuck on fastboot, however I turn on the phone it will get into fastboot (see attached image to see what it says)
[IMG_20160914_210059.jpg](https://postimg.org/image/ptin5opgl/)
I, for some reason, have Philz Recovery installed and tried to use adb sideload to install a few files but my biggest problem is that I'm not sure which firmware I need, I'm really confused about all the terms and what not. I'm not the type of person that pays much attention and like knows the difference between JB or KitKat or whatever. All I know is that the phone was purchased in Germany along with a contract with either Vodafone or O2 (really not sure). I have so many files and tools installed on my PC and I would like to delete everything and start from scratch. I have fastboot and adb working (except for RSDLite, for some reason it just won't recognize the device, while adb sideload did work....haven't figured that one out yet.
If any one happens to know. or can post a link for 1 or 2 versions of the firmware and help me out. Just point me in the right direction, I know my way around a computer but like I said, I've never really done much in this area
I bought a new model Motorola soon after this one crashed the second time, so it's not even about the phone itself. I kind of challenged myself to get it working again, on top of that, it was a very good phone and I got really used to it. These new big screens are too much for me so if I get it working I might actually start using it again lol.
Also thanks to all of you who put time and effort in helping people who have these kind of problems, it's a really nice community overall and I've gotten to like it and will try to spend more time learning about this. I might just help out some lost soul myself some day

PS; sry about the green lol, I actually just realized it...I just can't be bothered cropping it out