Related
i originally had faria's wm6 on my phone, but then i wanted to try xplore core 2.0. i flashed it, but when it finished it would start. it wouldnt go past the second splash screen. i tried a hard reset using the hard keys, but when i try it, it says format failed. i have tried to reflash using bootloader using the OEM carrier roms from both t-mobile and cingular. i am having the same issue no matter what i do. if there is anything i can do to fix this.. please help me because i constantly use my wizard and i don't no what i can do without it. i really appreciate any input. thanks
im not sure what to do but i figured i'd respond just so you know people are trying to help. I've heard of the format failed problem, but im not sure what the solution was. Good luck!
What device do you have ? A G3 ?
How I fixed my Format failed problem...
This is a quote from thread
http://forum.xda-developers.com/showthread.php?t=276963&highlight=splash+screen+freezing
I followed these steps with an SD card fresh from the package...
Drug_Store said:
...
2- Get a clean SD card (in qtek 9100 / Htc Wizard case is MiniSD) with 128MB (some people say 64MB, but I personally used a 128MB, maybe a 64MB is enough)
3- Kill (task manager) wescomm.exe (this is related with activesync installed on your PC). Insert the blank SD card on the phone.
4- Get your phone in bootloader mode. Like this : Phone powered off, press Camera button + Power On, will enter in bootloader mode (RGB screen).
5- Now connect your USB cable to your phone. And start MTTY_updateROM.exe (http://wiki.xda-developers.com/uploads/romupdate.rar). After open, on Port selection, choose \\.\WCEUSBSH001 and press OK. A window will open with a blank sheet.
6- Type "r2sd all" and hit enter... wait to the end (at end shows "cmd>"). On your phone screen u can follow backup progress... small bar will appear down the RGB screen.
7- Power off the phone (or remove battery), enter bootloader mode (camera button + power on) and this time RGB won´t appear right away. Will ask if u want to "download SD image", press voice dial button to agree, and writting will begin. Wait to the end. Power off and power on normally. Now your phone should be working ok. Not even needed to reflash the phone after this.
Thanks to all and hope this helps more people with this problem
Click to expand...
Click to collapse
thanks guys... im going to try that.. and just so all of you know, its a g3
thanks everyone who helped me out. my wizard is working perfectly again. i appreciate all the help
wow that's awsome
idd, mtty is last chance weapon.
woah...
Guess I'll post this...
For the record, the Core 2.0 rom ****ED my phone up too. When I tired to flash back a different rom because of all the changed **** in Core 2.0 my phone flipped out. I had to flash it 3 or 4 times to get it to even boot.
I recommend anyone thinking of tyring Core 2.0 to stay away from it unless they don't plan on changing roms after going to it.
GldRush98 said:
woah...
Guess I'll post this...
For the record, the Core 2.0 rom ****ED my phone up too. When I tired to flash back a different rom because of all the changed **** in Core 2.0 my phone flipped out. I had to flash it 3 or 4 times to get it to even boot.
I recommend anyone thinking of tyring Core 2.0 to stay away from it unless they don't plan on changing roms after going to it.
Click to expand...
Click to collapse
yes, i edited it.
I believe operator error isnt something to blame on the rom. Anyone that openly drops the "F" bomb when discussing a cell phone really should get a life.
GldRush98 said:
woah...
Guess I'll post this...
For the record, the Core 2.0 rom ****ED my phone up too. When I tired to flash back a different rom because of all the changed **** in Core 2.0 my phone flipped out. I had to flash it 3 or 4 times to get it to even boot.
I recommend anyone thinking of tyring Core 2.0 to stay away from it unless they don't plan on changing roms after going to it.
Click to expand...
Click to collapse
anichillus said:
You are an asshole, pardon my language. My rom doesn't **** systems up, mabe you just don't know what you are doing.
I won't release any more roms. I am just tired of all this SH**. I stay calm and watch people who only know how to complain and don't give a F*** about all the work that's put up just for free, but this does it. I am giving up.
I can't afford to brick my Wizard for people like you who are simply here as ignorant sharks.
Click to expand...
Click to collapse
You sound like Faria...LOL!
Really, that's why I put what I did in my thread about saying "My phone is stuck in bootloader..." (remember the fillet knife?) ROM's DO NOT MESS UP A PHONE UNLESS THEY ARE CID LOCKED, THE FLASHING PC HAS ISSUES, OR BECAUSE OF OTHER OPERATOR ERRORS.
Don't let it get you down. You're doing a good work and if one or two people out of a thousand can't get it right, then they need to be running carrier ROMs, and you can stay calm and happy helping those who really need it.
See, that's not so bad now is it?
GldRush98 said:
woah...
Guess I'll post this...
For the record, the Core 2.0 rom ****ED my phone up too. When I tired to flash back a different rom because of all the changed **** in Core 2.0 my phone flipped out. I had to flash it 3 or 4 times to get it to even boot.
I recommend anyone thinking of tyring Core 2.0 to stay away from it unless they don't plan on changing roms after going to it.
Click to expand...
Click to collapse
i went form core 2.0 back to the tmobile rom and then to the core 2.0n and it worked fine. did you lose connection during the flash or somthing?
anichillus said:
You are an asshole, pardon my language. My rom doesn't **** systems up, mabe you just don't know what you are doing.
I won't release any more roms. I am just tired of all this SH**. I stay calm and watch people who only know how to complain and don't give a F*** about all the work that's put up just for free, but this does it. I am giving up.
I can't afford to brick my Wizard for people like you who are simply here as ignorant sharks.
Click to expand...
Click to collapse
Boy, I know more about what I'm doing then most people here put together.
Your rom ****ed my phone right in the ass.
Luckily I recovered from it.
You call your Rom "stock" yet YOU CHANGED ALL KINDS OF STUPID STUFF IN IT.
Like the alignment screen graphic?
Why the hell would you do that.
Or putting on 3 different boot screens. wtf?
Oh yeah, not to mention it runs like **** before even loading any more software on it since you used the OLD WM6 build.
Don't release any more.
You're terrible at it.
kthx bye.
jawnsixteen said:
i went form core 2.0 back to the tmobile rom and then to the core 2.0n and it worked fine. did you lose connection during the flash or somthing?
Click to expand...
Click to collapse
Nope, flash went to 100% then the phone tried to reboot and nothing happened.
I do all my flashing on that machine because it's stable and I have never had a problem flashing until the Core 2.0 rom. That is the first and only rom I have had any trouble with.
golfernutnflorida said:
I believe operator error isnt something to blame on the rom. Anyone that openly drops the "F" bomb when discussing a cell phone really should get a life.
Click to expand...
Click to collapse
OMG, he used a naughty word.
Like you don't hear it daily?
Get real.
GldRush98 said:
Boy, I know more about what I'm doing then most people here put together.
Your rom ****ed my phone right in the ass.
Luckily I recovered from it.
You call your Rom "stock" yet YOU CHANGED ALL KINDS OF STUPID STUFF IN IT.
Like the alignment screen graphic?
Why the hell would you do that.
Or putting on 3 different boot screens. wtf?
Oh yeah, not to mention it runs like **** before even loading any more software on it since you used the OLD WM6 build.
Don't release any more.
You're terrible at it.
kthx bye.
Click to expand...
Click to collapse
I do my rom as I please, you can't question that.
For YOU to know all roms have 3 (boot =NOT) splash screens You're just too SMARTass to notice.
You can quote multiple post in same message, in case that slipped your soo full-of-knowledge mind.
I used old WM6 build ? Please explain to me what you mean ...i am not that wize
I did not called my rom STOCK ! I called it Core . But you are probably too smart to actually even read anything.
In case you don't understand the word "CUSTOM", then let me explain it to you : I can change whatever i want in it. All of it if I like to.
Ah yeah, and i almoust forgot ... please read this
http://forum.xda-developers.com/showpost.php?p=1241040&postcount=1
It's been there from day 1, just made it bigger now, so that you can see too
And next time, keep your opinions to yourself. No need for public -> "Ooh, look at me how tough I am ! " stunts.
....
whether you like it or not...
I'm confused by people who choose to post cooked ROMs in a public forum, invite people to use and comment, but them complain if the feedback it not all roses and accolades.
You may have done this for free, and many if not most, appreciate your time and effort. That being said, some have legitimate complaints and are posting them because they have experienced problems with your ROM. I’ve been reading your reaction to any negative feedback and you are highly defensive, never conceding that there may be issues to address.
All cooks say that you are not responsible if the ROM bricks someone’s device or if they have problems, and no one has asked for you to pay for their repairs or replace their devices.
There is no place for foul language or insults in such a forum. It's childish and may simply help support the complainant’s point.
If this is your reaction to complaints, then yes do us all a favor and stop posting and keep your work for your personal enjoyment and benefit.
If you can't stand the heat, then get out of the kitchen. No pun intended.
Well if it doesn't work for you then try a different ROM. I tried all the ROMs and pretty much gonna stay with Faria The Real Thing
I tried Xplore 1.0 and i had alot of troube so I dont think im gonna try 2.0. If it works dont change
Funny thing is I have flashed this ROM to my wizard 6 times, and each time something else didn't work. But let me explain...
I want a stripped version of windows, I don't do any messaging at all. And since the Explorer ROMS are known for their stability, it seemed a logical choice. So I have been using package tools, to create packages with option.XML files for each package so you can choose, what parts of the OS get installed.
But back to the point...
Each time I flashed something went wrong... Something I did, a "tmail not found warning when activesync starts", to once I got a 260(?) error once when flashing at 63% so I started it while holding the voice command button. It booted into Bootloader, I flashed it to Cingular 2.25.11 and immediately flashed back to the same ROM successfully.
There are hundreds of people Ecstatic with the Xplorer ROMs, for each one of you here complaining. I for one would think it a travesty, for a few unappreciative people to ruin it for hundreds of others. By pissing off one of our cookers. Maybe had you posted your problems here we would have been able to help you.
But please don't be so accusing, just read, and if you can't find an answer. Then ask nicely, and thank the cook for the time he spends cooking for us! If you don't like the answer you get or you decide you don't like this ROM try one of the many others...
I know there are a lot of newbies out there trying to cook with the ROM kitchens and running into problems--wanted to provide a little advice to save you from yourselves. But first, my story:
This weekend I was playing around with Faria's ROM Kitchen. Wasn't really paying attention to what I was doing, and forgot to load the Start Addresses and Image Names in nb2nbf before flashing. Guess what? Got myself a brick. Wouldn't go past the initial boot screen, and I couldn't reset it to save my life. Mustering my calm I set out to fix it...popped out the battery to reset the device...entered bootloader mode (hold camera button after soft reset)...follow Dr Puttingham's outstanding tutorial to reCIDunlock...flashed a few ROMs to get back to IPL/SPL 2.x and I was back in business.
Point of all this is not to blame others, learn about what you're doing and fix your own mistakes. Pointing fingers and someone's ROM won't get you there. Paying attention to what you're doing would also help (still gotta learn that one myself obviously!) Most importantly, before digging into these advanced topics, learn how to save yourself if something goes wrong. Know enought about your device (G3/G4, etc) to know if you should even be doing what you're about to do!
</rant></down from soapbox>
And yes I know this is a non-technical post in a technical forum, but maybe it will help cut down on the chatter and keep the other threads on topic!
nice. beautifully written my friend.
Your device was never bricked.
People do need to know how to recover from a failed flash and not create a new thread for something that was already said!
great
maybe one thing that is not said here is luck... in your case you know what to do and have found solutions
Agreed, not really ever a brick. I've had my computer simply turn off in the middle of flashing before. Just reset to the "flag" screen and reflash. A brick is where you flash the _WRONG_ ROM and it won't even go to the tri-color screen.
im in a panic
need a solution:
I have successfully flashed many roms before. Today i was flashing BlackDiamond 1.1 ROM and i was at 92%, My PC restarted (this is my prob). I have done nothing yet on Phone and its still showing 92%(with blue bar). I tried to run update again biut its giving connection error 264. Does this means im bricked (plz. dont say yes). Im in a desperate need of quick help.
Out Of panic. Done flashing using bootloader help http://forum.xda-developers.com/showthread.php?t=294107 . Running fine
Pastamancer said:
Agreed, not really ever a brick. I've had my computer simply turn off in the middle of flashing before. Just reset to the "flag" screen and reflash. A brick is where you flash the _WRONG_ ROM and it won't even go to the tri-color screen.
Click to expand...
Click to collapse
Does a brick give light? NO. Then that phone was never a brick
Sometimes good intentions can mislead others and set hopes high... (maybe changing topic's title)
Wow, didn't think I was digging in to the metaphysical meaning of the term's exact definition...Don't think it changes the original intent that people should spend a little more time reading about what they are doing before doing it!
Fab stuff. I did exactly the same. It's most times we fail to read and are so eager to get going, we miss minute details which make a big difference.
I made a mistake using Dr. Puttingham's guide while only pressing S button and restarting and not doing the C (CID unlock) button and had myself a brick.
Hey all,
I'm getting my G Tablet tomorrow and I'd just like to get some things clarified.
I know, the first thing some will say is USE SEARCH! Well, I did - and that's actually why I just want to get some things straight before I go down the path of modifying the device software. See, reading it all has managed to confuse me more than help me get a definitive instruction set for forging ahead.
I'm seeing the update "****s on CWM" according to a user...and then a 'fix' for that. Than I see that Gapps causes FCs for some, while it works for others. So...yeah, a little back and forth on what to do and who's instructions to follow.
Alright, so first thing's first....Should I flash the Clockwork Mod that I'm seeing available - 0.8? or is there something else I should consider or that I've missed? or maybe wait for a newer version? Should I even flash CWM if I get the newest (and I WILL be getting the newest) S/W version? Are there any downsides at all to flashing CWM on there in terms of messing with OTA updates, etc?
I read this:
"All the ROMS use a standard firmware updater that can be used by non-technical users. Here is an explanation on how it works:...."
Sooo, does that mean I can live without CWM? If an update doesn't work for some reason, will I be able to fix it or overwrite it somehow if I can't get into the tablet at all from the tablet itself? I read something about going into APX mode and putting things on through Windows, is this an infallible method?
Second of all, I read the FAQ thoroughly (I think and hope) but I'm still not 100% on what Gapps to DL or how to put a working Android Market on there especially with this new S/W update. I've seen how to 'fix' the Market to see missing apps, but not how to actually install it on the G Tablet. I may have missed that post somewhere on here.
I'm also unclear if I should get Gapps or not at all, as I've read that some have FCs on there while others do not - so what's the general consensus in light of this update that was just released as of Dec. 21, 2010?
Ultimately, here is what I'd like from my GTab:
I'd like to run the new official Tapn'Tap released recently first and foremost.
I'd like to have the official/unofficial (w/e) Google Market.
I'd like to run Google Apps (Gtalk, Gmail, etc.).
IF I don't like Tapn'Tap, and this is a worse case scenario situation, as in if I HATE TnT - I'd like to have the option to slap something else on there and I'd like to make sure I don't brick my Tablet. Whether that means storing an original official TnT ROM or whatever.
Point me in the right direction please, especially considering things may have changed as of the new S/W update.
Thanks much and sorry for all the questions. I assure you I used search and I attempted to put it together on my own. It's been a long time since I've modded (G1 was the last time) and I don't do it often. Also, apologies if I posted this in the wrong section....I considered posting it in Dev. section but this one seemed better suited.
Thanks again, XDA rocks.
Neoprimal said:
Hey all,
I'm getting my G Tablet tomorrow and I'd just like to get some things clarified.
I know, the first thing some will say is USE SEARCH! Well, I did - and that's actually why I just want to get some things straight before I go down the path of modifying the device software. See, reading it all has managed to confuse me more than help me get a definitive instruction set for forging ahead.
I'm seeing the update "****s on CWM" according to a user...and then a 'fix' for that. Than I see that Gapps causes FCs for some, while it works for others. So...yeah, a little back and forth on what to do and who's instructions to follow.
Alright, so first thing's first....Should I flash the Clockwork Mod that I'm seeing available - 0.8? or is there something else I should consider or that I've missed? or maybe wait for a newer version? Should I even flash CWM if I get the newest (and I WILL be getting the newest) S/W version? Are there any downsides at all to flashing CWM on there in terms of messing with OTA updates, etc?
I read this:
"All the ROMS use a standard firmware updater that can be used by non-technical users. Here is an explanation on how it works:...."
Sooo, does that mean I can live without CWM? If an update doesn't work for some reason, will I be able to fix it or overwrite it somehow if I can't get into the tablet at all from the tablet itself? I read something about going into APX mode and putting things on through Windows, is this an infallible method?
Second of all, I read the FAQ thoroughly (I think and hope) but I'm still not 100% on what Gapps to DL or how to put a working Android Market on there especially with this new S/W update. I've seen how to 'fix' the Market to see missing apps, but not how to actually install it on the G Tablet. I may have missed that post somewhere on here.
I'm also unclear if I should get Gapps or not at all, as I've read that some have FCs on there while others do not - so what's the general consensus in light of this update that was just released as of Dec. 21, 2010?
Ultimately, here is what I'd like from my GTab:
I'd like to run the new official Tapn'Tap released recently first and foremost.
I'd like to have the official/unofficial (w/e) Google Market.
I'd like to run Google Apps (Gtalk, Gmail, etc.).
IF I don't like Tapn'Tap, and this is a worse case scenario situation, as in if I HATE TnT - I'd like to have the option to slap something else on there and I'd like to make sure I don't brick my Tablet. Whether that means storing an original official TnT ROM or whatever.
Point me in the right direction please, especially considering things may have changed as of the new S/W update.
Thanks much and sorry for all the questions. I assure you I used search and I attempted to put it together on my own. It's been a long time since I've modded (G1 was the last time) and I don't do it often. Also, apologies if I posted this in the wrong section....I considered posting it in Dev. section but this one seemed better suited.
Thanks again, XDA rocks.
Click to expand...
Click to collapse
I don't know how much direction pointing I can do but here goes..
Clockwork mod in my opinion is a necessity. Version 0.8 is the best one for most people because of how it deals with the memory locations. Yes, you can do things without it. The update process is as simple as putting an update.zip file, and a recovery folder with a command file in it on an sdcard and holding the vol + button while hitting power. It is easy. Clockwork has a lot of little features though that make life easier. You can make a complete system backup with it. You can install updates, and new firmware with it. You can completely lock up your tablet and using clockwork and your backup be back in business in about 3-4 minutes. You can load new roms and if you hate them you can go back to your old working stuff in minutes. Yes, there are ways to make one of these tablets work again when they get stuck. I don't think anyone has actually bricked one. Some may think they have, but I doubt it.
Unless you are dead set on wanting the stock TnT interface the easiest way to get what you want is to load one of the roms. Yes, there are ways to get most of it without loading a new rom. Most everyone that has gone the I have to stay stock but want all the mods has eventually just loaded a rom. TnT3.0 is based on the latest stock stuff. It has the market, flash, etc. already in it. VegaN is what I use mostly but they are both stable and fast.
Before you flash something brand new that just came out I would read about it and see what others have to say about issues. It usually only takes about 30 minutes until you can tell if it is going to be good or not.
All of the roms for this tablet have there own little quirks. The stock has gotten better with each update but it still is not as good as the ones I named.
Finally.. This tablet is very easy to play with. It is pretty much unbrickable. Anything you can possibly break one of us has probably already broken before and fixed. There are some people that seem to have problems doing every little thing. Most don't. So I wouldn't let any of it scare you off because none of it is that hard.
With a little bit of searching almost everything you may want it to do can be done. I really love mine, and when I got it almost 2 months ago I hated it...
"Finally.. This tablet is very easy to play with. It is pretty much unbrickable. Anything you can possibly break one of us has probably already broken before and fixed. There are some people that seem to have problems doing every little thing. Most don't. So I wouldn't let any of it scare you off because none of it is that hard."
"Sigh" of relief. Then I'm not too worried. As I said I've dabbled in modifying my G1 and it is mostly cake. But I've just been seeing conflicting posts on whether cwm works with the newest official tnt release or not so I wasn't sure what to do.
Thanks for your advice. And when I said pointers, I meant like this as well as pointing me to any posts I may have missed on how to do whatever. Though I THINK I found most of them.
Neoprimal said:
"Finally.. This tablet is very easy to play with. It is pretty much unbrickable. Anything you can possibly break one of us has probably already broken before and fixed. There are some people that seem to have problems doing every little thing. Most don't. So I wouldn't let any of it scare you off because none of it is that hard."
"Sigh" of relief. Then I'm not too worried. As I said I've dabbled in modifying my G1 and it is mostly cake. But I've just been seeing conflicting posts on whether cwm works with the newest official tnt release or not so I wasn't sure what to do.
Thanks for your advice. And when I said pointers, I meant like this as well as pointing me to any posts I may have missed on how to do whatever. Though I THINK I found most of them.
Click to expand...
Click to collapse
The new release overwrites clockwork. But it is not hard to put back. Always a good idea to copy the clockwork backups folder to your pc, or somewhere they won't be lost. The custom roms typically leave the recovery image alone and can be installed with or without clockwork by either extracting the zip contents for stock recovery, or installing it as is in clockwork.
Sprdtyf350 said:
Finally.. This tablet is very easy to play with. It is pretty much unbrickable.
Click to expand...
Click to collapse
I can vouch for that. Erased system, boot, data and cache in preparation for a new ROM. Accidentally rebooted and couldn't get into recovery. Booted it into APX mode, flashed stock and was on my way.
I would just run ZRoot, then upload the TnTLite 3.0 recovery and update.zip and then do the recovery mode process. You should have a microsd handy just in case it doesn't work, but so far I haven't needed that.
This tablet is much easier to work with and very forgiving since VS never took the time to lock down the bootloader etc like Motorola did with my Droid X. You really shouldn't fear changing files out etc, provided you're getting a ROM from one of the people providing them here. If you can press and hold two buttons at once, you can make your gTab an awesome little tablet. It benchmarks about 1000 points higher than my Droid X on quadrant. Can't wait to see what these guys can do with Gingerbread.
Sprdtyf350 said:
The new release overwrites clockwork. But it is not hard to put back. Always a good idea to copy the clockwork backups folder to your pc, or somewhere they won't be lost. The custom roms typically leave the recovery image alone and can be installed with or without clockwork by either extracting the zip contents for stock recovery, or installing it as is in clockwork.
Click to expand...
Click to collapse
It is also not hard to alter the update so that it does not overwrite clockwork.
Open update.zip
Find updater-script, Open in notepad++
Remove the line that references recovery.img
Flash update
hogasswild said:
I would just run ZRoot, then upload the TnTLite 3.0 recovery and update.zip and then do the recovery mode process. You should have a microsd handy just in case it doesn't work, but so far I haven't needed that.
This tablet is much easier to work with and very forgiving since VS never took the time to lock down the bootloader etc like Motorola did with my Droid X. You really shouldn't fear changing files out etc, provided you're getting a ROM from one of the people providing them here. If you can press and hold two buttons at once, you can make your gTab an awesome little tablet. It benchmarks about 1000 points higher than my Droid X on quadrant. Can't wait to see what these guys can do with Gingerbread.
Click to expand...
Click to collapse
with the new update however does the z4root still work? i heard it may not anymore. just curious also since im hopefully getting mine on sat for xmas
rothnic said:
It is also not hard to alter the update so that it does not overwrite clockwork.
Open update.zip
Find updater-script, Open in notepad++
Remove the line that references recovery.img
Flash update
Click to expand...
Click to collapse
Thanks for the info Rothnic! I had already flashed it before I figured out it removed Clockwork. Learning new stuff every day is good... Thanks..
dragonfly1113 said:
with the new update however does the z4root still work? i heard it may not anymore. just curious also since im hopefully getting mine on sat for xmas
Click to expand...
Click to collapse
The very first time I rooted, I used ZRoot and installed 2.4.0. I didn't change anything and used the exact same process of simply copying over the 3.0.0 files over to the root directory of the internal memory and did the recovery procedure (vol+ and pwr keys). It worked like a charm.
hogasswild said:
The very first time I rooted, I used ZRoot and installed 2.4.0. I didn't change anything and used the exact same process of simply copying over the 3.0.0 files over to the root directory of the internal memory and did the recovery procedure (vol+ and pwr keys). It worked like a charm.
Click to expand...
Click to collapse
Ok cool, thanks cant wait for my g tablet hopefully sat morning
I think you'll like it a lot. I also own an iPad. While they are similar they are also a little different. Merry Christmas!
hogasswild said:
I think you'll like it a lot. I also own an iPad. While they are similar they are also a little different. Merry Christmas!
Click to expand...
Click to collapse
my mom has an ipad and my dad could only buy it while i was on my honeymoon bc he knew i wouldnt approve of an apple device in the house haha.
rothnic said:
It is also not hard to alter the update so that it does not overwrite clockwork.
Open update.zip
Find updater-script, Open in notepad++
Remove the line that references recovery.img
Flash update
Click to expand...
Click to collapse
My device hasn't come yet (damn you FedEx!) but I'm eagerly awaiting it.
My plan:
Unbox, start it....do a factory reset from the getgo if it has enough juice.
Set it back up. Charge it to full. If whatever comes on it is as unbearable as I've seen in on Youtube - start modifications.
Will CWM install on it AFTER I do the update if it's available to me? I've seen that the update messes with it if it's already there - but noone's mentioned putting it on there after the fact. I may just go that route for simplicity sake.
Thanks for this!, and thank you all for chiming in with your experience. I feel much better about just getting my hands dirty in it all. I had wrote something to someone yesterday about jumping in and just doing it, but when it comes to dealing with it yourself it can be a daunting task - especially when it still has that new smell, lol. Anyway, thanks again. You guys really rock.
Will stop back later on after I've done my thing
I think they are both nice devices. There are trade off for both of them. I think the screen on the iPad is wonderful, where the gTab's is okay. But the gTab has a forward facing camera, you can print from it, and you can modify it fairly easily too.
Sprdtyf350 said:
Finally.. This tablet is very easy to play with. It is pretty much unbrickable.
Click to expand...
Click to collapse
...famous last words...
Seriously though...trust the directions from the great devs like roebeet. Follow their instructions word for word. You can switch ROMs and then flash back if you want. No worries...
Off topic!
Well...disappointment! Fedex had my package out for delivery at 8am and at 8pm, they're not here. This is why I like UPS, they show up at my door on the day of delivery, no exceptions - they have shown up at almost 9pm before. The Archos 101 I got was sent out at 8am as well but got here at 1:30pm - I suppose that was before the holiday rush.
Checking the details of my tracking I'm seeing a "delivery exception" at 7:30pm (I guess it was time to get back to the facility so they can clock out by 8pm?) and upon calling them I get a somewhat stumbling but polite CS who tells me the delivery went out "late" - upon which I asked if 8am was considered late, especially from a distribution facility WITHIN the same zip code as I am, and all he could say was "Very sorry about this".
Aaaanyway....I guess it will be tomorrow before I can report my adventures.
Think I'll be able to get my $3.99 back from Amazon? I have Prime and with that the package would have come tomorrow anyway. Basically my $3.99 is wasted. Imagine if I didn't have Prime though? Whew.
ima_UNC_fan said:
...famous last words...
Click to expand...
Click to collapse
If you can figure out how to brick it you will probably get an award.. It won't be a good award but probably one of those top ten dumb things people do awards. So far unless you plug the motherboard into a wall socket no one has bricked one. May think they have, but like I said before I doubt it..
And your right.. If it can be done, someone eventually will figure out how. And then we will all laugh at them.. At least I will
I finally got the G tablet tonight and...alright, don't flame me for this - but I don't see what all the complaints about the screen being horrendous or the device being molasses slow are about?
I don't know how people are trying to view it...but when looking at it or setting it on a stand to watch media, I'm not seeing any problem with the viewing angles. It's about the same as my laptop so I watch it the same way.
It's not even a 1/4 as slow as the stuff I've seen on Youtube or in some of the review videos I've seen around the net. I haven't gotten a single FC. Granted, I haven't put in a SD Card yet so maybe problems will start then?
I guess I should note, the very first thing I did was did a factory reset. Then I hooked it up to Wifi and got the 3053 update. I'm one of those who will be waiting for the 'official' update on the 24th.
I set up the time and date, restarted and everything works. I haven't installed flash yet (don't need it that much) and stuff that I DO want on there right now works fine (skype, pandora, fring, dropbox, evernote). I'm slowly figuring out a list of what I want/need from my Mytouch 4G to port to the VS GTab. Figure I don't really NEED Gtalk, Gmail on there because I have these on my phone AND PC - do I really want them making noises all around my home on 3 devices? I was concerned about getting the Google Apps on but now I'm finding I really don't need them. So it seems to me this will be a matter of learning to separate what I need on a tablet vs. my phone - I was of the mentality that I should just get whatever's on my phone on the tablet, this is something others apparently do as they seem to want everything that's on their phone, on their tablets as well.
I personally don't see the point in that. Had I had the Google Market, that would have escaped me as I'd have used Appbrain to just get my motherload of apps from the MT4G to the GTab. Not having it has slowed me, and now I get to re-evaluate before I do grab apps for it.
Now I just have to merge/convert my HTPC into a NAS device as well and find an app that will allow me to DLNA stream media from it and I'll be in mobile heaven.
I haven't had my wifi drop at all anywhere in my home and I've marched all over with it (I use full Wifi N, no G compat. so maybe my range is wider?). Tried email, etc. to replicate crashes and force closes but haven't so far. No surfing issues. I DID find that one app got 'stuck' being downloaded and I had to delete the file before the 'downloading' icon would go away, even after restart.
Maybe the trick to getting a workable GTab in the first place is to factory reset it before first use? Iunno. Things may change and issues may pop up the more I use it and as time passes - but so far, so good!
Again, I can't thank XDA enough for the advice and info. I've found and been given.
Sprdtyf350 said:
If you can figure out how to brick it you will probably get an award.. It won't be a good award but probably one of those top ten dumb things people do awards. So far unless you plug the motherboard into a wall socket no one has bricked one. May think they have, but like I said before I doubt it..
And your right.. If it can be done, someone eventually will figure out how. And then we will all laugh at them.. At least I will
Click to expand...
Click to collapse
I figured it out. Accidentally hit one of the devkit nvflash .cabs and boom
Today, I acquired a infuse 4g, off contract. I wanted to mess around with android, as my current phone is an iphone, and maybe switch over.
One of the first things I tried to do was tether my iphone to my infuse using mywi. I soon discovered android doesn't work with ad hoc networks. I googled a couple fixes, and decided to try my hand. I have never touched android before. I found this thing that said I could. So I went for it. After reading a few guides, I decided the first step was to root it using superoneclick. That went fine. Then, I read the instructions and it told me to 'flash the zip file using a recovery rom' which was total gibberish to me. So I did some more googling and found a modified 3e recovery thing for the infuse. I used some file system app to put that where it was supposed to be, but then saw that I needed clockworkmod to be able to flash things. By this point I realized I was far, far over my head, but stupidly pressed on. At about the same time, I also extracted the zip file from exop.pro, and replaced the wpa file that existed already in system/bin with the one from the zip. I also booted into recovery mode, and tried to install clockwork mod, which failed even though as far as I can see. Now, when I turn my phone on, everything is ok except that it can't scan for wifi. I assume this is because I ****ed with the wifi file. I've basically decided to give up at this point, so please, just tell me how to made it work again and I'll promise to not **** with it anymore. Also, I neglected to make a backup. Stupid, but I didn't know how and didn't want to go through another huge thing.
tl;dr
I tried to make it so I could connect to ad hoc networks on my infuse 4g and ended up destroying my wda_supplicant file in system/bin (i think) and
Google the original file you replaced, ' wpa supplicant file download for infuse 4g'. Next time save a copy or backup of whatever your doing.
Thanks, but I really have no idea what is what. Could you link me the right one? I'm sorry that I'm so useless.
Itaer said:
Thanks, but I really have no idea what is what. Could you link me the right one? I'm sorry that I'm so useless.
Click to expand...
Click to collapse
this was your problem the first time... you need to read and study before you just start flashing things to your phone man. haha... us linking you somewhere will not help you figure that part out... and its an important part of tinkering with these phones in the way you are trying to.
rid yourself of the apple mentality where everything is spoon fed.
moving on, however, do what the guy previous to me said... find that file you downloaded. and do some reading, watch some instructional videos, focus on just rooting the phone properly for now. do that, then read, watch, ask questions like you are doing when you need to, then proceed.
read comments and stuff in forums about the ROMs you are flashing, what kind of problems do they have, what recovery is recommended for that particular ROM, stuff like that. just READ everything and anything you can about what you are doing....
the company that made your newly found OS has a nice little search engine called google... and it works pretty well if you know how to use it i'll keep an eye on this thread for you as others are probably doing so we can provide you with whatever answers you might need. good luck!
a good rule of thumb when flashing hax0red software to these phones is when something ****s up, 9/10 times it's just a little tiny thing you missed or did during the install yourself... so back to square one, and pay close attention to detail. these phones can be a little touchy when flashing ROMs if you are not doing it exactly they way it is recommended.
perfect example of this: when i had my samsung moment... when i converted from 2.1 OS to 2.2... for some odd reason i would ALWAYS have to flash a little script zip to wipe the 2.1 data from the device before flashing the 2.2 zipped ROM to the phone... the 2.2 ROM was supposed to do this and take care of it completely for me, but even though it did, the only way it would work properly every time i was going from 2.1 to 2.2 was to flash that zip beforehand...
hope that long rant provided some useful insight
Thanks.
But I have read the instructions on the stuff I'm trying to do, several times, and like I said, I'm more confused that I was at first.
I'm just not willing to break it any further.
So basically what I'm wondering now is, how do I put everything back to how it should be. Is there a way? Like, is there a way to load the original software back? I don't think restoring it to factory settings would fix what I did, but tell me if I'm wrong.
I just want everything back to normal.
Please.
Edit: I know it seems like I'm not doing anything to help myself, but I have a lot on my plate in life right now, and I also have absolutely no idea where to even start. Half of the terms you use mean nothing to me, and I'm just so overwhelmed.
I just want to know if there is some way to put it back to how it came out of the box.
Turns out that once the new wda_supplicant thing is ACTUALLY GRANTED PERMISSION TO EXECUTE, that everything works fine. Thanks guys
see... Knew you would figure it out man
Sent from my EVO3D using XDA App
Hey guys...As a few of you know, my phone met its demise last night for (seemingly) no reason. I had recently backed up my ROM through Rom Manager and tried out a few themes from the market.
Anyways, when I plugged my phone into my computer, I see that it tried to install some drivers and then I see "QHSUSB_DLOAD" as my phone.
Ive noticed that all TRULY bricked phones (not just the sensation) all have this "QHSUSB_DLOAD" in common. No one has yet to figure out what this is or how to fix this.
Tmobile chalked it up to hardware failure and has a new (likely refurbished ) on its way.
I think we need to figure out what the heck this is. A few mentioned a connection between Rom Manager, CWM, and QHSUSB_DLOAD. I, for one, will make dang sure that Rom Manager stays off my phone...Any other ideas?
Until this is worked out, its VERY likely that rooting COULD randomly cause the dreaded true brick, QHSUSB_DLOAD style.
Matt
Just swayed my decision on wether to root or not.
So does it turn on? You are a bit unclear about your situation. Does it charge, when you charge it. And does the PC recognize it when you connect it to the PC?
Actually this is well documented. You are in Qualcomm high speed USB download mode. It is typically caused by a problem with your processor and or it's software. Either it is crapping out or more likely something corrupted the software, either by flashing a custom kernel that isn't 100% stable with the hardware (since kernel source for this phone is incomplete this IS possible) or it's just bad luck. Voltage tweaks can have a long term detrimental effect on hardware.
Hey guys, it is dead as a door knob.
http://forum.xda-developers.com/showthread.php?t=1321110
That ought to sum things up...
Im sure its bricked...I just want to look more into this as I have yet to find a single case where this was solved. It just gets pushed aside since no one knows.
Behold_this said:
Actually this is well documented. You are in Qualcomm high speed USB download mode. It is typically caused by a problem with your processor and or it's software. Either it crapped out or more likely you corrupted the software, either by flashing a custom kernel that isn't 100% stable with the hardware since kernel source for this phone is incomplete this IS possible. Voltage tweaks can have a long term detrimental effect on hardware.
Click to expand...
Click to collapse
I was using cm7, build 9 and fauxs kernel build 8. I dont do UVing or OVing and have kept the CPU speed to 1.18Ghz.
My computer told me that it failed to install whatever it felt it needed.
So this is known? Am I correct in thinking that this is a 100% brick then, or is there anything, save from tearing it open, that can be done to fix it?
Although I have a new one coming, Id like to get to the bottom of this for everyone else.
Matt
Well, yes...and no. For all intensive purposes it is bricked, however, if it's just software HTC (or anyone with a leaked loader) could recover it easily. If it's hardware then nothing can be done. You can find the Qualcomm drivers online but still need the loader (all I've found are motorola sbf's nothing for HTC). Basically you did the only thing you can at this point, but now you have a little more info on it.
Behold_this said:
Well, yes...and no. For all intensive purposes it is bricked, however, if it's just software HTC (or anyone with a leaked loader) could recover it easily. If it's hardware then nothing can be done. You can find the Qualcomm drivers online but still need the loader (all I've found at motorola sbf's nothing for HTC). Basically you did the only thing you can at this point, but now you have a little more info on it.
Click to expand...
Click to collapse
Someone could get an XDA style Nobel prize for coming out with something that could fix this phone when this happens.
Im guessing that is what a JTAG does? Would be great once warranty time is over!
I am suspicious this could be another build quality issue with HTC...Day one with this phone had the same sort of thing happen, but it eventually booted. Perhaps this was just waiting to happen?
Or, I wonder if it is related to CWM and Rom Manager? This seems to be a RARE occurance considering how many people flash the above mentioned ROM and kernel without this happening. The last thing I did before charging was backing up in Rom Manager.
Jtag is a little extreme as it involves soldering and messing with internal components, plus don't think it's been done on this chip set, but I could be wrong. The ROM is usually less of a concern then custom kernels are. Also ROM manager sucks and many times is very buggy. It is safer to do all those kinds of things through recovery. Uninstall ROM manager and forget it ever existed (just my opinion).
Behold_this said:
Jtag is a little extreme as it involves soldering and messing with internal components, plus don't think it's been done on this chip set, but I could be wrong. The ROM is usually less of a concern then custom kernels are. Also ROM manager sucks and many times is very buggy. It is safer to do all those kinds of things through recovery. Uninstall ROM manager and forget it ever existed (just my opinion).
Click to expand...
Click to collapse
Okay, how about this...I intend to S-off and reinstall CWM the SECOND I get my new phone. LOL...Should I erase my ROMs+kernels from the SD card and start over from scratch, or can I just boot up again like nothing happened?
I guess its safer to start over, huh?
EDIT: I have been reading over stories involving a hard brick and QHSUSB_DLOAD. It seems it ALL came from SD card partitioning in CWM. I was also in recovery that day restoring my ROM when I accidentally touched the screen and the phone rebooted. (After restoring) I thought it was just rebooting recovery. I wonder if something else happened? The phone booted up fine and worked for some time after. The last thing done was charging the phone via wall charger, seeing it was done, and then unplugging.
Matt
it may not be necessary, but I would. I'd just redownload all the software I plan on loading from the start and give it a clean slate, but that's just me. Also be very careful with resorting apps and data since we really don't know the total cause of your issue. All in all you probably won't have to deal with this again as long as you minimize your risk.
nice. maybe there are aliens inside your phone! Just a thought as it seems everyone seems to just turn around when they see this problem. some of the brave ones got taken by the aliens too for snooping out too much
vitusdoom said:
nice. maybe there are aliens inside your phone! Just a thought as it seems everyone seems to just turn around when they see this problem. some of the brave ones got taken by the aliens too for snooping out too much
Click to expand...
Click to collapse
Im the alien!
Yea, I never saw this happening to me. I read carefully before I do anything and have never tried anything fancy.
Im guessing that QHSUSB_DLOAD lets you know the phone is fully erased and waiting for something to be flashed the elite way? (From the factory via their gadgets). To date, NO ONE has recovered from this.
Man Id love to be the one to recover! I crapped myself when I saw QHSUSB_DLOAD mentioned on my computer. Its the kiss of death.
I also have to wait till next week to get my replacement despite me opting for the fastest most $$$ method of shipping. UPS Express is the fastest and will take till monday (which means tuesday since no one will be around to sign for it).
Ugg..
Matt
Doh! that just sucks Matt. but then again, thats way better than having some hardware issue and being fixed (anything with hardware issue fixed surely ends up going back to the guys that fixed it. they seem to put some time bomb in there so you'll go back crying to fix it again and again. lol) haven't had this issue ever since.(was flashing my phones way back then) maybe im just lucky. hopefully i will not encounter this. (the only thing I bricked was my brand new PSP2002. just bought it from US and im way over in NZ mate - didn't have a option to return it. )
where does this QHSUSB_DLOAD appear? would this come up when you turn the device on? because i've seen some devices that are bricked, they just lit up and goes off and never charges and can't go to bootloader. thinking this is 100% bricked or this QHSUSB thingy is the pure brick?
vitusdoom said:
Doh! that just sucks Matt. but then again, thats way better than having some hardware issue and being fixed (anything with hardware issue fixed surely ends up going back to the guys that fixed it. they seem to put some time bomb in there so you'll go back crying to fix it again and again. lol) haven't had this issue ever since.(was flashing my phones way back then) maybe im just lucky. hopefully i will not encounter this. (the only thing I bricked was my brand new PSP2002. just bought it from US and im way over in NZ mate - didn't have a option to return it. )
where does this QHSUSB_DLOAD appear? would this come up when you turn the device on? because i've seen some devices that are bricked, they just lit up and goes off and never charges and can't go to bootloader. thinking this is 100% bricked or this QHSUSB thingy is the pure brick?
Click to expand...
Click to collapse
The message QHSUSB_DLOAD appears the first time I tried to connect via USB to my computer. It showed up on my computer down where usb notifications occur. After it told me it couldnt install hardware, that was it. No more action from either the phone or the computer. Its like the world just passed right by my poor phone.
Maybe I will get lucky and get a phone free of dust as well! I was waiting on calling in that care package for later...Oh well.
Matt
Oooh nice! so the device really has a black screen and that message appeared on driver installation on you computer.
most of the people in the net just mentions that this driver is missing. If the driver is missing, maybe it did really get corrupted(software because of rom-manager not pointing to this ) but yeah, could also be hardware failure. did it say on your computer that it was installing some drivers for that QHSUSB_DLOAD? and it failed? what about HTC? did you see anything from HTC about this?
vitusdoom said:
The message QHSUSB_DLOAD appears the first time I tried to connect via USB to my computer. It showed up on my computer down where usb notifications occur. After it told me it couldnt install hardware, that was it. No more action from either the phone or the computer. Its like the world just passed right by my poor phone
Click to expand...
Click to collapse
this is the EXACT problem im having! on my tmobile SGS2
not sure if this has already been mentioned but what do you guys think of this?
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-ii-jtag-brick-repair/
Hey guys,
I'm in the same situation too.... I've been flashing hundreds of roms and all kind of software on a lot of different android phones...but this is the first time ever I came across something like that where I feel that this is the end of it!!!! I made a mistake...by not paying attention flashing an HD2 rom to my sensation!!! You know some time s**t happens... and here we go...I got a completely dead bricked sensation with nothing i can do, even I've been searching and reading for 2 days with no luck what so ever...so I guess no one is able to find a solution for this issue yet!!!!Which is too bad: confused: .I wish I was able to find some solution to this problem so I can get my phone back to life and help every one else who might end up with this issue. Because I think a lot of people might be in this situation!!!. I tried every thing I can possibly do with m y knowledge and the results was all dead ends. I just hope that this issue will be taken to the next level by some one...like all the other phones that it can be unbricked...so why not the sensation!!!?. Any one can come up with and ideas for this please help us as a community to get pass by this dead end on our Htc sensations.
Guys i have absolutely same problem with my sensation, i believe there must be a way how to bring our phones back to life. Im sure that on my phone its just software problem caused by backing to s-on(got bricked right after adb rebootbootloader). So if some1 find out how to unbrick, PLEASE post it. I dont want to solve it by warrany, because its little far for me :-(