Got my gTab yesterday. [VERY EXCITED!]
Plugged in wall outlet, waited 4 hours to charge.
Connected to WiFi.
Updated TapnTap, as instructed.
My Vist Ultimate computer didn't see the gTab when I plugged it in, at least not so I could get to the root directory.
So I went to an old XP and tried that. It worked.
Wanted to Root it, so I installed (sorry if that's not the correct word) ClockworkMod v08.
So far so good.
Then rooted TnT Lite v 4.2
Still good.
Then rooted TnT Lite suppl 4.25
STILL okay.
Then went to gMail. Added my gMail account. (An account I use for business.) It took a LONG time to do whatever it was doing. So I went to do something else, thinking it would continue doing it's thing in the background. I was wrong. It messed up, and I kept getting error messages.
Next thing I know, I'm somehow in that infinite boot loop.
It was about 2 am, and I was tired, and... panicked!
Next thing you know I'm freaking out and went hog-wild (while following directions to the letter), to get my brand new toy to work.
I did nvflash windows, still infinite boot loop. I tried putting the vanilla recovery 3588 on there. Still infinite boot loop.
Kept at things, trying everything I read, and STILL... infinite boot loop.
Then I figured it was time to try to get my Vista computer working so I wouldn't have to keep transferring stuff from the Vista to the XP to the miscroSD card to the gTab, and followed directions about APX mode.
I was delirious, exhausted and scared, and kind of went postal (in a frenzied OCD sort-of way), trying everything and anything to get rid of the infinite boot loop.
Now it won't even power up. (AT ALL!) I think I gave it a heart attack, or possibly a stroke. And that's with not even owning it for 24 hours!
I've tried the long 45 second power hold, then the short one. [Did that about 37 times.] I've tried power and Vol+. Nope. Then did a few power and Vol-, just to really freak the poor sick, dead thing out. [Like kicking the proverbial dead horse, I guess. Trying to see if there was any life left in it.] I even read to turn off the lights to see if there was a faint glow. But nope. No glow.
I will now follow the directions from another post, and will let it just sit for 24 hours (if I can survive the wait) to let the battery discharge and then see if it will boot. [After this nightmare, there is no WAY I will take off the back and hit the reset button--thereby definitely voiding my warranty.] But I hope I'm not like the woman from the forum thread: http://forum.xda-developers.com/showthread.php?t=968177
If I am, and can't get this thing to power up, do you think WOOT will let me return it???? I'm so upset that I broke my new toy so quickly. If anyone has any suggestions about getting this thing to boot up, I'd appreciate it. [at this point, I'd be happy to have it boot up in the infinite boot loop!]
Oh, and one last question, how does having it turned off (because I can't turn it on) and sitting there drain the battery to the point that it needs to start fresh after a mere 24 hours with no activity? Is that typical for tablets?
THANK YOU to anyone who can offer advice on what to try next or how to remedy this problem. Please keep in mind that I am good with PCs and laptops/netbooks, but am VERY new to this whole android and tablet things, so if you send instructions, please give implicit directions (as though you are instructing a 3-year-old), without feeling as if you are insulting me. [Please believe it's what I need, and will appreciate. As will the other wooters who just turned their gTabs into brinks] And know that you will be helping Roebeet by answering my questions, because the poor guy must be exhausted from all of us lay-peoples' foibles and mess-ups. [The man seems to be a God at this site!]
Did you do what is mentioned right after step 10 in this thread?
http://forum.xda-developers.com/showthread.php?t=865245
"If your tablet bootloops…Also may be required to get market running correctly on some ROMs...
Press and hold the power button to shut the device down. Boot back into Clockwork. Select the advanced option at the bottom, then go to “partition SD card”, for the first option select 2048, and for the second option select 0. Then, redo steps 7-10. This erases all data on your tablet, including backups."
But first... switch to decaf and get some rest... ;-)
Panic doesn't help.
It might actually be powering up but staying in APX mode. I've seen one do that. If that's the case you can still nvflash it back to normal. Let it charge for 15-20 minutes and leave it on the charger. Try to start it up and see if your pc can see it.
You maybe got the bootloop because your tab had sleep death while syncing. Was the error you got by chance something like process.acore? If so that is a classic error that happens after syncing contacts, sometimes there are empty contacts with no data that make the tab go nuts. Simply deleting the bad contacts solves the problem.
A simple wipe data/cash/davlic would have been the first place to start. Breathing helps when stuff goes wonky.
If you can get it to recovery a repartition is totally necessary. Deffinetly... and maybe some whiskey ....
Good luck.
good luck with woot return, dont even think they do it.
I wouldn't worry about the warranty. You already voided it when you rooted the device.
I'm so sorry, guys, I didn't check off the subscribe notification, so I didn't know that anyone had written.
cdavisccs28, I didn't do that while the tablet was boot looping, but somehow it went from bootlooping to complete death.
K J Rad, it wasn't charging, and wouldn't boot. [And you can probably guess, I tried numerous times.]
Mantara, the death in the middle of syncing certainly didn't help it, and, as you suggested, might have been the last nail in the coffin. The whiskey suggestion was funny! Actually I, personally don't drink, but as you might have deduced, I'm a carrier. [AKA: I've been told that I drive people to drink.]
spike378 & filterking: Yup, I think you are both correct. How I managed to spike from "excited as a schoolgirl" to "completely tanking" in less than 24 hours amazes even ME! [And I know me, and am used to me! I think that was a personal record!] [If I don't laugh about it, I'll cry!]
THANK YOU ALL for replying! Your time and concern meant a lot to me, but I think this baby is totally bricked! Elvis has DEFINITELY left the building! If I do get another one (I'll have to start saving again), I might be too afraid to play with it. I really am good with PCs and notebooks, so I might just keep staying with what I know. YOU GUYS ROCK, for trying to help me, and I really appreciate it!
Same problem. I booted the device up, and connected it to WiFi. Then it gave a popup where it asked to update to the newest version. I said okay, and let it do its thing. Then it restarted into a bootloop. So, I turned the device off, and tried to turn it back on, except -- nothing. With the USB plugged in, it's not recognized by the computer at any time after I press the power button. I've been trying to get it to boot for an hour now and it's still just sitting there with a black screen. Not even a backlight is showing. Anyone know of any solution? Or is it time to ask for an RMA from Woot!?
h.nocturna, WOW, you didn't even get to the part where you started doing everything and anything (in a frenzy) to get it to work properly! That might be a good thing, h.nocturna, because you haven't voided your warranty! You might need to send it to Viewsonic to be fixed (since it messed up while you were doing their update), but at least you can do THAT! I mailed my brand new brick to my son up in college and gave him this site, and told him to have a blast, and do whatever he wanted with it. [He's known me his whole life, and said even HE "can't fathom my destroying something so completely in less than 10 hours."] I wish you luck!
Oh, one more question that will help the masses, I'm sure. So how do you get your computer to recognize the device as a hard drive, when it is plugged in to a Windows PC (without voiding the warrenty, of course)? [Vista Ultimate does not recognize it, and neither did Windows 7.] Please give step-by-step instructions for the lay-person. [By answering this question, at least we will solve THAT problem for folks!]
badtypist,
I wrote you a fix last night and when I went to save it the Forums had been shut down and do it didn't save to post --
and I had been on the road and was exhausted and just couldn't stay up long enough to redo it if and when they came back up. Sorry.
You simply needed to find one solution and then let us get down the procedure to follow to fix it.
Several people in the past have gotten to the point where you were. I read two fixes.
One was some people were able to get the tab to start again by playing with the
power switch -- hold it for long, long times and then press a short startup, etc. Somehow they got that to reset and start.
Somewhere else in the forums -- and I have never done this with either of my tablets --
there are a few threads where someone in this kind of situation opened up
the tablet card and simply unplugged the battery for 10- or more seconds. There also
is a reset button inside the case as shown in an old thread where someone opened a
G-Tab up and took pictures.
If any of those three choices get to where you can either use power / volume - to get
into NVFlash more ---- or to where we can load CWM -- then you are in fair shape.
LOTS AND LOTS OF BOOT LOOPS ARE ASSOCIATED WITH PARTITIONING. Simply
getting into CWM and re-partitioning to 2048 and 0 and then using CWM to "Fix
Permissions" will get it working. CWM also will let you wipe the cache and wipe the
factory data, which sometimes will allow and NVFlash to come on up and work right.
You see, we were not dead by any stretch.
You might pass this on to the recipient of the tablet.
Also, so many people are trying to do so much that is over their heads -- and so many
people are borking their tablets -- that this site and the folks that can help -- just can't communicate. Sad day.
I wish you luck. Hope this helps.
Rev
EDIT: Well, I guess we missed the boat completely. Evidently she mailed of the G-Tab and checked
out for good!!!
Hi Rev! Sorry I didn't get back to you sooner. I TRIED to get back to you sooner, but I think this site was down, because it kept timing out and wouldn't let me get to the site OR the conversation thread! I tried a few times, then tried later, and now just tried again!
I think you guys are getting BLASTED with desperate lay-people from the over 10,000 tablets sold on Woot who have "borked" their tablets. (That's a funny word, Rev! I hope I'm using it properly! And please note, although the WORD is funny, the actual situation is NOT funny!)
Yes, I mailed the offending frustration-linked object to my son, and can't "take it back," but perhaps I will beg for and borrow enough money to try again, sometime soon! If I do, I will come back here again sine I feel I have bonded with the wonderful, sharing folks on this site. (I'm a she, by the way, not a "he.") I admire (okay, worship) the folks who help us lay-people out so we don't sit alone crying and trying to power/Vol+ in solitude!
I've read your other posts previously, Rev, and you are so wonderful to help us n00bs! So please remember "badtypist" (hopefully with good thoughts) and when you hear my name again, let's hope it's to say... THIS TIME I ROOTED IT CORRECTLY!!!!
Thanks again, for your time, Rev AND the rest of you, which wasn't wasted, because I sent my son this link and he will (in his spare time) read through it to fix HIS new tablet. [I think he kind of liked that his mom messed up! He got a VERY expensive new toy, if he can fix it.]
Perhaps I'll talk with you soon...
badtypist (and bad ROOTER. Or is it ROOTERIST? Or maybe ROOTIST? Whatever the proper term, I think we can all agree that I AM bad at it!)
Gtab Update Problems
So, I would agree with some of the posts above. I would also point out that you have two options (or some combination of the two):
1. Try to return the tablet, or put in a warranty claim (the warranty specifically does not cover modification\rooting)
2. Try to fix it yourself
I tend to choose #2 f I think the chances are better than 50/50 in my favor. Also, if the hardware is okay, you can have it fixed in 20 minutes.
The experience that the OP went through is EXACTLY why I discourage newer g-tablet owners from rushing in and flashing alternate firmware to their tablet. I am often chided for this recommendation, but I believe that it is unwise to modify a brand new tablet.
If you still want to mod it, you should have a backup plan. I save my update file to an external USB drive. You should then be able to re-install the stock update by placing it on a microSD card. You need to rename it to update.zip, and add a file that tells it to look at the microSD card for an update. I am a but fuzzy on the specifics, but that file is named "command", and I found it somewhere here in the forums.
As I plan on modding my newer woot tablet (or maybe my older Sears one). I will first set this up, and will work out the details.
Hi buzzzard, thanks for the great info! VERY helpful. I did see that video while researching the gTab, but didn't bookmark it, so I appreciate your adding it here! My son will see all your posts and will use all of your suggestions to try to raise my brand new gTab from the dead! [It wasn't even in zombie mode when I shipped it to my son, so we'll see what happens! I'll keep ya'll informed.]
wasserkapf, you are probably right about not jumping in with both feet for us n00bs. And I most certainly don't mean to be disrespectful in ANY way, but I have a (serious) question... if I'd kept the tap-n-tap and played with it for a while, how would that have changed things for me if I eventually decided to root it to a faster, better OS? [I'm not meaning this sarcastically, I really want to know what I'd have to learn in order to change the results I had, in case I ever do this whole process again, or in case others out there are (hopefully) learning by my mistakes.] What would you suggest lay-people should be learning about the gTab BEFORE attempting to root it? [The answer to this question wil help a LOT of folks!]
buzzzard,
I have always understood -- and I don't want to know bad enough to spend the time
researching it -- that the warranty is void when you load non-standard software.
And even if it were not, I have real questions about messing up a computer and then
taking it back to the seller as if it were faulty. Seems to me there is a dishonesty
component in that equation.
I think modders SHOULD accept the risk that they can trash their tablets -- and that
if they do then the loss is theirs.
Rev
P. S. -- I've tried to say this much without starting a flame war -- if you do I won't
answer you and will ask the moderator to close and hide the thread.
badtypist said:
wasserkapf, you are probably right about not jumping in with both feet for us n00bs. And I most certainly don't mean to be disrespectful in ANY way, but I have a (serious) question... if I'd kept the tap-n-tap and played with it for a while, how would that have changed things for me if I eventually decided to root it to a faster, better OS?
Click to expand...
Click to collapse
For one, this will give you time to read up and learn more. I can tell that you are confused by all of this. You don't "root it to a faster OS". Rooting is a method to gain root privileges on the tablet. To you windows users, root is the equivalent of Administrator. There also is only one OS available for this tablet, and that is Android. Some have made modified/customized versions of Android, but it is still Android.
[I'm not meaning this sarcastically, I really want to know what I'd have to learn in order to change the results I had, in case I ever do this whole process again, or in case others out there are (hopefully) learning by my mistakes.] What would you suggest lay-people should be learning about the gTab BEFORE attempting to root it? [The answer to this question wil help a LOT of folks!]
Click to expand...
Click to collapse
There seems to be the misperception that you have to install a custom firmware to get root privileges or Android Market access. This can be done on the stock firmware, and then makes the tablet much more useful.
butchconner, I know you weren't talking to me, but I am taking full responsibility, and am hoping my son can resurrect my gTab, and I DO hope there will be no flaming, as well. ["There's no need for flaming. It's unsportsmanlike, kind-of rude and unproductive," said the mom to all reading this thread. So please don't flame so this won't get deleted for other poor people who "bork" their gTabs.]
badtypist,
wasserkapf was around when I got my first G-Tablet -- when we were all getting started last November.
You have no idea how bad the software was back then and the things we had to do to make things work.
It wasn't a question of 10 different ROMS and whether it was fast or not -- it was a question of making it work.
But I agree with wasserkapf (and I don't mean this comment particularly at you ) that
people are trying to do too much to fast. In addition to being a minister, I also was
an exec in the IT field for 30 years. I learned to read the docs, to move slow, to make sure each step was
successfully completed before moving on, to test things that
I'm not sure of -- and a whole host of other things that IT people use to operate their
company's systems without crashing it and losing data.
I helped a guy along the way who said he was inexperienced and that his tablet was in
the same kind of situation yours ways. He had gotten his G-Tab, charged it up, and had loaded EVERYTHING he could find on it.
Three or four different ROMS including an
experimental ROM he had been warned was risky. Yet he was having to ask what
recovery was and where to look for files and other basic questions.
I think everybody should get their tablet, upgrade to the latest version of stock, install z4root and
Titanium Backup and learn to use them, then install the latest version of Angry Birds and whatever useful software they need -- and then enjoy
that for a while while they learn the ins and outs of modding.
I help people because of the kind of person I am and because I am retired and have
some time to devote. But I also will be honest and tell you this -- I don't suffer
obnoxious, foolish people well -- and there are folks I just don't help because someone gave them good advice
and they didn't listen........I help folks who need and deserve to be helped.
The alternate ROMs are nice. And it's neat to add market and other useful stuff to
your tablet. But none of those kinds of things are so important that they are worth
what some folks do.
Nuff said. I don't respond to flames. And when you have been helping people as long
as I have, then you can have your opinion.
Peace,
Rev
Related
I did one flash...to TNT version 4xx, and I loved it...but I'm finding I'm getting lots of Google Framework errors and generally just kind of want to start from scratch, over again.....go back to the latest version of the official viewsonic roms.
Sadly I didn't use clockwork or anything so I think my original files are history
I know there are lots of threads, and I tried to follow one about snagging a rom and moving it to the Root and all it does is re-install TNT I think I am "not getting something".
Can someone walk me through this....
The force closes can be fixed by re-partitioning your sd card. Part 1 Step 7 in this tutorial:
http://forum.xda-developers.com/showthread.php?t=865245
But partitioning will erase everything, and is usually done after installing cwm and before flashing a rom.
You really don't want to go back to stock, especially if it's only to gain stability. All the force closes will go away when the tablet is properly formatted.
If your looking to go back to stock, I like nvflash, but there are easier ways.
http://forum.xda-developers.com/showthread.php?t=861950
Force closing is a known issue that can be easily fixed by repartitioning your internal sd card to the right specs. It has nothing to do with your newly flashed rom.
What you need to do is back up all your data on the sdcard and then go into clockworkmod advance and repartition to 2048/0.
Added by edit.
To be honest, your original post tells me the gtab isn't for you. I say a mainstream device like the ipad is more for you. Here is why. In order to use the gtab, you need to do the following things.
(1) Install clockworkmod.
(2) Use clockworkmod to repartition to fix the force closing issue.
(3) Use clockworkmod to flash a new rom.
And you're done. The entire process takes about 10 minutes at most.
Again, steps 1-3 should take you 10 minutes at most and the device is ready for use. If you find yourself frustrated by one of these steps or that you're spending more than 20 minutes, then the gtab is not for you and you need to get a mainstream device.
goodintentions said:
Again, steps 1-3 should take you 10 minutes at most and the device is ready for use. If you find yourself frustrated by one of these steps or that you're spending more than 20 minutes, then the gtab is not for you and you need to get a mainstream device.
Click to expand...
Click to collapse
This recommendation is of course assuming you have no determination whatsoever, and are incapable of learning anything new.
brettdwagner said:
This recommendation is of course assuming you have no determination whatsoever, and are incapable of learning anything new.
Click to expand...
Click to collapse
Look, for most people this device is a toy. I use it at work, and I suspect most people don't do this. Let's admit it. Modding a device isn't for everybody.
I went into modding the gtab as a total android newbie. And yet it took me all of 15 minutes to figure out how to install clockworkmod, repartition, and flash a custom rom. Then a week after I flashed a custom kernel.
You just can't ask everybody to go through the headache of modding a device if they have neither the will nor the time.
I said 15 minutes because that was my first time ever modding an android device. After that first time, it took me about 5 minutes to do my second device.
It's a simple process to go through. If a person gets stuck on any of those 3 steps, then I think it's best that they get a mainstream device. The gtab just isn't for everybody.
HeadRusch1,
I think you can handle modding the gTab. If you understand how a file system works, can extract a zip, and have already flashed a custom ROM then your about 90% of the way to a smooth running gTab. As mentioned above, you simply missed one step.
I understand the "10 minutes or forget it" argument, however I think it's wildly inaccurate when gauging a new user's potential competency with the gTab. If you find yourself frustrated then go read some more, search for a solution, or ask a question. It should take a long time to get comfortable modifying Android devices, there are tons of loosely documented best practices, but don't bail early because it's hard.
PS.
This assumes your looking for a device to tinker with. Goodintentions is right for users who are looking for iPad equivalent. I just assume that users looking for a cheap iPad rarely make it as far as XDA. And if they have, then it's a good opportunity to encourage further exploration.
The reason I gave the 20 minutes advice is because I've seen too many people buying the gtab thinking they got an ipad. The gtab isn't mainstream at all even though it's outsold a lot of the mainstream devices out there (ahem xoom) by several orders of magnitude. Customer support for the gtab is almost non-existent. And don't hold your breath for updates from viewsonic.
I absolutely love my gtab. I am currently running vegan ginger OC to 1.2ghz. The speed on my gtab is absolutely stunning. There's no jerking at all. My touchscreen is incredibly sensitive. Viewing angle has never bothered me. I love the full size usb where I can just put a memory stick in there just like my laptop. The autocad app is extremely helpful for me. In fact, it's been a whole week since I turned on my laptop.
That said, again, this device is not mainstream. Meaning it's not for most people. I am absolutely convinced that most people would be better off with something like the ipad or transformer.
Based on my experience, there are two types of people in the world of gadgets. (1) Those who sees a problem and see the end of the world and (2) those who sees a problem and try to get around it.
An example of #1 is my friend Sarah. She wanted to use my gtab to get a feel for it. She said the touchscreen bothered her and that she was more comfortable with a laptop touchpad more. And then she said "I don't know, I think I'll be better off with an ipad." LOL. Boy is she going to be so surprised to find out the ipad also uses the touchscreen rather than an touchpad.
Anyway, another example is one of my colleagues. After I told him the autocad app doesn't work with 3-D view yet, he acted like it was the end of the world. Me, I just use the side, top, and front views in my demos. Works just fine for me.
Anyway, I'm rambling now. The point is my experiences tell me most people are better off with something like an ipad or transformer. Since those devices are mainstream, people can't say "of course you can't do this, you can't do that". With the gtab, since it is not mainstream, the smallest inconvenience means the end of the world.
HeadRusch1 said:
I did one flash...to TNT version 4xx, and I loved it...but I'm finding I'm getting lots of Google Framework errors and generally just kind of want to start from scratch, over again.....go back to the latest version of the official viewsonic roms.
Sadly I didn't use clockwork or anything so I think my original files are history
I know there are lots of threads, and I tried to follow one about snagging a rom and moving it to the Root and all it does is re-install TNT I think I am "not getting something".
Can someone walk me through this....
Click to expand...
Click to collapse
Plug the gtablet into the computer.
Mount it for file transfer when prompted.
Check for an "update.zip" file at the root of the SD card (That's the tablet's 16gb internal memory). Delete it using your computer. That was causing TNT to be reloaded.
Here's the link to the original 3588 version they shipped with: http://tapntap.http.internapcdn.net/tapntap/viewsonic/update-smb_a1002-3588-user.zip Save it to your computer. Rename it "update.zip". Copy it to the root of the gtablet SD. Shut off the tablet. Unplug the USB cord. Restart with power & vol +
It should update.
If anyone notices a mistake, feel free to correct me. I've only flashed from stock 3588 to Vegan Ginger. So a whole 1x.
For what its worth, I tinkered and now I'm good.
Got NVFLASH working, went back to stock. Then went to Clockwork, then went to Vegan 5.1.1, then to CM7, now back to Vegan. I've found some apps that work and I'm liking it more. For the record, I own an Ipad2 as well.
Now, to those who chose to comment: You guys need to understand that many of those links are drowning in "extra information", and that is fine if you don't mind clicking hyperlink to hyperlink to do some trial and error, but now with multiple install path choices and whatnot, it gets confusing and it also means you have some time. I asked for someone, possibly someone in my shoes who has been down the path, to walk me through the steps.
Some of you did, some of you projected some assumptions with the underlying message of "RTFM".
This, too, was my first dip into the Android pool. Thanks for the help.
HeadRusch1 said:
I'm getting lots of Google Framework errors and generally just kind of want to start from scratch, over again.....go back to the latest version of the official viewsonic roms.
Sadly I didn't use clockwork or anything...
Click to expand...
Click to collapse
I had that issue and didn't have clockwork.
Solution:
1: install clockwork
2: boot into clockwork, and select 'fix permissions'.
3: reboot, tablet fixed
Here's my problem XDA Gods:
I've recently made a huge mistake, I was %&$#ing around with roms for the HDX and with Hashcode's Safestrap and had my phone fully rooted with the ADB drivers installed on my pc. I was using the default rom slot to operate(Yes it's stupid, but I have problems working with under 8gb of space and it was working fine.). Through an accidental factory reset I managed to delete my safestrap backup and screw up the current Rom. So I went into safestrap and tried to flash a new rom which suddenly wouldn't flash correctly. So I did advanced wipe and cleared everything and rebooted the device whilst still set to bootup from the default rom slot. My Proceeded to then bootloop the grey kindle logo. In a panic trying to fix it, I did the factory reset by holding the volume and power buttons (Another stupid move in my game of life.). Now when I plug it into a PC it reads the device as MTP USB Device and proceeds to fail installing Drivers that I've already installed. Adb wont recognize the device and I'm currently attempting to reinstall all my drivers.
To Sum It Up:
* My Device Can't Boot Into Safestrap
* My Device Can't Boot Past The Kindle Gray Logo
* My Computers wont recognize the kindle and calls it an MTP USB Device and fails driver installation.
*ADB also rejects my love.
Dear XDA Gods, I pray to thee for divine help and request the speedy help of thy talents. Many goats I will sacrifice for any that will help. I have scoured the Internet looking for a holy answer and have stumbled only upon ADB fixes to which I cannot. Please look upon my request and help me fly through this terrible storm.
From what I understand...
...this is a brick situation. Not to be a debby downer but I found myself in the same situation. I spent countless hours in the XDA forums and beyond, read every Android Cowboy post (who knows his way around this issue), tried a fastboot cable (didn't work), and even looked for a way to JTAG the internal memory - all to no avail. My advice - if you can't get ADB to wreckonize, accept your fate and flaunt your expensive taste in paperweights because, indeed, the stakes of being a tinkerer are high.
zomblitous said:
Here's my problem XDA Gods:
I've recently made a huge mistake, I was %&$#ing around with roms for the HDX and with Hashcode's Safestrap and had my phone fully rooted with the ADB drivers installed on my pc. I was using the default rom slot to operate(Yes it's stupid, but I have problems working with under 8gb of space and it was working fine.). Through an accidental factory reset I managed to delete my safestrap backup and screw up the current Rom. So I went into safestrap and tried to flash a new rom which suddenly wouldn't flash correctly. So I did advanced wipe and cleared everything and rebooted the device whilst still set to bootup from the default rom slot. My Proceeded to then bootloop the grey kindle logo. In a panic trying to fix it, I did the factory reset by holding the volume and power buttons (Another stupid move in my game of life.). Now when I plug it into a PC it reads the device as MTP USB Device and proceeds to fail installing Drivers that I've already installed. Adb wont recognize the device and I'm currently attempting to reinstall all my drivers.
To Sum It Up:
* My Device Can't Boot Into Safestrap
* My Device Can't Boot Past The Kindle Gray Logo
* My Computers wont recognize the kindle and calls it an MTP USB Device and fails driver installation.
*ADB also rejects my love.
Dear XDA Gods, I pray to thee for divine help and request the speedy help of thy talents. Many goats I will sacrifice for any that will help. I have scoured the Internet looking for a holy answer and have stumbled only upon ADB fixes to which I cannot. Please look upon my request and help me fly through this terrible storm.
Click to expand...
Click to collapse
---------- Post added at 12:18 PM ---------- Previous post was at 12:04 PM ----------
Google "Setting Up Your Kindle Fire Tablet for Testing" there is an article that might help to get ADB up.
This may be helpful to try to get ADB working. Also, a fastboot cable might be worth a try, though I don't think it will work if you don't get ADB working. Did you modify build.prop? Delete any system files?
I am sure that there is a way to restore through QPST:
http://forum.xda-developers.com/showthread.php?p=49862146
but I lack the skills to complete this process
Thanks
Thanks for the speedey responses guys, I'll try the QTSP method when I have time, but still thanks. Any other help is good to.
Same happened to me also , and i contacted with Amazon Customer Service. I explained whole situation ( that i tried the install gapps and bricked it like you - same way - ) they offered me a replacement. Then they sent me a new Kindle.
If you cant do anything just contact with them and explain everything. They will help im sure about that.
They are the most amazing Customer Service i've ever seen in my life. Just 2 days , i got my new Kindle and sent bricked one back.
Also they sent me a email for return shipping expenses. I used it at UPS and did not paid any money for return shipping.
Aren't they amazing?
Really!?!?
squee9 said:
Same happened to me also , and i contacted with Amazon Customer Service. I explained whole situation ( that i tried the install gapps and bricked it like you - same way - ) they offered me a replacement. Then they sent me a new Kindle.
If you cant do anything just contact with them and explain everything. They will help im sure about that.
They are the most amazing Customer Service i've ever seen in my life. Just 2 days , i got my new Kindle and sent bricked one back.
Also they sent me a email for return shipping expenses. I used it at UPS and did not paid any money for return shipping.
Aren't they amazing?
Click to expand...
Click to collapse
So even after ""breaking the system"" I'll get my money back. I dont have a warranty by the way, and I got it in December. Will that effect anything.
zomblitous said:
So even after ""breaking the system"" I'll get my money back. I dont have a warranty by the way, and I got it in December. Will that effect anything.
Click to expand...
Click to collapse
I have to admit I went through something very similar to you with my first HDX. I wiped the system without fully understanding it and afterwards it was bricked with my computer being unable to recognize it.
I also spent quite a bit of time looking for a solution but ultimately it was far easier talking to Amazon about this and having them send a replacement. Now with my second HDX I didn't make the same mistake twice.
I didn't tell the truth though. I just said that after I powered it on one day it would get stuck on the boot screen and after a troubleshoot run through Amazon offered a replacement.
Good luck.
Fastboot & the system
lawnnewm said:
...this is a brick situation. Not to be a debby downer but I found myself in the same situation. I spent countless hours in the XDA forums and beyond, read every Android Cowboy post (who knows his way around this issue), tried a fastboot cable (didn't work), and even looked for a way to JTAG the internal memory - all to no avail. My advice - if you can't get ADB to wreckonize, accept your fate and flaunt your expensive taste in paperweights because, indeed, the stakes of being a tinkerer are high.
---------- Post added at 12:18 PM ---------- Previous post was at 12:04 PM ----------
Google "Setting Up Your Kindle Fire Tablet for Testing" there is an article that might help to get ADB up.
This may be helpful to try to get ADB working. Also, a fastboot cable might be worth a try, though I don't think it will work if you don't get ADB working. Did you modify build.prop? Delete any system files?
Click to expand...
Click to collapse
Well I did the advanced system wipe, I think I may have just wiped off all traces of a rom by formatting the system, I havent touched the build.prop or any file like that, only format. Also I'll grab a fastboot cable off ebay and give tinkering a try,
Thanks
zXiC said:
I have to admit I went through something very similar to you with my first HDX. I wiped the system without fully understanding it and afterwards it was bricked with my computer being unable to recognize it.
I also spent quite a bit of time looking for a solution but ultimately it was far easier talking to Amazon about this and having them send a replacement. Now with my second HDX I didn't make the same mistake twice.
I didn't tell the truth though. I just said that after I powered it on one day it would get stuck on the boot screen and after a troubleshoot run through Amazon offered a replacement.
Good luck.
Click to expand...
Click to collapse
Well, best to have a working kindle and bad karma than an expensive paperweight, i'll give a fastboot cable a try first and use this as a last attempt. Thanks, also, when did you get the replacement and did you have a warranty?
zomblitous said:
Well, best to have a working kindle and bad karma than an expensive paperweight, i'll give a fastboot cable a try first and use this as a last attempt. Thanks, also, when did you get the replacement and did you have a warranty?
Click to expand...
Click to collapse
Rubbish. A bad kindle is a temporary thing. Bad karma lasts a lifetime & even if you can work it off, it's on a sliding scale approximately 1000:1.
The worst thing you can do is panic. 99.999% of devices can be recovered. However, you greatly increase your chances of being in that screwed .001% statistically by panicking & doing things like factory resetting or rebooting.
Personally, after sitting down to think about it, I can say I have actually borked my device 23 times. Nearly every three times, it was a different issue, since I was recreating issues to find solutions for others. To this day, I still have my FIRST HDX. I even got the update, the one that nobody can reverse. Guess what? I'm rooted, have SafeStrap & GAPPS still, because I didn't panic.
When you screw something up, you have to walk away. 3 out of 4 times, if you react to an issue without planning & reasoning, you will only make things worse, particularly if you really have no idea what you are doing & how Linux, Android Bootloaders & firmware in general work together. You don't need to know every detail, but a basic understanding at the very least. Listen, I am by no means a developer. I am a butcher hack of a coder, but I am a mechanical engineer & so I approach everything methodically, especially when dealing with something I do not know. Knowing your limits can be the most important thing to know at times & when you have stepped outside of your knowledge base, reacting with a guess rarely goes good. Just ask all the folks leaving Las Vegas casinos without their money. The bottom line is that bad things happen when you panic & let fear take hold. Bad things happen when you think you know more than you do.
What also helps me, is that this is my NEWEST username (you used to be able to have multiple, for different devices, etc), which is from 2006. I am pretty sure my first login was from 2002, maybe early 2003. When I joined I didn't do anything other than lurk, read, ask questions & follow things that interested me in IRC for a year & a half. I never even posted for the first 9 months I was around. I used PM & IRC, then it was only to ask questions to things I could find answers too reading through the earlier posts. Again, there are brand new members that understand & have abilities in technology that far outstrip anything I'll ever comprehend. Just like there were over a decade ago. Find those people & become friends. Follow one of the tutorials on building a basic app or building a rom like CM or AOSP or any of the other open roms from scratch. You'll learn something new, I garuntee it & it will come in handy some day, even if it's just a hobby. Of course things are different at XDA these days. It used to be that EVERY member was here to learn how to do these things for themselves & to share the experience & what was learned. Now, you still have some of those types, but predominantly, you have members that are here just because they want someone else to make a theme, or mod, or fix for them & they have no desire to contribute.
At any rate, I don't have the time to keep up with all the bootloops & bricks these days. Right now, work is crazy busy & that is what pays the bills, so it takes precedence over everything else. I'll start answering PM's & taking a look at borked devices again when things slow down again, however, I think I could probably recover 8 out of 10 if I had it in my hands & so could you. For those of you unwilling to give up, I suggest you read around other forums, check out some of the qualcomm developer forums & find some of the very talented developers that participate in those communities too. Most of them WILL take the time, not necessarily to fix your problem, but to answer questions & even to teach you a thing or two, if you are sincere about wanting to learn & not just looking for the first sucker to fix whatever problem you have.
GSLEON3 said:
Rubbish. A bad kindle is a temporary thing. Bad karma lasts a lifetime & even if you can work it off, it's on a sliding scale approximately 1000:1.
The worst thing you can do is panic. 99.999% of devices can be recovered. However, you greatly increase your chances of being in that screwed .001% statistically by panicking & doing things like factory resetting or rebooting.
Personally, after sitting down to think about it, I can say I have actually borked my device 23 times. Nearly every three times, it was a different issue, since I was recreating issues to find solutions for others. To this day, I still have my FIRST HDX. I even got the update, the one that nobody can reverse. Guess what? I'm rooted, have SafeStrap & GAPPS still, because I didn't panic.
When you screw something up, you have to walk away. 3 out of 4 times, if you react to an issue without planning & reasoning, you will only make things worse, particularly if you really have no idea what you are doing & how Linux, Android Bootloaders & firmware in general work together. You don't need to know every detail, but a basic understanding at the very least. Listen, I am by no means a developer. I am a butcher hack of a coder, but I am a mechanical engineer & so I approach everything methodically, especially when dealing with something I do not know. Knowing your limits can be the most important thing to know at times & when you have stepped outside of your knowledge base, reacting with a guess rarely goes good. Just ask all the folks leaving Las Vegas casinos without their money. The bottom line is that bad things happen when you panic & let fear take hold. Bad things happen when you think you know more than you do.
What also helps me, is that this is my NEWEST username (you used to be able to have multiple, for different devices, etc), which is from 2006. I am pretty sure my first login was from 2002, maybe early 2003. When I joined I didn't do anything other than lurk, read, ask questions & follow things that interested me in IRC for a year & a half. I never even posted for the first 9 months I was around. I used PM & IRC, then it was only to ask questions to things I could find answers too reading through the earlier posts. Again, there are brand new members that understand & have abilities in technology that far outstrip anything I'll ever comprehend. Just like there were over a decade ago. Find those people & become friends. Follow one of the tutorials on building a basic app or building a rom like CM or AOSP or any of the other open roms from scratch. You'll learn something new, I garuntee it & it will come in handy some day, even if it's just a hobby. Of course things are different at XDA these days. It used to be that EVERY member was here to learn how to do these things for themselves & to share the experience & what was learned. Now, you still have some of those types, but predominantly, you have members that are here just because they want someone else to make a theme, or mod, or fix for them & they have no desire to contribute.
At any rate, I don't have the time to keep up with all the bootloops & bricks these days. Right now, work is crazy busy & that is what pays the bills, so it takes precedence over everything else. I'll start answering PM's & taking a look at borked devices again when things slow down again, however, I think I could probably recover 8 out of 10 if I had it in my hands & so could you. For those of you unwilling to give up, I suggest you read around other forums, check out some of the qualcomm developer forums & find some of the very talented developers that participate in those communities too. Most of them WILL take the time, not necessarily to fix your problem, but to answer questions & even to teach you a thing or two, if you are sincere about wanting to learn & not just looking for the first sucker to fix whatever problem you have.
Click to expand...
Click to collapse
Thanks for the pep-talk, I haven't even thought about giving up, and I don't really want to just get out the easy lying way. But sadly my problem is one of few and will take time even with the help of power techies. I really only have one option at the moment and that is to continue troubleshooting and ignore everyone who just says that i have acquired a taste in paperweights. And Thanks anyway, means alot when a member takes time just to cheer ya on.
zomblitous said:
Well, best to have a working kindle and bad karma than an expensive paperweight, i'll give a fastboot cable a try first and use this as a last attempt. Thanks, also, when did you get the replacement and did you have a warranty?
Click to expand...
Click to collapse
Replacement was expediated by Amazon so in two days.
You have a limited warranty for a year. You just have to convince Amazon that your problem falls under that.
Edit: It's admirable to try and fix it yourself but in my opinion it's far too time consuming.
1 year then...
zXiC said:
Replacement was expediated by Amazon so in two days.
You have a limited warranty for a year. You just have to convince Amazon that your problem falls under that.
Edit: It's admirable to try and fix it yourself but in my opinion it's far too time consuming.
Click to expand...
Click to collapse
Well I have about a year then.
[Q] "Retroactive Bricking" or "spontaneous" hardware fault? [Xpost One X/X+ Help]
*PSA: This will be crossposted in xda GenerAL Q&A and HTC One X+ forums, I hope cross posting is allowed, haven't seen it mentioned in rules.*
Hi all,
Quick disclaimer: I've been lurking parts of xda now and again for a couple years now, have flashed a couple of phones and tablets now and again for mainly practical reasons, recently getting more interested in it as a ""fun" interest or "hobby".
SO: I am very aware that this is my first post, the rules, search function, etc. ..
BUT: After extensively searching both google and specifically xda to help me resolve this issue *myself*, I decided to create an account and post. I'm sorry if this Q should have been put in the newbie thread, my assessment was that it probably has no place there.
ALSO PLZ NOTE: What was meant to be a succinct summary and question somehow turned into a condensed but complete rundown of events, so here is a...
TL;DR:
- Replaced HTC One X+ display/digitizer unit myself, ran fine for 5 weeks.
- Then: flashed twrp 2.7x or 2.8, not sure anymore, before installing Android HD Revolution 33.1 by mike1986, and following the official instructions, which ran great for about week until my phone spontaneously BRICKED THE F*CK OUT COMPLETELY.
(yes, true brick, paperweight, robot-corpse, whatever)
=> Question: IS "RETROACTIVE/RETROGRADE BRICKING POSSIBLE/A "THING"??
If so, what could I have done wrong? (POSSIBLY something to do with a bootimage of firmware that I was sure I had the up to date version of... dunno though).
=========================================================================
About 6 weeks ago:
- Cracked the display of my HTC One X+ badly by dropping it onto concrete-type floor at a rave/party
=> Decided to try and replace it myself, researched for a good while (talking several days here, 90s/00s kids),
=> Decided to replace the display/digitizer unit myself to save money and gain knowledge.
Repair process was challenging and nearly as nerve wracking as playing the WSOP (not kidding, have played it three times), had an issue immediately after putting it back together where it suddenly wouldn't charge AT ALL anymore (NO LED), and overheated, and had unusually fast battery drain of its remaining charge (which never ran out completely before resolving that issue, since I kept turning it off whenever possible).
=> Took it apart and put it together again XX times until realizing the power switch flex cable kept slipping out of its two (jawbone?) connectors during putting it back together (I was doing something wrong with the flex positioning).
=> This resolved the issue.
=> Felt like a hero and that I win at life (since this phone has a rep as being hard to meddle with, and this was my first time even opening, let alone taking apart a smartphone).
=> Continued joyful phone shenanigans for over one month.
=> THEN: Decided to root it, mainly because there was a particular app I wanted that required root ("Quick reply for Whatsapp/Pushbullet", for the curious).
My previous, very limited rooting/flashing experiences =
- Google Nexus One (CWM/Cyanogen) a few times, years ago
- Galaxy Tab 10.1 (CWM/Cyanogen 10.1 ages ago, TWRP/Omnirom Kitkat 4.4.4 recently) a couple times.
So, did my research (or so I thought..?) for this particular custom ROM, decided to go for Android Revolution HD for HTC One X/+ 33.1 by mike 1986 (because it looked fckin awesome, and it was, while it ran) and loved the sh*t out of my "new" phone for about a week. Especially the vastly improved battery life seemed almost surreal, a big deal for a fixed-battery phone.
Then, ONE FATFUL EVENING in a bar, I remember looking at my phone and seeing 35% left, (days before it would've been an amazing 70-80% on an avg. day), which may not be relevant as it was my birthday, so had been using it a lot that day => may be a moot point
- Next time I looked at the phone ( < 1 hour without active use for sure) it was dead.
"Hmmmm," thought slightly drunk me. Whatever, charge it later, weird sh*t happens.
- Got home later, charged it over night after booting it with usb cord attached (mains).
Seemed normal, I even set an alarm.
=> Alarm never rang because it was in a powered-off state again come morning, despite all-night charging.
=> It booted to HTC logo. Seconds later, it turned off again. Held down power again, all I saw was the soft touch buttons flashing red a few times. After this it unexpectedly became (or was secretly crowned):
!! COMPLETE AND UTTER FCKNG KING BRICK OF BRICK COUNTRY AND ATTACHED TERRITORIES !!
No power on with or without volume up/down held for whatever amount of time;
No charging, no heating up when "charging";
No LED in any colour or flashing frequency, ever;
No response after hours and days of charging on different USB cables on PC/wall socket;
PCs and laptops don't register a sign of anything when it penetrates their port parts, etc etc...
...
.Even that semi-mystical bright-light-exposure-while-charging "light sensor manipulation" thing (which apparently worked for a lo of people with similar issues) did nothing for the cause.
Promotion: *Paperweight status successfully acquired.* Yay.
=====================================================
Now, obviously my first thought was that the power flex that gave me trouble during display replacement probably slipped again., somehow (I had taped it down solidly I thought).
=> SO I opened it once again, flex position seemed ok, but I wasn't sure of its functionality as it did look kind of battered from the somewhat unprofessional repair I had conducted on it (which I openly admit to, though I really did try my absolute best).
- Spontaneously took mainboard/battery combo to a local independent phone/accessory shop after being told they'd take a look for free
(I was in there was in there buying a microsim adapter so I could use my ancient Nexus One, since my GF has my old S2 now, which she kindly offered back, but its hers now, so nah. Great phone though.)
=>Shop's advice echoed my thoughts: Flex cable may be screwed, I may have damaged it by bending in the wrong direction/too often, and that damage somehow didn't manifest until much later. I didn't mention the recent rooting + flashing as I deemed it irrelevant at the time.
Their secondary thoughts: Battery or mini-usb port fukt, (which would require soldering, which they don't even offer).
=> SO, feeling confirmed in my layman's assessment, I cheaply got a pristine new replacement flex on ebay, double checked all videos/tutorials, implemented the damn thing with considerably more skill/experience and even higher anticipation. What happened next was shocking:
Absolutely nothing, obv.
=> Did an additional epic f*ckton of internet/forum research, found similar problems and some resolutions, but no real answers, probably because my main problem translates to a kind of hybrid question.
So here I am now am with my core question:
Is it possible to FULLY brick an HTC/any smartphone but not become aware of this until one week later, when the device dies OVER ONE WEEK of reliable and amazing performance?
(and if yes, what aspect/stage of the flashing process is this likely related to?)
If the answer is NO, it must be a hardware fault with probability rank (I think)
:
1.) Battery dead for whatever reason
2.) Mini USB OR mainboard/integral component (equal rank as not sure), possibly caused by incompetent repair, but why or how would this express itself over a month later??
3.) Other, which I'm not aware of.
While researching new ROMS for the N1, I realized that I may have messed up on the "bootimg part" of the flashing process of the Revolution ROM, a part I found v. confusing in the instructions, even after rereading them many, many times. It was about the most recent firmware, which I was pretty sure I had anyway, since it was unrooted before and I do remember installing some firmware updates over the air.
I still did my best to follow the instructions though.
=> Maybe this has something to do with it, i.e. the hardware can't accept a charge because the software allowed it to become too uncharged (a fairly paradox concept to me, but apparently it can happen. Guess it's like a BIOS-type thing).
Thank you for anyone who read this far!
As it stands, I refuse to give up hope so soon after experiencing that rush of having fixed it myself.
Any specific or general help, tips, hints, pointers, replacement phones (One M8 or S5 plz., Iphones will go straight on ebay) would and will be greatly appreciated!!
The obvious choice is to get a new battery and see what happens, but I'm not sure if I wanna sink any more money into this phone, only to later find out the mainboard is at fault (not worth the money replacing), AKA "get a new phone without a contract", which would more than suck for me financially atm (Im ignoring my N1 here, which I love, but don't wanna be stuck with, esp. as it has the standard-issue broken power button (which I actually had repaired once under warranty, back in the ol' days of yore some prefer to refer to as 2009.
So guys: What's my move, if there is one, besides going to a local/online service centre (I live in Germany btw.) and probably paying unproportionate cash money to even have it looked at?
Cheers, thanks, merci, danke
PS: Just saw the polling function, so I attached one just for the hell of it, to see what happens (never used one before).
If you feel both qualified AND so inclined as to pass judgement on this here serious business, please indicate what you think may be the cause of my issue.
Poll is in "General QA" Forum original post: http://forum.xda-developers.com/general/help/retroactive-bricking-spontaneous-t2948954
*BUMP 1*
Come on guys, I know it's a wall of text, but can't someone at least answer the TL;DR?
=> Is is possible to flash a custom rom which then (possibly because of improper installation) causes the phone to brick about a week later?
Simple question surely!
bear.are.cool. said:
*BUMP 1*
Come on guys, I know it's a wall of text, but can't someone at least answer the TL;DR?
=> Is is possible to flash a custom rom which then (possibly because of improper installation) causes the phone to brick about a week later?
Simple question surely!
Click to expand...
Click to collapse
Oh yea I was meant to reply to this... Reading what I can of this, sounds like offmode charging wasn't working (Sounds like to me not 100% is it)
You can try this http://forum.xda-developers.com/showthread.php?t=2576405 <--- Windows only
That is a last ditch attempt at charging....Which is what it sounds like to me, please tell me If I'm wrong.
And NO, providing your device is S-ON you CANNOT BRICK IT
thanks
Lloir said:
Oh yea I was meant to reply to this... Reading what I can of this, sounds like offmode charging wasn't working (Sounds like to me not 100% is it)
You can try this http://forum.xda-developers.com/showthread.php?t=2576405 <--- Windows only
That is a last ditch attempt at charging....Which is what it sounds like to me, please tell me If I'm wrong.
thanks
Click to expand...
Click to collapse
Thanks for the reply!
I believe I actually ran into that (linked) post during my previous research, but just as is the case now, I don't get how I'm supposed to run a .bat from windows that influences the phone when windows doesn't recognize a thing when I plug the device in. Not in device manager, NADA.
EDIT: I do have S-ON, yes. BTW thanks for trying to help, but again, my fundamental question: Is "retroactive bricking" as I call it possible in theory?
bear.are.cool. said:
Thanks for the reply!
I believe I actually ran into that (linked) post during my previous research, but just as is the case now, I don't get how I'm supposed to run a .bat from windows that influences the phone when windows doesn't recognize a thing when I plug the device in. Not in device manager, NADA.
EDIT: I do have S-ON, yes. BTW thanks for trying to help, but again, my fundamental question: Is "retroactive bricking" as I call it possible in theory?
Click to expand...
Click to collapse
To get it working you need the android sdk tools. You also need to install HTC SYNC + Drivers then uninstall HTC sync leaving the drivers behind.
And In answer to your Q. No
After reading the TL;DR
Lloir said:
To get it working you need the android sdk tools. You also need to install HTC SYNC + Drivers then uninstall HTC sync leaving the drivers behind.
And In answer to your Q. No
After reading the TL;DR
Click to expand...
Click to collapse
Hmm, ok. I'll give it a go. So essentially, if I manage to implement this method correctly and I still get nothing, theres gotta be a hardware fault, correct?
bear.are.cool. said:
Hmm, ok. I'll give it a go. So essentially, if I manage to implement this method correctly and I still get nothing, theres gotta be a hardware fault, correct?
Click to expand...
Click to collapse
Probably
Sent from my Nexus 7 using Tapatalk
Lloir said:
Probably
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I'm trying to find a good guide on how to go through with this, as the post you linked is helpful but a bit vague.
One more question: When you say "offmode charging" is that synonymous with "offline charging"?
EDIT: Also, what I really do not get about the procedure outlined in the post is the following line
"Run the following script as a batch file while your phone is in USB fastboot mode."
=> How do i put this brick into anything mode?? It's in constant brick mode!
bear.are.cool. said:
I'm trying to find a good guide on how to go through with this, as the post you linked is helpful but a bit vague.
One more question: When you say "offmode charging" is that synonymous with "offline charging"?
EDIT: Also, what I really do not get about the procedure outlined in the post is the following line
"Run the following script as a batch file while your phone is in USB fastboot mode."
=> How do i put this brick into anything mode?? It's in constant brick mode!
Click to expand...
Click to collapse
Just a question. When you replaced the display, did you tamper with brightness control? I mean were you able to change the brightness after your repair?
And secondly, logically, I think its a hardware fault. Whatever happened, might have happened over the week or happened that specific day. Maybe the wire connecting the charger socket to the phone's board got cut/damaged during repair but worked for a while, then it imght have touched another wire and short circuited maybe?
Or maybe something inside was loose, and something happened to the phone, it fell or something, and a component got broken?
I would suggest comparing your internals to the internals of another HOX+ whether on youtube or whatever. And try to check the wire connecting the charger socket to the board. Another possibility is the battery got damaged as you stated. The last idea is, (And I hope it didn't get to that), the wire short circuited and fried the board.
All my theories are just as stated.. Theories, which may or may not be true. If there is an HTC Care center, I would suggest that you go to them, atleast for debugging.
Best of luck
Hi Everyone, I need some serious help - thanks in advance!
I have a LG Enlighten phone - I am a tech, although I am new to the whole smartphone thing (ya, I know, where have I been lol). Anyway, as you probably know it has limited internal storage. So I have a Sandisk 32gb micro sd card installed where I move things over to it to keep space open on the internal. The phone is rooted.
Ok, things were going well - and I am not sure what happened precisely, but obviously I must have moved something over to the sd card I shouldn't have. The phone went wonky on me after a reboot. I got stuck in a boot loop I could not recover from. So I did a factory reset (power button, home, and volume up). That went just fine. I activated just fine to. Problem is after that all I get is: Sorry! the application com.android.lgsetupwizard (process com.android.lgsetupwizard)has stopped unexpectedly. please try again.
You can press the force close button a million times (I probably have) and nothing happens. I have tried EVERYTHING to try to clear this and I can't get passed it. I've spent two days online reading forums, web pages, watching youtube videos - nothing has helped. Problem is, since I did a factory reset its back to defaults (I am assuming) meaning USB debugging and mounting is turned off because it is turned off as default. I can't get passed that infernal screen to turn it back on.
I don't have any data on here that I care about I just want my phone back. I don't mind flashing the rom but for the life of me I can't get at it!
When I go into restore mode, at least with the enlighten it doesn't give you options - it just shows the picture of the android for a few seconds then reboots. No idea what it's doing there.
I tried re-formating the micro sd card thinking maybe it was picking something up from there, that didn't seem to do anything.
I have Android Studio installed, I was hoping to do something through it - but again the phone isn't mounting when plugged into my laptop (windows 7) - it was before - no doubt because that feature is turned off because of the factory reset.
If you have ideas, please speak in small words with lots of steps. Thanks.
HELP!
Pandora1331 said:
Hi Everyone, I need some serious help - thanks in advance!
I have a LG Enlighten phone - I am a tech, although I am new to the whole smartphone thing (ya, I know, where have I been lol). Anyway, as you probably know it has limited internal storage. So I have a Sandisk 32gb micro sd card installed where I move things over to it to keep space open on the internal. The phone is rooted.
Ok, things were going well - and I am not sure what happened precisely, but obviously I must have moved something over to the sd card I shouldn't have. The phone went wonky on me after a reboot. I got stuck in a boot loop I could not recover from. So I did a factory reset (power button, home, and volume up). That went just fine. I activated just fine to. Problem is after that all I get is: Sorry! the application com.android.lgsetupwizard (process com.android.lgsetupwizard)has stopped unexpectedly. please try again.
You can press the force close button a million times (I probably have) and nothing happens. I have tried EVERYTHING to try to clear this and I can't get passed it. I've spent two days online reading forums, web pages, watching youtube videos - nothing has helped. Problem is, since I did a factory reset its back to defaults (I am assuming) meaning USB debugging and mounting is turned off because it is turned off as default. I can't get passed that infernal screen to turn it back on.
I don't have any data on here that I care about I just want my phone back. I don't mind flashing the rom but for the life of me I can't get at it!
When I go into restore mode, at least with the enlighten it doesn't give you options - it just shows the picture of the android for a few seconds then reboots. No idea what it's doing there.
I tried re-formating the micro sd card thinking maybe it was picking something up from there, that didn't seem to do anything.
I have Android Studio installed, I was hoping to do something through it - but again the phone isn't mounting when plugged into my laptop (windows 7) - it was before - no doubt because that feature is turned off because of the factory reset.
If you have ideas, please speak in small words with lots of steps. Thanks.
HELP!
Click to expand...
Click to collapse
could you just do a factory reset with the buttons on it?
or has that been tried before
---------- Post added at 07:39 PM ---------- Previous post was at 07:37 PM ----------
btw, i havent been here that long but i dont think you will get much responds because this is on a general thread, i think it would be better if it was in a helping section
Phurkus said:
could you just do a factory reset with the buttons on it?
or has that been tried before
---------- Post added at 07:39 PM ---------- Previous post was at 07:37 PM ----------
btw, i havent been here that long but i dont think you will get much responds because this is on a general thread, i think it would be better if it was in a helping section
Click to expand...
Click to collapse
****
I mentioned that I did a factory reset - but I didn't mention I did it several times (more than that even). Again, the enlighten doesn't really give you a lot of options when you do one. It shows a picture of the android and a file folder for a few seconds - maybe 10... then it boots. there's no option, no text, no choices, nothing. A bit confusing to be honest. Then it boots up, you get the language choice and activation call (which goes through fine) and then wham! back to hell and that freakin' error message.
BTW I posted here because there is no specific forum for the enlighten phone - I didn't want to post in a forum for another phone and get yelled at. Suggestions on a forum? and thanks for taking the time to reply! :0
Pandora1331 said:
****
I mentioned that I did a factory reset - but I didn't mention I did it several times (more than that even). Again, the enlighten doesn't really give you a lot of options when you do one. It shows a picture of the android and a file folder for a few seconds - maybe 10... then it boots. there's no option, no text, no choices, nothing. A bit confusing to be honest. Then it boots up, you get the language choice and activation call (which goes through fine) and then wham! back to hell and that freakin' error message.
BTW I posted here because there is no specific forum for the enlighten phone - I didn't want to post in a forum for another phone and get yelled at. Suggestions on a forum? and thanks for taking the time to reply! :0
Click to expand...
Click to collapse
***
I just thought I would post how I just resolved this. I got passed it by getting a PHONE CALL! I flipped the screen up to answer, yanked away. After the call was done I didn't do anything, the other party hung up. Then there was a REALLY long pause on the phone - the screen went black. I waited a couple of minutes, pushing the buttons did nothing. Then finally - the home screen came up. NO MORE BEING PROMPTED FOR A FORCE CLOSE! Yea! And it appear everything is working. Now before it decides to break again I want to flash the rom (I am running the bloated stock rom). Thanks for checking this out. and if you're looking at this cause you're having the same problem, I really hope what worked for me works for you too!
Pandora1331 said:
***
I just thought I would post how I just resolved this. I got passed it by getting a PHONE CALL! I flipped the screen up to answer, yanked away. After the call was done I didn't do anything, the other party hung up. Then there was a REALLY long pause on the phone - the screen went black. I waited a couple of minutes, pushing the buttons did nothing. Then finally - the home screen came up. NO MORE BEING PROMPTED FOR A FORCE CLOSE! Yea! And it appear everything is working. Now before it decides to break again I want to flash the rom (I am running the bloated stock rom). Thanks for checking this out. and if you're looking at this cause you're having the same problem, I really hope what worked for me works for you too!
Click to expand...
Click to collapse
Ayy greate job OP! glad to hear that. hope you dont do the same mistake twice
Phurkus said:
Ayy greate job OP! glad to hear that. hope you dont do the same mistake twice
Click to expand...
Click to collapse
lol you and me both!
This was a learning experience, it was the first time ever I have had a phone with an external micro sd card which holds more data than the actual phone. Also, my first Android. So I am thrilled to have my phone back - I had been messing with it late last night when this happened and didn't sleep at all because, well, I thought I just bricked my phone!
Lessons learned:
You can move just about any app you want to the sd card, no problem - but what you don't want to move are the operating system files/apps. Nor do you want to convert them to "user apps" and move them. Or at least I don't. Since I don't quite understand how it works, and what that does. I had THOUGHT it would just mean everything would run from my sd card - maybe a smidge slower - but it would run. Well, I was wrong. lol. So I am passing that tidbit along.
Also, in the future, if anything like this happens - don't be so quick to do a factory reset, cause you now take away the ability to connect via usb... It is a last resort, not a panicked, go to move. At least not for me.
And, there is something called Rom Managers - install one on your freakin' phone. I didn't know about them. So I didn't have one. I could have resolved this whole thing sooner if I had (maybe).
Lastly, before you do too much - have someone call you or call yourself from another phone to see what happens. It fixed my problem. Of course I won't be rebooting before I flash my rom (wow, that sounds dirty lol) cause I fear the same thing happening...
That's all I wanted to share - cause that's what I learned. Sorry if this is super obvious to people - it sure wasn't to me.
Pandora1331 said:
lol you and me both!
This was a learning experience, it was the first time ever I have had a phone with an external micro sd card which holds more data than the actual phone. Also, my first Android. So I am thrilled to have my phone back - I had been messing with it late last night when this happened and didn't sleep at all because, well, I thought I just bricked my phone!
Lessons learned:
You can move just about any app you want to the sd card, no problem - but what you don't want to move are the operating system files/apps. Nor do you want to convert them to "user apps" and move them. Or at least I don't. Since I don't quite understand how it works, and what that does. I had THOUGHT it would just mean everything would run from my sd card - maybe a smidge slower - but it would run. Well, I was wrong. lol. So I am passing that tidbit along.
Also, in the future, if anything like this happens - don't be so quick to do a factory reset, cause you now take away the ability to connect via usb... It is a last resort, not a panicked, go to move. At least not for me.
And, there is something called Rom Managers - install one on your freakin' phone. I didn't know about them. So I didn't have one. I could have resolved this whole thing sooner if I had (maybe).
Lastly, before you do too much - have someone call you or call yourself from another phone to see what happens. It fixed my problem. Of course I won't be rebooting before I flash my rom (wow, that sounds dirty lol) cause I fear the same thing happening...
That's all I wanted to share - cause that's what I learned. Sorry if this is super obvious to people - it sure wasn't to me.
Click to expand...
Click to collapse
there you go OP! what i do is i have an old LG phone that i like to mess with or put apps to try them out from here. and it its good, i put it on my regualr phone.
sounds like you learned and just bumped yourself up the ladder of software knoledge today!
Phurkus said:
there you go OP! what i do is i have an old LG phone that i like to mess with or put apps to try them out from here. and it its good, i put it on my regualr phone.
sounds like you learned and just bumped yourself up the ladder of software knoledge today!
Click to expand...
Click to collapse
---
Absolutely! I love to learn especially stuff I don't know much about - but... I wish it didn't happen in such a panic lol. Oh well, lessons learned... I wouldn't have been in a panic if it weren't my only phone, but it is. :0
I also wish it were easier to learn - it seems (at least to me) that every phone has enough unique characteristics that you really have to be specific about model and o/s. It makes searching for answers that much more difficult. What works for one person won't work for all or even most. You have to do a lot of trial and error. I suppose if I were a programmer perhaps it would be more clear to me on how these things tick. I am tho, just a tech - I fix and build stuff. Although I do have some programming ability, I would never even dream to call my pathetic scribblings code. lol Scripts yes, but really, really simple ones and thing more complex is just greek to me.
Is there any good place to see what kind of custom roms work best with the enlighten? I am thinking of putting one on there... I hate the bloatware stock rom.
Pandora1331 said:
---
Absolutely! I love to learn especially stuff I don't know much about - but... I wish it didn't happen in such a panic lol. Oh well, lessons learned... I wouldn't have been in a panic if it weren't my only phone, but it is. :0
I also wish it were easier to learn - it seems (at least to me) that every phone has enough unique characteristics that you really have to be specific about model and o/s. It makes searching for answers that much more difficult. What works for one person won't work for all or even most. You have to do a lot of trial and error. I suppose if I were a programmer perhaps it would be more clear to me on how these things tick. I am tho, just a tech - I fix and build stuff. Although I do have some programming ability, I would never even dream to call my pathetic scribblings code. lol Scripts yes, but really, really simple ones and thing more complex is just greek to me.
Is there any good place to see what kind of custom roms work best with the enlighten? I am thinking of putting one on there... I hate the bloatware stock rom.
Click to expand...
Click to collapse
i learned that lesson too when putting a rom on my phone, not everything works for everyone.
the best place i can think of is on here lol. i just assume the rom with the most replys and views is the most popular. you can try googleing because i know there are other mobile development forums out there that work on other roms. but i know this is the most popular forum.
THANK!YOU OK guys once again and at the same time, in advanced, THANK!YOU
so i am in serious need of some help or someone to just give it to me straight and just put me out of my misery. its been a couple weeks now and ivr put in huge amounts of time trying to search out a solution. Now it's just cruel, if I were and animal they would have put me down weeks ago
I already apologize, I'm going to do my very best to keep this short ( as possible ) and to the point, I have a tendency ( more like debilitating compulsive disease ) of rambling while simultaneously over descriptive, and my effin' phone is broken!!! Give me a break. Ok here we go I promise
This is my first thread / post, believe me I have searched independently, finding a TON on parts but no real conclusion or fix, or of it was there I meed my hand held. So I am, was, running a Verizon galaxy s4, rooted (king root), lollipop 5.1.1
Situation of my phone right now
Ultimately the phone won't boot past the Verizon logo / loading screen, whatever that phase ( if it even is one ) is called. No amount of time has done anything for it. It leaves me with only 3 different options ( attempting to boot normally being the first )#2 I can get info "Odin mode" <holding Vol Down + Power + Home>as its named at the top of the prompt. Where basically I've deduced that it's trying to update or install a custom operating system, from where? I'm not sure, the cloud I reckon, since it warns me not to turn it off and I dont have it plugged in, or anything else provided for it to do much of anything, don't think I even downloaded Odin that I know of. I'm thinking I forgot to mention I do not have access to a computer currently. Quick update: or I just forgot to mention but if you haven't guessed it, I have no immediate access to a computer, and while I'm here I also was not far enough to save a backup. Thanx
continuing. . 3rd and final pathway open to me Recovery Booting<holding Vol Up + Power + Home> I'm sure you guys know the one, where I have tried every option ( more than twice ) to, unnecessary to say I'm realizing, no avail. Had even come to terms with what appeared to be my only hope in sigbt and attempted the wipe / factory boot. And if that worked and changed anything I guess I misunderstood the whole concept of factory wipe. So that's about where I stand currently.
Events leading up to disaster. ..
I was in the overall process of installing xpose of course! I had already performed a successful Root thanks to kingroot, verified with root checker. Had moved onto the slow going process of learning to get TWRP going, here's where it starts to get a little messy... So it goes without saying that I was having.. let's say difficult time with TWRP. I went through one of the pains of the overall process and located my version of framework ( or so I had thought, quite a few people thought actually ( ok so thinking back on it I never really looked at the date on any of the threads so this whole chain of events could have been last year for all I know, and I just started at the beginning and got the full ride and experience everything those in this community running lollipop 5+ had to go through. And when I say chain of events I'm talking about the first rounds of xposed for Samsungd and lollipop. And the nightmare left in its wake. Evident in the step by step UPs and DOWNs left in the threads) so being not 100% correct i had the right framework I put that on hold awaiting a few replies. I then began to attempt twrp once again, this time for a backup . Once again I found myself hating twrp. Defeated I put it all aside for a few days.. upon retire I began reading up on everything all over again. Came across a very helpful ( helpful now, very much not so in the time I'm currently speaking of ) app I bought "Super-Sume". Which sounded like it was going to help out and make things not only easier but get me back on track and going in the right direction again. Well somehow as it was performing it's first stage of removing kingroot and all the extra goodies that they have been accused of adding in as well, the app froze. Not sure I I froze exactly but it had not moved or gained any progress in quite a while, I believe some or most of this to be caused, I recently found out as I was attempting the whole adventure over again on another ( older, less expensive) phone. The one I'm currently on. Just a galaxy lite or something. But come to find out you cannot use the latest , or those after like 4.90 versions of kingroot, or the super-sume won't work, and possibly do what it did to me maybe? ?? But after it froze or whatever it restarted when I shut if off and we find ourselves having come around full circle now.
Once Again ! Thank You I really just want to thank those of you that made it all the way through this never-ending thread. Just being dedicated / motivated enough to get this far, gives me high hopes we will be able to get through this ! The hard parts over, right?
Once Again ! Thank You