I have no idea what exactly has gone wrong but I think I bricked my NT! I made modifications to the build.prop file, copied it back to root/system and rebooted (with quick reboot app) and now it won't come back on. Now I don't mean it's stuck in a boot loop or it's having a funny when it tries to boot I mean IT WONT COME ON! dead as a door nail
Anybody got any words of wisdom that may be of use at this point, I don't get anything, just a black screen!
I'm a bit paniced now because I'm in UK and it was obviously bought from a B&N store in US then sent over so I could give it to my wife as a Xmas pressy. I've bee tweaking it up to get it like a normal android tablet. It's been great little tab but now it's bricked!
Any suggestions?
Moved to general.
Battery empty? Try to recharge for some time. This thing does strange things on deep discharge. Otherwise factory reset (8 fail boots).
Sent from my B&N Nook Tablet using XDA Premium App
Related
so this guy came into my store who had a rezound, never once had a problem with it ever...then the battery died fully overnight because he forgot to charge it..
so when he woke up, it was dead obviously. he then plugged it in, and the orange light came on for 5 seconds...then shuts off. and nothing happens. this even happened when he brought it in for me to try. so i'm like, wtf, probably a bad battery maybe?
so i put in a good one we've got...same thing. so i ask if he's rooted or anything, he says no...but i did a search, and found some posts that when people had bad flashes of roms, it would stick at the white screen, and they had to restore a backup in CWM for it to work.
so i tried to see if maybe he was rooted...went into bootloader, hit recovery, and the phone just died. just shut off. so i was like, thats weird...so then i tried to do a factory reset....same thing, i hit factory reset, the white HTC screen came rgiht up, then the phone just died...and this was with a fully charged battery, too.
eventually we had to just call up and get him sent a refurb, but still, has anyone seen this problem? nothing i could do could get it to boot, and that's such a ****ty feeling especially if this guy said that he NEVER had a problem with any HTC phone, especially this rezound, until that battery died and it would'nt turn on again.
I've had that problem after a bad flash, but it still let me get into hboot and recovery without problems, so I doubt it was that. Don't have a clue what it could be though... at least you got him taken care of with a refurb. Maybe the inability to boot to recovery could be not having amon ra or cwm installed (never tried without one) and if he wiped /data or /system I don't know if factory reset would know what to reset to (again, never tried).
Edit: Also, with me, the phone never died. White HTC screen would stay up until I pulled the battery and it would still recognize the charger.
exactly! it's a problem after a bad flash. i wonder if this dude was lying and tried to flash something, his battery died, and it bricked it
I am currently experiencing the exact same problem; I was able to replicate everything you describe, including what happened when you tried to go into recovery or factory reset mode. I have NOT tried to root or do anything else untoward with the phone ... if anyone has any idea what I can do other than get a new phone and lose all my data, I would really appreciate it!
edit - there is one difference: my battery never died. I took my phone out of my pocket at 5:40 to look at it, and it was fine. I looked at it again at around 5:50 and I had the white htc screen. At this point I pulled the battery and started googling.
second edit - could the forced update have something to do with it??
nope, he brought his in before the update.
have you gotten anything to work? when we called customer service, they just replaced his phone for him..i hope it works out for you, man. maybe try to get into fastboot and wipe the phone, or something? i know i was able to get into the bootloader..maybe you can push a factory reset from the comp
avertist said:
I am currently experiencing the exact same problem; I was able to replicate everything you describe, including what happened when you tried to go into recovery or factory reset mode. I have NOT tried to root or do anything else untoward with the phone ... if anyone has any idea what I can do other than get a new phone and lose all my data, I would really appreciate it!
Click to expand...
Click to collapse
If you want to at least get the data off of it you can try using testdisk.
http://www.cgsecurity.org/wiki/TestDisk
I used it for my external sd card that wouldn't read in the phone or computer anymore and had all my nands and other backups on it. It seems like it won't work on Android but it will, but since I formatted it in the phone it didn't seem to have a volume name.
After you select the drive and it comes up with the partition table list, select [None].
Then select [Analyse]
I think that's when it will list all your directories.
You might be able to hook up your phone and get stuff off the internal card if you leave it at the white htc screen, not sure. But I have used testdisk successfully on a drive and the sd card that all systems said was unreadable and needed to be formatted. Anyway, it's worth a shot to see if you can get your stuff off it even if you have to return it.
jayochs said:
so this guy came into my store who had a rezound, never once had a problem with it ever...then the battery died fully overnight because he forgot to charge it..
so when he woke up, it was dead obviously. he then plugged it in, and the orange light came on for 5 seconds...then shuts off. and nothing happens. this even happened when he brought it in for me to try. so i'm like, wtf, probably a bad battery maybe?
so i put in a good one we've got...same thing. so i ask if he's rooted or anything, he says no...but i did a search, and found some posts that when people had bad flashes of roms, it would stick at the white screen, and they had to restore a backup in CWM for it to work.
so i tried to see if maybe he was rooted...went into bootloader, hit recovery, and the phone just died. just shut off. so i was like, thats weird...so then i tried to do a factory reset....same thing, i hit factory reset, the white HTC screen came rgiht up, then the phone just died...and this was with a fully charged battery, too.
eventually we had to just call up and get him sent a refurb, but still, has anyone seen this problem? nothing i could do could get it to boot, and that's such a ****ty feeling especially if this guy said that he NEVER had a problem with any HTC phone, especially this rezound, until that battery died and it would'nt turn on again.
Click to expand...
Click to collapse
Yeah I had a lot of white screen time when I had the Evo! A co-worker of mine had this happen on his Evo. It was from overheating. Now I realize this is the Rezound we're talking about but brilliant phones do think alike.
Sent from my ADR6425LVW using Tapatalk
happened to me when the kernel didn't flash but the rom did. Had to boot into fastboot and flash a kernel through a command prompt on my PC.
Just finished dealing with this after a bad flash. I couldn't boot, couldn't flash a new rom because of the Mainver error and couldn't get into recovery. Finally fixed it by deleting the PH98IMG.zip file. That let me get into recovery. Then had to flash back from ICS to Gingerbread. The I could follow the instructions to fix the Maiver error.
I had heard reports that people had data loss issues from the battery dying all the way in the rezound? Something tells me running the RUU on the phone would have fixed it.
Sent from my ADR6425LVW using XDA App
Hey everybody, longtime lurker. Going to make this short and sweet for anybody willing to give their insight. I have a 100% stock, never rooted (never even tinkered with) DNA that I bought from Verizon. I've had it for under a year. Today at work I felt it vibrating constantly in my pocket, after a while I took it out to see what the heck was going on and it was just bootlooping at the HTC screen. It is currently stuck like this until it drains the battery, then just starts up again once I plug it in. I've tried searching but it appears most issues are with people who have rooted their phones and are trying to flash back to stock because of issues. Any help would be appreciated. Going to try and call Verizon tomorrow. Also, I tried to boot to recovery, it worked once. And seems to not work anymore for some odd reason.
Only thing I can tell you is try to factory reset and if that does not help try to ruu it. You can find the ruu file if you just search the forum... You will probably lose all of your data though.
Sent from my HTC6435LVW using xda app-developers app
Defective, get replacement.
Try, while boot looping, to plug in and save any files you can...
Thanks for the reply's. After letting it charge basically for almost 15 hours, I woke up this morning to see the green charging light which gave me a little bit of hope. I went to turn it on but it just went straight back to bootlooping Calling Verizon soon, hopefully they aren't a pain in the ass to deal with...
Hello Everyone,
I am very new to this and I do not know a lot of terminology of developers so it is quiet hard for me to figure this out on my own.
I got HTC One X Plus in May and I did not root it or anything, just used it normally. I think I made a mistake of not charging it for 24 hours the first time, because my battery drains very quickly, even when I don't play games or use 4G. Yesterday when my battery level was very low, the phone shut off, and turned back on again, but didn't get past the HTC Logo, and a few seconds later it shut off. And since then its been doing just that. I'm suspecting that the battery cannot charge or something, because I tried a hard reset and reboot, recovery, factory reset and everything. I did notice that when I got to the screen with three Androids, a message, that said "battery too low to flash". Now, I know there are lots of posts about this, but they're all about rooted phones or custom ROMS, and I honestly don't understand what they're talking about. I have almost two years with this phone and I can't afford a new one and even though Im still under warranty I can't send it back, because I have a small crack in the glass(not the screen) and apparently ATT warranty will charge you $500 for physical damage. Please help, if you can.
Nikita
You all are useless nerds.
Nikita92 said:
You all are useless nerds.
Click to expand...
Click to collapse
great way of getting help! Hope you like your new phone!
Sent from my Nexus 4 using Tapatalk 2
OK, guys, I'm talking about, most likely, a fairly unique problem I have with my Hisense Sero 7 Pro. So, considering the events of this have occurred over a year ago, pardon me if I have a bad memory. Get ready for story time!
Somehow, I could not get my Hisense Sero 7 Pro to boot up Cyanogenmod. I believe that is the software I loaded on it. For whatever reason, I could not boot it. I mean, fine whatever, right? I still have fastboot or bootloader and those combinations of buttons so that I reflash my software if needbe. It should technically be only a temp brick. But for whatever reason, it became really low on battery, perhaps from me unsuccessfully attempting to change it. I mean so low, that it reached that magical number where all of a sudden the tablet itself doesn't think it has a battery. And thus, it wouldn't even charge. I used a myriad of chargers and attempted all sorts of things to jump start it to a point where I could get it charging again, but it couldn't. Thus, I gave up on this tablet, and got a Nexus 7 2013.
Sometime later (ie, now), I fished this old tablet out of a shoe box when cleaning stuff out. I mean, not that old, but whatever. I thought, why not give it another go? I grabbed a random charger and plugged it in. I left it for 30 minutes to sit there, not doing anything. When I returned, to my surprise, it had reached the magical HISENSE boot screen it had been stuck at previously. This meant, that for some odd reason, my tablet had begun charging to some point, right? Alas, I was very excited. Yes, the tablet was still stuck at the HISENSE screen, flashing off and on again every minute or so, as if it's trying to boot a software that's essentially bricked, it's not there. But it has the electricity throbbing through its veins. And thus, that is enough for me to be excited. Just recently, I tried to boot into fastboot, I believe. And the device threw my a Low Battery symbol. The same kind it threw me when I tried to start it up way back when, and continued to attempt to, whilst it didn't charge, until it was deader than Abraham Lincoln.
But now I have the charger that will charge it, and that's good enough for me. Next Steps? Obviously, wait around, right? Perhaps it's below that 10% locked threshold needed for it to boot into fastboot or recovery? And if that's the case, I'll update you guys on that, but if that's the case, then great. I've got it at that screen.
Now what?
What do I do to flash Cyanogenmod, or Clockwork if I don't have it for whatever reason, and then Cyanogenmod and get this old thing working again? It's a project, true, but if I can get it functioning, this tablet would be awesome to have around the house, and, either way, it's a fun thing to work on.
Thanks for reading my story, and if you can help, great stuff!
i would suggest you install the latest lollipop.
first you will need to install a new recovery (neither the stock recover nor CWM will work with the newer roms)
http://forum.xda-developers.com/android/development/rom-sero-7-pro-uk-au-aosp-5-0-2r1-dopa5-t3015014
the above link has all the info, and files you need.
I have a Verizon Ellipsis 7 tablet that is stuck in a boot loop. When I turn it on, I get the "Powered by Android" screen and then the screen goes blank but lit, and never gets to the next stage. I tried entering Factory Mode and cleared the eMMC, but after doing that I can't even get back into Factory Mode. (I spoke to a Verizon rep and he said clearing the eMMC likely cleared too much, and it now lacks the proper kernels to start up.)
I believe this whole fiasco may have started when I used the wrong charger after having not turned on the tablet for months. I stupidly ignored the warning, and the problems started soon after (although it worked perfectly normally for about a day first). I now have the correct charger and have fully charged the device overnight, but nothing's changed.
I think the only hope at this point is to reinstall the OS (the Verizon guy said "flash" it, but I'm not 100% sure what this involves). Can anyone help me do this, simply and safely? I'd like the original OS if possible, but otherwise I'm open to open-source alternatives. Thanks!
i just had this happen too -- and now i am stuck too;
however mine gets stuck at the verizon loading logo
Dude I'm right there with you. I'm almost at the point of installing Ubuntu touch lol I'm still not done with this fight though shoot I'll learn a whole new skill if need be damn things made me forfeit more than enough times.
hola busco firmware qmv7a