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
Related
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
Curious for those of us without the proper tools or the know how to do this properly. This works for the Note but can also work for any other device.
Just study up. Read the instructions. Visit the general section and read. Flashing is easy. Best to just learn. Watch some YouTube videos. Be careful. Have fun.
Sent from my SAMSUNG-SGH-I717 using xda premium
NightHawkUndead said:
Just study up. Read the instructions. Visit the general section and read. Flashing is easy.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
You missed the part in the OP about not having the proper tools. No amount of reading or studying or preparing can help when the tool is made for Windows and you're running a Mac (or no computer at all).
OP -- I'm sure there's plenty of people on here who do (or would help you with) flashing ROMs but a lot of that is going to depend on where you live. Best bet: Craigslist and see if you can find someone in the Cell Phones section who does that. Denver (yes... where I am) has a ton of shops that will flash custom ROMs for you - but of course they want you to pay for the privilege.
However - I would really recommend finding someone local and trustworthy. Don't EVER send someone your device, because let's be honest - you'll most likely never see it again unless you're sending it to a real business.
bmstrong said:
Curious for those of us without the proper tools or the know how to do this properly. This works for the Note but can also work for any other device.
Click to expand...
Click to collapse
First....start off at YouTube, and watch people root the Nexus One over ADB. You'll learn a few tricks...but most importantly, you'll learn your way around the device manager and the command prompt in windows. While it may seem daunting at first...there are only a few commands you'll need to learn.
That solves the problem you'd have with rooting and installing Clockwork Mod (the basis for flashing any new ROMs.
Lastly...if you can find a valid windows installation (or you can even use a 90 day trial version of windows 7 enterprise) you'll want to install boot camp on your Mac...which allows you to run windows on your Mac. Easily.
By no means am I an android powerhouse, but I do work in IT and am handy with a device manager, various hosts, and windows and Mac.
The next best option would be to offer someone here 10-20 bucks to show you over Skype, or do it for you using go to meeting.
Remember 1 thing. Its actually hard to brick a device if you do a few things.
Only flash RC or final versions of ROMs. In general. These have been THOUROUGHLY tested. The more feedback for a ROM the better. Learn to search threads here frequently.
Don't go about customizing the software by flashing mods (until your more comfortable). Android provides a perfect host system for providing customization via the Play store. Widgets...toggles...backgrounds. Notification tweaks, and almost everything else you'll need can be found on the play store and easily uninstalled.
Lastly...always keep a backup of you're system
via Nandroid, and keep a backup of your apps with Titanium backup.
If you have any more questions....feel free to ask them here or PM me.
You can start by researching "how to do a Nandroid" and "what is clockwork recovery mod" in your favorite search engine.
If you think you can follow the simple steps of performing a Nandroid and you can find your way around Clockwork Recovery Mod....there really isn't much to worry about.
Bricking your device can usually be fixed in the case of a soft brick or boot loop. The real bricking usually happens when you flash software meant for another device, or don't follow instructions.
Once you've flashed your first ROM...you'll find that the process is remarkably similar for all mods ROMs and other packages.
Appreciate the replies. The largest problem I have is the computer itself. I have whole rooms of computers sitting across the street at KSU. Not a problem to use and my pick of OS. The problem lies in they are public and get wiped on shutdown. So no backup. Thoughts?
I've done updates across various Mobiles for years like that.
bmstrong said:
Appreciate the replies. The largest problem I have is the computer itself. I have whole rooms of computers sitting across the street at KSU. Not a problem to use and my pick of OS. The problem lies in they are public and get wiped on shutdown. So no backup. Thoughts?
I've done updates across various Mobiles for years like that.
Click to expand...
Click to collapse
Honestly - Once you get CWM setup on the phone there's very little if any need for a computer. I'm not sure what you mean by "backup" but since you're talking about public computers - let's just run through this scenario:
Go across the street and install CWM. Now, let's say a few days later a new ROM comes out. Woohoo! Assuming you've already flashed CWM, all you need to do is shutdown your phone, backup it up in recovery. This saves to your external SD. Reboot. Download new ROM save to internal SD. Shutdown, pull external SD, boot to recovery, flash away.
If you're worried about it - buy a USB external drive and use the university computer to copy the contents of your external SD across to the hard drive every one in a while.
netsyd said:
Honestly - Once you get CWM setup on the phone there's very little if any need for a computer. I'm not sure what you mean by "backup" but since you're talking about public computers - let's just run through this scenario:
Go across the street and install CWM. Now, let's say a few days later a new ROM comes out. Woohoo! Assuming you've already flashed CWM, all you need to do is shutdown your phone, backup it up in recovery. This saves to your external SD. Reboot. Download new ROM save to internal SD. Shutdown, pull external SD, boot to recovery, flash away.
If you're worried about it - buy a USB external drive and use the university computer to copy the contents of your external SD across to the hard drive every one in a while.
Click to expand...
Click to collapse
Now that sounds like a plan. Hmmm. Maybe I can do this myself. Now I need to find a stock stable ICS with NFC enabled. Even better would be one to take advantage of the radio hidden by AT&T. It would be nice to have the option to pop and flop.
Exactly. Once the initial root and new recovery menu is done then you are set. Between a CWM nandroid, Titanium Backup, MybackupPro, and even Appsaver your only real limitation is set by how large your external sdcard is.
You can even use online storage sites like Minus, Google Drive, Drop Box etc to host all of the files so that you can access them anywhere.
Hmmm. What's the closest stock ICS out there right now, if I may?
I am running Flapjaxx Unofficial ICS and it is super smooth. I plan on switching to his latest though once it is finished downloading.
netsyd said:
Honestly - Once you get CWM setup on the phone there's very little if any need for a computer. I'm not sure what you mean by "backup" but since you're talking about public computers - let's just run through this scenario:
Go across the street and install CWM. Now, let's say a few days later a new ROM comes out. Woohoo! Assuming you've already flashed CWM, all you need to do is shutdown your phone, backup it up in recovery. This saves to your external SD. Reboot. Download new ROM save to internal SD. Shutdown, pull external SD, boot to recovery, flash away.
If you're worried about it - buy a USB external drive and use the university computer to copy the contents of your external SD across to the hard drive every one in a while.
Click to expand...
Click to collapse
+1 on any Flappjaxxx ROM btw. So you pull your external sd? Have you ever had an issue or is it just a precaution?
Sent from Galaxy Note
bmstrong said:
Appreciate the replies. The largest problem I have is the computer itself. I have whole rooms of computers sitting across the street at KSU. Not a problem to use and my pick of OS. The problem lies in they are public and get wiped on shutdown. So no backup. Thoughts?
I've done updates across various Mobiles for years like that.
Click to expand...
Click to collapse
I wonder if it would help you to back up on google drive? Ive never tried it or anything but it could possibly give you some cloud space. Maybe a good option?
Yayodroid said:
I wonder if it would help you to back up on google drive? Ive never tried it or anything but it could possibly give you some cloud space. Maybe a good option?
Click to expand...
Click to collapse
Yeah. I use both Drive and Dropbox, so no worries. The larger question I have is why do I need to back some of this stuff up? I've never been a big application guy. This Note has 4? Maybe 5 apps on it, aside from the stock Google services. SMS/MMS get deleted instantly or saved into the Cloud. And email moved with my Gmail account and that gets barfed back into each Mobile I use very easily.
Titanium backup seems like a pain in the ass. All I'm after is a clean stock ICS build, a way to shut off the hard keys and replace them with soft buttons, and that MHL works. Turning this Note into a portable LTE MHL Chromebox with a fantastic screen. The option to flop and plop would be nice...
you dont have to back up, but personally i would like to have my own personal backup of stock. of course there are stock odins around here. but in your situation it might be more handy on the cloud to access anytime. you might want to use the back up to flash back to for when they release ics over the air.
Service makes some sense
If you've read many of the questions that some poeple ask on these forums, it really makes me think that certain people really shouldn't be trying some of these things themselves. Most of us have no problem reading and understanding rudimentary steps to get us going, but some people come in with little to no foundation in these matters; what we're saying really is Greek to them. I feel bad, but for these people, I encourage them to seek out someone that knows, at least on a basic level, what they are doing.
I've written looooong, detailed tutorials for people and I'm glad to do it. But sometimes even after that, I get the feeling that these people will still end up messing their phones up. I've been proven right on at least two occasion and I can't help but feel bad... So maybe a pool of people in each area capable and willing to do these kinds of things might make sense. Haven't thought through how that would work, but maybe. Hmmm...
bmstrong said:
Hmmm. What's the closest stock ICS out there right now, if I may?
Click to expand...
Click to collapse
Im using team perfections ics ucle2 objection with rc1 its great as well as fj's
sent from team perfections ics rom
Extremely interesting process and results. I still have a host of questions, why certain things are done in a certain order, what exactly some of the things do that I did, and why when I did not make a back up of anything, it said specifically that it failed, some of my apps and vids are still here in the new FJ ROM. Just a fasincinating first time experience from someone who has always used stock Nexi. The ROM isn't really my taste, I hate Apex and there is bloat apps in it. But!
I feel like the old Quantum Leap show...
You can debloat with tibu. Also, you can use any launcher you want.
Sent from Galaxy Note
All, I've gone through many of the forums here and all I am now is confused. Issue: Had CWM and NVFLASH on and Honeycomb on gtab. Some issues, wanted to go back to stock. Followed instructions; however, now it's in a loop. I cannot get to it via PC. Holding power and volume key, see the 3 birds and "recovery key detected, goes to gtablet screen, goes to screen with a box (arrow in it pointing down) and status bar across bottom, goes to w/tap n tap screen, goes to screen with tnt; then reboots through the process again and again. I've spent the past two weeks going through the internet and reading the various methods to unbrick, none work; because I can't get to the internal SD card.
Is there a way to fix this? Is there a way to use the external micro-SD card? Or do I just need to throw this thing away? Any assistance would be appreciated. Oh, I've tried the Code Red and every other unbricking method I came across.
Thank you in advance, Michael
[email protected]
Since you are only experiencing a cycled boot loop then you are not bricked. There is still hope.
What NVflash file did you use to get back to stock?
Which bootloader do you want to run?
http://viewsonic-gtablet-for-dummie...268582d53a1&fw_sig_social=1&fb_sig_network=fw
This website helped me out allot when I was in a jam.
nobe1976 said:
Since you are only experiencing a cycled boot loop then you are not bricked. There is still hope.
What NVflash file did you use to get back to stock?
Which bootloader do you want to run?
http://viewsonic-gtablet-for-dummie...268582d53a1&fw_sig_social=1&fb_sig_network=fw
This website helped me out allot when I was in a jam.
Click to expand...
Click to collapse
I grabbed the latest one. Basically, I'm almost at the "throw it in the trash" stage. If there is a way to boot from the external SD card to load the stock 1.1 version; that's what I would like to do and give this to my niece. Thank you for replying.
Michael
There is a way to "install clockwork from external SD" - search that phrase and you should find it.
BTW- If you plan on trashing it, I'll pay for shipping to my house. I'll 'throw it away' for you
new_to-droid said:
I grabbed the latest one. Basically, I'm almost at the "throw it in the trash" stage. If there is a way to boot from the external SD card to load the stock 1.1 version; that's what I would like to do and give this to my niece. Thank you for replying.
Michael
Click to expand...
Click to collapse
Well all and all I know your fustration. The first link I beleive you are using is the Stock 1.1 from the 3588 branch. That one I used before and had nothing but issues. The best one to use is from the 4349 branch perfered with CWM pre-installed. After flashing that file shut the Tablet off during boot up. Then boot into recovery mode by holding down the volume + while pressing the power button. Do a Wipe Data Factory reset, Clear Cache, and then under advance Wipe Dalvic Cache then go back to main menu of CWM and reboot device. Make sure you don't select reboot recovery since that will not let you boot into anything but CWM. TNT TabUI will then boot up and you chould be good to go.
Thanks...but
Thanks to everyone. I still can't get this darn thing to connect to the PC or CWM to run. I would love to be able to just put it back to stock and be done with it. The more I work with Android devices, the more I'm convinced that I will stick with Windows or Apple. Android is great, but until there is a one size fits all solution; the tweaking and manipulation one has to do just to increase the functionality is what will be Android's downfall. Nothing is "simple" with Android and unless you're a programmer; there isn't much one can do with it. Partially it is the manufacturer's fault (i.e. Viewsonic) for putting out crap that doesn't even work; part of it is Google for not requiring standards for Android (yeah, no standards are great because one can explore/tweak/etc); and it is my fault (for this instance) for thinking that I could tweak and enhance my system. So, I'll put this thing up on Craigslist and see if I can make some change with it and get a newer device or just stick with a laptop and be done with it. Thanks again everyone for all your help.
$$Price?
Sent from my Droid using XDA
new_to-droid said:
Thanks to everyone. I still can't get this darn thing to connect to the PC or CWM to run. I would love to be able to just put it back to stock and be done with it. The more I work with Android devices, the more I'm convinced that I will stick with Windows or Apple. Android is great, but until there is a one size fits all solution; the tweaking and manipulation one has to do just to increase the functionality is what will be Android's downfall. Nothing is "simple" with Android and unless you're a programmer; there isn't much one can do with it. Partially it is the manufacturer's fault (i.e. Viewsonic) for putting out crap that doesn't even work; part of it is Google for not requiring standards for Android (yeah, no standards are great because one can explore/tweak/etc); and it is my fault (for this instance) for thinking that I could tweak and enhance my system. So, I'll put this thing up on Craigslist and see if I can make some change with it and get a newer device or just stick with a laptop and be done with it. Thanks again everyone for all your help.
Click to expand...
Click to collapse
Sorry to see that your experience with your newly found failure did not come with a price of knowledge. Truth be sayed I am no programmer, geek or knowledge of script writing either, but what I can pass along to all new-to-android persons is that your best path is to read and follow instructions to the T or you will end up with a expensive paper wait. The web link I posted above is pretty self explained and I give that man credit because I was a newbie too once. Then somewhere in these forums I found that website and was able to recover from just about anything that happened to my poor Gtab. Hell, I even had to drill a hole in the back of the case just because I wanted more and there was ICS from Team DRH. But truth be said that web link is your path and only path to going back to the stock UI and recovery.
Price
50 plus shipping to us only
new_to-droid said:
50 plus shipping to us only
Click to expand...
Click to collapse
I'll buy it. DIBS EVERYONE!
PM me with your info and I'll have the money sent right away.
Even if I couldn't get it to work, I could use it for parts for my current g-tab.
EDIT: Don't mind my post count. I'm very active on SD, just not here.
Just wanted to mention that I have not been PM'd or replied to. Hope this guy got his tab to work.
Hi Guys,
Once again, my apologies if these queries have been already answered in another thread that I have missed but here goes.....another essay <g>
1. I recently successfully rooted my TF201 with instructional help read from this forum (and even donated a few bucks to Sparky for his great work).However, when I (often) reboot my Prime, it still only says "Your device is unlocked" in the top left-hand corner, and nothing else - is that normal? After that, it boots normally. When I press the power switch at the top of the device to turn it off, the only option I'm given is 'Close down device', but nothing else, like restart device. Is this right or is there a way to change that, to add more options?
2. For safety reasons, I understand it is advisable to make nvflash backups to prevent my Prime ever bricking. Can one of the decent people here please point me in the direction of the best thread for the easiest way to do this, so I don't make a balls-up?
3. Are there any benefits and/or pitfalls of upgrading from my ICS 4.03 to Jellybean or better to leave it on ICS? (I'm getting sick and tired of the oh-so-frequent full-screen reminders to upgrade that I always hit the POSTPONE button).
Is there ANY way to DISable that dang notification?!?!?!?
4. Lately, the stock launcher has been frequently stopped responding and usually has needed a reboot to get anything working. Is this normal and is there a good way to fix it. I'm assuming it's a memory-management issue. In your valued and learned opinion, which are the best memory optimizers and task-killers available?? And likewise, are there any apps. including launchers that should be avoided like the plague (I have about 5 different launchers installed (Next, GO, SPB etc)?
5. How would you rate CyanogenMOD 10.1? Is it worth the flash?
6. Also lately, whilst trying many many games, the screen has started flickering and the game has stopped responding. Is there a fix for this or is it a common fault that many of you have experienced? I don't know what's causing it, but a solution would be greatly appreciated.
7. Is there ANY way to speed up my TF201 and get launcher to stop responding so often??
8. My TF201 takes almost 3 minutes from pressing the power button to reaching the lock screen - is this normal and is there any way to speed it up?
9. Last one for now, is the TF201 capable of using a 128GB SD card in either one or both of the SD card slots, and if so, can someone honestly recommend the best brand and type of SD card to buy? Sandisk or Kingston perhaps?
Ok, hope someone has time, patience and can make the effort to be able to answer my questions (without trolling).
Thanks in advance, always.
My Specs:-
Android Version - 4.0.3
Kernel Version - 2.6.39.4
Build Number - IML74K.WW_epad-9.4.2.28-20120525
Pad EC Version - TF201-PAD-0215
"This is ground control to Major Tom....can you hear me Major Tom?"
"Just nod if you can hear me........is there anyone at home???"
Surely my questions aren't 'that' difficult? - any answers to them, please (with sugar on top)?
Al.Gray said:
"Just nod if you can hear me........is there anyone at home???"
Surely my questions aren't 'that' difficult? - any answers to them, please (with sugar on top)?
Click to expand...
Click to collapse
Relax
I'll need some information first
Just the basic facts
Can you show me where it hurts? :victory:
So, now then, any answers, 'wise one'? Seems you're the one with all the facts.....or was it just that I was woefully mistaken about you?
Al.Gray said:
Hi Guys,
Once again, my apologies if these queries have been already answered in another thread that I have missed but here goes.....another essay <g>
1. I recently successfully rooted my TF201 with instructional help read from this forum (and even donated a few bucks to Sparky for his great work).However, when I (often) reboot my Prime, it still only says "Your device is unlocked" in the top left-hand corner, and nothing else - is that normal? After that, it boots normally. When I press the power switch at the top of the device to turn it off, the only option I'm given is 'Close down device', but nothing else, like restart device. Is this right or is there a way to change that, to add more options?
2. For safety reasons, I understand it is advisable to make nvflash backups to prevent my Prime ever bricking. Can one of the decent people here please point me in the direction of the best thread for the easiest way to do this, so I don't make a balls-up?
3. Are there any benefits and/or pitfalls of upgrading from my ICS 4.03 to Jellybean or better to leave it on ICS? (I'm getting sick and tired of the oh-so-frequent full-screen reminders to upgrade that I always hit the POSTPONE button).
Is there ANY way to DISable that dang notification?!?!?!?
4. Lately, the stock launcher has been frequently stopped responding and usually has needed a reboot to get anything working. Is this normal and is there a good way to fix it. I'm assuming it's a memory-management issue. In your valued and learned opinion, which are the best memory optimizers and task-killers available?? And likewise, are there any apps. including launchers that should be avoided like the plague (I have about 5 different launchers installed (Next, GO, SPB etc)?
5. How would you rate CyanogenMOD 10.1? Is it worth the flash?
6. Also lately, whilst trying many many games, the screen has started flickering and the game has stopped responding. Is there a fix for this or is it a common fault that many of you have experienced? I don't know what's causing it, but a solution would be greatly appreciated.
7. Is there ANY way to speed up my TF201 and get launcher to stop responding so often??
8. My TF201 takes almost 3 minutes from pressing the power button to reaching the lock screen - is this normal and is there any way to speed it up?
9. Last one for now, is the TF201 capable of using a 128GB SD card in either one or both of the SD card slots, and if so, can someone honestly recommend the best brand and type of SD card to buy? Sandisk or Kingston perhaps?
Ok, hope someone has time, patience and can make the effort to be able to answer my questions (without trolling).
Thanks in advance, always.
Click to expand...
Click to collapse
1. That is normal. If you want more options in the shut down menu install a custom rom.
2. http://androidroot.mobi/pages/tegra3-guide-nvflash/
3. I've told you more than once now to upgrade from ICS yet you are adamant you want to stay there. Not my job to convince you.
4. Don't use memory killers, don't have 5 launchers installed.
5. Try it and see, everyone has different needs.
6. Not read anything about it. Might be an ICS issue.
7. Upgrade from ICS.
8. Mine takes about 20 seconds.
9. I don't use sdcards in the dock just the micro sd on the tablet itself and I use 64gig Sandisk UHS-1 class 10.
Trolllolololol.
flumpster said:
1. That is normal. If you want more options in the shut down menu install a custom rom.
2. http://androidroot.mobi/pages/tegra3-guide-nvflash/
3. I've told you more than once now to upgrade from ICS yet you are adamant you want to stay there. Not my job to convince you.
4. Don't use memory killers, don't have 5 launchers installed.
5. Try it and see, everyone has different needs.
6. Not read anything about it. Might be an ICS issue.
7. Upgrade from ICS.
8. Mine takes about 20 seconds.
9. I don't use sdcards in the dock just the micro sd on the tablet itself and I use 64gig Sandisk UHS-1 class 10.
Trolllolololol.
Click to expand...
Click to collapse
(1.) Thanks for taking the time out to reply, flumpster, my Prime seems to have settled down a bit now and things are running smoother, although still not perfect (too much installed and running in the background probably (and hence the long boot-time)). I now use an app named 'Quick Boot' to give me more shutdown options without the need yet to install a custom ROM.
(2.) Thanks for the link that I already had, but certain stages of that process seem more inclined to working with Linux to make nvflash backups, no? I wish there was an app that would make this a process not requiring 'nerves of steel' or more Windows 7-friendly (is there?)
(3.) Don't get me wrong buddy, I would upgrade to Jellybean yesterday if and when I'd made nvflash backups first, as that is the only reason delaying my upgrade (the NEED for an unbrickable device!!)
(4.) I've cut down on memory-optimizers and now only have 4 launchers installed - Good, eh? =o)
(5.) All things will be achieved in good time.
(6.) Could be, but it usually settles down after a reboot - no worries.
(7.) Things are gradually improving through experimentation and YES, I WILL upgrade from ICS if and when I get this nvflash backup issue resolved.
(8.) Patience is a virtue.
(9.) Still only using my old 32GB Micro-SD card in the tablet (soon to be upgraded to 64GB SanDisk Ultra Android MicroSDXC Class 10), but now also using a 128GB Class 10 SDXC-card in the dock too. Directory-Bind is working fine with both cards, so no complaints there.
Never take a troll seriously (or personally, for that matter).
Respect!
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.