Related
Hey everyone - my first post here.
Anyway, I read and read and read about my new Vibrant to see just what I could do with it without screwing it up and bricking it and I find out my device is hardware locked.
After reading [GUIDE] / [THINK TANK] - Accessing downloader & recovery w/ locked hardware access (I cannot post a link just now, apparently) from start to finish, I am more confused than not. I cannot do anything but stay in a boot loop (by holding buttons down) or boot up the phone like normal. No recovery or download mode has so far been possible.
So, can I root my phone? Should I just attempt to exchange it? Should I wait for a work-around? Or is there information I'm missing somewhere?
Thanks, all. This community is insanely helpful and cordial, without you guys I'd never have gotten my dream working properly.
Edit: I was told that my lack of drivers were the problem - I thought I didn't need them on a 32 bit system. I did. Recovery reboot solved for me!
If you cannot enter Recovery Mode with Vol Up+Vol Down+Power, your phone is defective and T-Mo will exchange it.
You're serious? It really is that simple?
So, I call them up, tell them I have a hardware locked phone and I cannot boot into recovery mode, and they'll set me up?
I'm thinking I had to go learn odin and start getting less a'scared of command lines.
FenixGryph said:
Hey everyone - my first post here.
Anyway, I read and read and read about my new Vibrant to see just what I could do with it without screwing it up and bricking it and I find out my device is hardware locked.
After reading [GUIDE] / [THINK TANK] - Accessing downloader & recovery w/ locked hardware access (I cannot post a link just now, apparently) from start to finish, I am more confused than not. I cannot do anything but stay in a boot loop (by holding buttons down) or boot up the phone like normal. No recovery or download mode has so far been possible.
So, can I root my phone? Should I just attempt to exchange it? Should I wait for a work-around? Or is there information I'm missing somewhere?
Thanks, all. This community is insanely helpful and cordial, without you guys I'd never have gotten my dream working properly.
Click to expand...
Click to collapse
Here's my advice in a step-by-step:
-Install the AndroidSDK (And make sure it is named that) Found here - http://developer.android.com/sdk/index.html
-Move the folder to Computer> Local Disk ( C: )
-Run the .exe
-Go to Settings, click on Miscellaneous, and check Force https
-Click on Available Packages and install (And then minimize)
-Click Start and search cmd (Also known as Command Prompt)
-Type cd\ (And then press enter)
-Type AndroidSDK\Tools\adb reboot download (And then press enter)
**Make sure your phone is plugged into the computer with USB Debugging turned on.
Your phone will reboot and be in Download Mode. Hope this helps.
Hardware Locked, huh? really? on the vibrant?
Can someone explain what hardware locked vibrant is. Is this some term you guys made up. I can not for the life of me, figure out, why in the world Samsung would ship some phones hardware locked and others not.
Makes no sense, someone explain, seems like this is a made up term which does not apply to Vibrant.
Either Samsung is being completely ignorant to this issue or they have the worst quality control. I am beginning to think it's both. Simply google searching brings up lots of results on this issue.
My first Vibrant (USB port eventually broke) 3 button recovery worked fine; dated July 15. The replacement after that did not work, nor did the one after that. Those were both made on Aug 16. I finally got a refund under buyer's remorse and waited another week. Got my fourth Vibrant today, made 09/01 and yes it does work with 3 button recovery.
Keep in mind none of my Vibrants were refurbished units. They were all brand new. I think Samsung has a serious flaw on their hands. I'm concerned about keeping this phone even but I added the insurance on it just in case.
By "hardware locked" they mean that you cannot access the phone's recovery or dl mode using the 3 button method.
this has apparently started with the 08/**/2010 batches. beforehand this phone was deemed "unbrickable" but it's now actually possible with the newer shipments so ppl have got to be a lot careful trying to mod their phones now.
on a side note: i've read that Samsung Mobile Canada has admitted that the hardware locked phones are in actuality a defect. hopefully Samsung Mobile USA will come to the same conclusion.
sabooher said:
Either Samsung is being completely ignorant to this issue or they have the worst quality control. I am beginning to think it's both. Simply google searching brings up lots of results on this issue.
My first Vibrant (USB port eventually broke) 3 button recovery worked fine; dated July 15. The replacement after that did not work, nor did the one after that. Those were both made on Aug 16. I finally got a refund under buyer's remorse and waited another week. Got my fourth Vibrant today, made 09/01 and yes it does work with 3 button recovery.
Keep in mind none of my Vibrants were refurbished units. They were all brand new. I think Samsung has a serious flaw on their hands. I'm concerned about keeping this phone even but I added the insurance on it just in case.
Click to expand...
Click to collapse
I think that's the first phone dated after 08/** that i've heard of actually having the 3 btn modes work. My bf has a vibrant and I've been holding off purchasing one myself since hearing about the hardware locked ones. i've been literally scouring ebay for a phone that was a part of the July batch.
well, this gives me a little hope.
Oniyuri said:
By "hardware locked" they mean that you cannot access the phone's recovery or dl mode using the 3 button method.
this has apparently started with the 08/**/2010 batches. beforehand this phone was deemed "unbrickable" but it's now actually possible with the newer shipments so ppl have got to be a lot careful trying to mod their phones now.
on a side note: i've read that Samsung Mobile Canada has admitted that the hardware locked phones are in actuality a defect. hopefully Samsung Mobile USA will come to the same conclusion.
Click to expand...
Click to collapse
Well just my 2 cents on the topic, entering recovery mode required following strict steps, miss 1 single step, and you won't get into recovery.
now as far as download mode goes, I have been able to get into it once. This was by accident, I was randomly doing various sequences of volume rocker and power, it went into download mode. Now since then, I have no clue what sequence I used, but I have never been able to get into download mode ever again.
Additionally, my phone is dated 7/2010, so the 8/2010 batch theory doesn't hold since I can not get into download mode either now.
To get into Recovery Mode, follow these steps.
Okay, I'm reading lots of people having trouble getting into recovery mode, thinking their phone is broken or busted. Chances are you are not holding down the power button log enough, or you are letting go of something too quick.
FOLLOW THESE DIRECTIONS STEP BY STEP.
1) START with your phone off
2) Press volume up AND volume down at same time, keep them pressed in the entire time, do NOT let go. I prefer to hold my phone in landscape, this gives me better control with my fingers.
3) WHILE holding down volume up and volume down, press and hold power button, DO NOT LET GO OF ANYTHING. You should be holding down volume up, volume down, and power, DON'T LET GO! HOLD ON... and proceed to next steps, dont let go!
4) PHONE will start, you will see the white Vibrant logo. STILL DON'T LET GO, volume down, volume up, and power all pressed.
5) White Vibrant logo disappears, still dont let go!
6) White Vibrant logo re-appears again for the second time. Right when you see the white vibrant logo pop up a second time, let go of ONLY the power button, keep holding down volume down and volume up.
7) Phone enters recovery mode, you can let go the volume rocker.
hope this helps, it worked for me, hopefully it works for you also.
now can someone post sure fire method into getting into download without needing to connect the phone to your computer and using odin?
Oniyuri said:
I think that's the first phone dated after 08/** that i've heard of actually having the 3 btn modes work. My bf has a vibrant and I've been holding off purchasing one myself since hearing about the hardware locked ones. i've been literally scouring ebay for a phone that was a part of the July batch.
well, this gives me a little hope.
Click to expand...
Click to collapse
Hate to break it to you, my phone is made in July, and it WILL NOT go into download mode, I do however get into recovery mode.
That phone date batch theory doesn't hold true, so you can stop searching for july phones.
Oniyuri said:
on a side note: i've read that Samsung Mobile Canada has admitted that the hardware locked phones are in actuality a defect. hopefully Samsung Mobile USA will come to the same conclusion.[/QUOTE]
where did you read this, please provide the link
Click to expand...
Click to collapse
Samsung Mobile USA support is worthless. I called three times and finally got someone in "premier support" who didn't know anything. He actually went as far as to tell me a simple data wipe would resolve this problem, ha! I then got a hold of someone at Samsung Telecom corporate office who said he'd look into it and never called me back. No surprise there either. I think it's kind of sad that people are having to resort to Facebook wall comments to get a company to start backing it's products.
Thanks to sabooher, I was able to get into download mode with no problems, I hope this works for you, and thank you again sabooher.
okay, start off with your phone turned off
hold down both volume down and volume up at the same time, do not touch the power button
now, get your usb cable, have one end into your computer, the other end put into your vibrant, while you are still holding down the volume up and volume down at same time. dont touch power button
your phone hopefully will now go into download mode!
SamsungVibrant said:
FOLLOW THESE DIRECTIONS STEP BY STEP.
Click to expand...
Click to collapse
Nope, no good.
jonathan3579 said:
Here's my advice in a step-by-step:
Click to expand...
Click to collapse
Had the sdk already, so that was no problem. With usb debugging on, I had the same problem I've always had with adb - error: device not found.
SamsungVibrant said:
Oniyuri said:
on a side note: i've read that Samsung Mobile Canada has admitted that the hardware locked phones are in actuality a defect. hopefully Samsung Mobile USA will come to the same conclusion.
Click to expand...
Click to collapse
where did you read this, please provide the link
Click to expand...
Click to collapse
Sure, it's all over their facebook page. I've read tons of android sites so I can't quote the site that led me to this page but I've been following the Samsung Mobile Canada FB page over the last few days about it. Suffice it to say: the Bell customers are really not pleased with the 3 btn issue: Samsung Mobile Canada
FenixGryph said:
Nope, no good.
Had the sdk already, so that was no problem. With usb debugging on, I had the same problem I've always had with adb - error: device not found.
Click to expand...
Click to collapse
maybe you don't have the correct drivers installed, try the ones from this thread --> http://forum.xda-developers.com/showthread.php?t=728929
Well here's my take on things. I got my phone (July 11th build date) directly from T-Mobile corporate. Came via FEDEX on launch day. Long story, suffice to say I had Behold II and complained to the right people at the right time and got swapped a Vibrant to basically shut me up.
Entering download mode seems to be very timing specific even for this original batch phone. There is only one way I can reliably get download mode 100% of the time...
- Pull battery
- plug in to USB cable connected to PC
- hold down VOL DOWN + VOL UP (DO NOT HOLD DOWN POWER)
- Insert battery
Alternately I can get into download mode using VOL DOWN+ VOL UP + POWER, but I have to be very careful to catch the right moment after the Vibrant logo appears the 2nd time to release power to get download mode.
When I ODIN, I use the first method always now.
masterotaku said:
Entering download mode seems to be very timing specific even for this original batch phone. There is only one way I can reliably get download mode 100% of the time...
- Pull battery
- plug in to USB cable connected to PC
- hold down VOL DOWN + VOL UP (DO NOT HOLD DOWN POWER)
- Insert battery
Alternately I can get into download mode using VOL DOWN+ VOL UP + POWER, but I have to be very careful to catch the right moment after the Vibrant logo appears the 2nd time to release power to get download mode.
When I ODIN, I use the first method always now.
Click to expand...
Click to collapse
That's odd. I've never had a problem getting into download mode; in fact, I was confused the first time it happened cuz I didn't mean to! All I have to do is make sure the USB cable is plugged in and then hold all 3 buttons when I turn it on and into download mode it goes.
crazycaveman said:
That's odd. I've never had a problem getting into download mode; in fact, I was confused the first time it happened cuz I didn't mean to! All I have to do is make sure the USB cable is plugged in and then hold all 3 buttons when I turn it on and into download mode it goes.
Click to expand...
Click to collapse
I tend to have bad luck with Odin too. I've seen the "ohsh*t" icon many times...
(note: the "ohsh*t" icon is what I call the phone/caution symbol/pc icon I tend to see quite often)
When that happens the ONLY way I can get back to download mode is the battery-insert method.
FenixGryph said:
Nope, no good.
Had the sdk already, so that was no problem. With usb debugging on, I had the same problem I've always had with adb - error: device not found.
Click to expand...
Click to collapse
It definitely sounds like you don't have the correct drivers installed. My drivers were downloaded through the installation of Kies, however, is your computer online while you are attempting this? I can only speak for my computer which is running Windows 7, but it automatically downloads any updated/new drivers necessary when connected online.
woot!
Ha ha!! The drivers were the problem. I was under the impression I only had to install the samsung drivers if I was on a 64 bit system.
I'm looking at my recovery menu now and am very happy! Wish I had time to do the stuff I wanted to do the vibrant before work, but I gotta make a couple of bucks before I get this guy set up just how I want.
See? I knew XDA was the place to be. Many thanks Oniyuri and jonathan3579!
so I made an ultra bone head move. I orginally bricked my phone to hte point it said AST_STAT in red text I think learned of the vol up and down tick to put iit into download mode. I was able to flash and had a working device again although be it 2.1.
I should of really stopped at this point, I figured man that was easy I'll get the latest firmware and get back up to 2.2 well it bricked again I have the computer, phone and the ! I figured okay no problem its not as bad as last time right?
WRONG none of the button combos work and I bought a jig from mobiletechvideos.com and that just displays the same thing as above I can't get into download mode to save my life on my phone.
I've got a new one coming from T-Mobile as a swap but seriously the $450 axe they have hanging over my head doesn't feel so good I know there was a similar thread but it never went anywhere there was no resolution and I'm hoping one of you fine posters will have a trick to help me out of this jam.
I've tried every button combo nothing seems to do it I just couldn't leave well enough alone lesson learned but I'm hoping there is still a way out.
Thanks everyone!
...What did you try flashing that first time?
It wasn't per chance something that contained bootloader like one of the new Gingerbread ROMS was it? A few of them still have bootloader flashes which can brick you.
It would be helpful if you listed what you tried flashing and the steps you took.
When I brick like that, that's the only screen I get. If Odin sees your phone, you can flash it. The !--pc screen doesn't matter.
Sent from my GT-I9000 using XDA Premium App
Orginally flashed it with T959UVJFD.tar and 512.PIT using ODIN3 1.0 ODIN does see my phone I'll keep giving it a shot it kept freezing at Cache.rpf but persistence might pay off.
Thanks for the quick replies!
You should try using Odin 1.7. I found it works best.
Soo who wants the first handy J in the corner? J/K you guys are ****ing amazing you will be dumbfounded none the less.
So here is my situation.
MY Rig:
Dell XPS 420
Win 7
Wife's PC
Custom built Win 7 with ABIT Mobo
I D/L ODIN 7 it fails again at Cache.rfs so I pull the plug just like the first time around I turn it on and notice it isn't turning on quickly anymore so I use hte JIG BOOM DOWNLOAD MODE!!
My XPS will not flash my phone to save my life so once again I flashed on hers using ODIN 1.0 and same FW as mentioned above it failed on cache.rfs and I pulled the plug and put it in download mode again using two button (vol + -, USB + Battery) and it flashes it fine.
Seriously I'm in debt and I so want to move to CM 7 as my buddy runs it on his t-mobile 4G (the very first 4g phone can't remember name) but I think I'm just going to hold my horses on doing anything for awhile
I honestly think the XPS 420 chipset might not be good for flashing android phones I never ever could get it to go I even tried in a virtual environment running XP and same exact thing occurred every time.
sorry to repeat myself but thank you, thank you, thank you, thank you!
Hey Guys,
I am sorry in advance if similar issue has been posted but I really need your help !
I just got my gtab and flashed with TnT Lite 4.4.0. I need to restore the original from factory. Now I am facing a problem, I can't go to the recovery mode because it stayed at viewsonic logo (not gtab). I can see the "recovery key detacted" at upper left corner but nothing else.
Please help me on back to restore the original or how can I go into the recovery mode to install/modify ?
I am just a new born baby and just step in this android world. any suggest is great help for me.
Thank you
Follow my link.
What happens if you hold only the power button for several seconds (10-30). Will your tab reboot? If it does what do you get then?
buchaneer.nl said:
What happens if you hold only the power button for several seconds (10-30). Will your tab reboot? If it does what do you get then?
Click to expand...
Click to collapse
Holding it for 10-30 seconds and then release will yield the same result as if you hold it for 5 seconds and then release. The gtab will turn off. To turn it on again, you need to hold the power button again.
Sorry for not stating the obvious What happens when you restart? Does it start up?
goodintentions said:
Holding it for 10-30 seconds and then release will yield the same result as if you hold it for 5 seconds and then release. The gtab will turn off. To turn it on again, you need to hold the power button again.
Click to expand...
Click to collapse
Hey Goodintentions if you want a monopoly on answering questions go right ahead. My intentions were only to help. Maybe you have more of a vested interest
Haha, I just temporarily have a lot of free time due to almost dying but now suffering from a massive infection. Right now, moving my fingers to type is about the only thing I can do comfortably.
Think of it this way. While I was 40 feet in above ground hand sawing a large branch off, it got loose, caught one of the ropes on its way down, the rope caught my arm, and dragged me down with it. Hanging on for my dear life, I used my other hand to grab the hand saw still dangling and cut the rope freeing my arm. The damn thing took a large chunk of my skin with it. I think it stretched my left arm out several inches.
Anyway, my dumbass decided it wasn't serious enough to go to the doctor. Patched up everything by myself and now I have an massive infection, a very sore arm, and lots of free time.
Edit.
Not to mention that asshole neighbor of mine who called the city to complain that I left the branch out violating city code.
How you get better...
goodintentions said:
Haha, I just temporarily have a lot of free time due to almost dying but now suffering from a massive infection. Right now, moving my fingers to type is about the only thing I can do comfortably.
Think of it this way. While I was 40 feet in above ground hand sawing a large branch off, it got loose, caught one of the ropes on its way down, the rope caught my arm, and dragged me down with it. Hanging on for my dear life, I used my other hand to grab the hand saw still dangling and cut the rope freeing my arm. The damn thing took a large chunk of my skin with it. I think it stretched my left arm out several inches.
Anyway, my dumbass decided it wasn't serious enough to go to the doctor. Patched up everything by myself and now I have an massive infection, a very sore arm, and lots of free time.
Edit.
Not to mention that asshole neighbor of mine who called the city to complain that I left the branch out violating city code.
Click to expand...
Click to collapse
Sorry to hear of your accident.
You have been very helpful to me. Thanks.
Hard-bricked?
Hello everybody,
I had VEGAn-GE-7.0.0-RC1-Harmony-signed flashed into my gtablet and I tried to flash update-smb_a1002-4349-user.
I've got a error (something similar to: bootloader not a command...) and after restart the tablet is bricked.
When I enter into recovery mode, I have the two messages
Detect a recovery key pressed
Booting recovery kernel image
and the tablet stop there. No changes in the screen and no USB recognition.
So I can't fix that with nvflash. It seems that the recovery kernel image (if there is one) is corrupted.
Do you know a solution for this case?
Thanks in advance
fogamz said:
Hello everybody,
I had VEGAn-GE-7.0.0-RC1-Harmony-signed flashed into my gtablet and I tried to flash update-smb_a1002-4349-user.
I've got a error (something similar to: bootloader not a command...) and after restart the tablet is bricked.
When I enter into recovery mode, I have the two messages
Detect a recovery key pressed
Booting recovery kernel image
and the tablet stop there. No changes in the screen and no USB recognition.
So I can't fix that with nvflash. It seems that the recovery kernel image (if there is one) is corrupted.
Do you know a solution for this case?
Thanks in advance
Click to expand...
Click to collapse
You flashed a 1.2 bootloader ROM over a 1.1 bootloader ROM using ClockworkMod. That is a sure recipe for problems. You will have to use nvflash to fix it. Go to Goodintentions "GTablet for Dummies" website. Don't be surprised if you don't see the VS Birds logo (or anything else) when you try to get into APX mode. Many people that have done this don't.
Thanks K J Rad,
Yes, I've tried cod triple red unplugging the batteries
http://viewsonic-gtablet-for-dummies.webs.com/starthere.htm
http://forum.xda-developers.com/showthread.php?t=1118087
all the night and still no change.
The screen stays with the birds logo and with the two sentences (... booting recovery kernel image), no black screen as described in NVFlash procedure, and my PC doesn't recognise the USB device (not listed with lsusb in Ubuntu and no identification in windows), so I can't nvflash.
I'm going to try to drain the batteries but it seems that the kernel image is corrupted and the sw is not reseted when power off.
Hard case?
Many thanks
fogamz said:
Thanks K J Rad,
Yes, I've tried cod triple red unplugging the batteries
http://viewsonic-gtablet-for-dummies.webs.com/starthere.htm
http://forum.xda-developers.com/showthread.php?t=1118087
all the night and still no change.
The screen stays with the birds logo and with the two sentences (... booting recovery kernel image), no black screen as described in NVFlash procedure, and my PC doesn't recognise the USB device (not listed with lsusb in Ubuntu and no identification in windows), so I can't nvflash.
I'm going to try to drain the batteries but it seems that the kernel image is corrupted and the sw is not reseted when power off.
Hard case?
Many thanks
Click to expand...
Click to collapse
Did you hold the Volume Down button as you were powering up?
many thanks
That's it.
I was allways pressing up. Sorry by the misundertunding and many thanks.
Regards
fogamz said:
That's it.
I was allways pressing up. Sorry by the misundertunding and many thanks.
Regards
Click to expand...
Click to collapse
Aha! You didn't follow my instructions properly. Goodness...
Added by edit.
Here is a screenshot of that portion of my instruction. Notice where the arrow is pointing at.
Are you restoring to stock to do an RMA?
goodintentions said:
Aha! You didn't follow my instructions properly. Goodness...
Added by edit.
Here is a screenshot of that portion of my instruction. Notice where the arrow is pointing at.
Click to expand...
Click to collapse
Hi, I am looking a zip file
gtab.nvflash.1.2.branch.20110617.zip
the file is 99.41 MB but I ALWAYS stock at 9.9 MB
Is it any available file I can download ??
Please help
What country are you from? I'll host it elsewhere it it makes a difference for you.
Added by edit.
Hang on. I host no such file on my website. Go to my website linked in signature and try to download that nvflash file.
goodintentions said:
What country are you from? I'll host it elsewhere it it makes a difference for you.
Added by edit.
Hang on. I host no such file on my website. Go to my website linked in signature and try to download that nvflash file.
Click to expand...
Click to collapse
I just try to download the nvflash with 1.2 branch with newer update. The nvflash1.2 zip and gtab.nvflash.1.2branch20110508.zip both stopped at 10.0 MB
Please help ! I am at Los Angeles area
Viewsonic G Tablet will not boot. Only APX mode works - 20110707
20110713- FYI. I re-posted the restore step information as a new thread and added some additional content on APX Mode and nvflash.
http://forum.xda-developers.com/showthread.php?t=1167944
Holy cow, man, that's some effort there for your wife. If it were me, I'd say "screw you, wife, here's a paperweight. Try to make it work since I screwed it up."
But seriously, I've said this before and I'm going to say it again. I'm constantly amazed at these rare cases of unrecoverable brickary that only a hand full of people get. And I have 3 gtabs to work with, not to mention thousands of visitors to my site.
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 there,
I think my z3tc just died.
I flashed the z3c firmware (only system) via flashtools in order to gain root with giefroot.
The tablet started, but the root process failed, and I had to hard reset the tablet (vol-,vol+,on/off), after that the device would not start again.
I tried the yellow reset-knob (beside the sim slot) for 10 secs ... nothing
vol-,vol+,on/off for 10 secs ... nothing
plugged it to the original wall-charger with the original cable ... nothing, not even the led shows up.
Has anybody an idea, or is my device a case for the wastebin?
Thanks in advance!
Hansifranzi said:
Hi there,
I think my z3tc just died.
I flashed the z3c firmware (only system) via flashtools in order to gain root with giefroot.
The tablet started, but the root process failed, and I had to hard reset the tablet (vol-,vol+,on/off), after that the device would not start again.
I tried the yellow reset-knob (beside the sim slot) for 10 secs ... nothing
vol-,vol+,on/off for 10 secs ... nothing
plugged it to the original wall-charger with the original cable ... nothing, not even the led shows up.
Has anybody an idea, or is my device a case for the wastebin?
Thanks in advance!
Click to expand...
Click to collapse
You flashed the wrong firmware. You could be hard bricked. Basically if you can't get into flash mode and flash the proper firmware then your screwed.
For future reference quadruple check your firmware before you flash the ftf file.
If your rooting SGP621 then you should have flashed the D6603 .93 firmware because that's the one with the exploit.
Sent from my D6603 using XDA Free mobile app
Thanks for the answer.
I have the SPG611, is it the same firmware to exploit as for the SPG621, namly D6603 .93?
Hansifranzi said:
Thanks for the answer.
I have the SPG611, is it the same firmware to exploit as for the SPG621, namly D6603 .93?
Click to expand...
Click to collapse
No the xploit shouldn't work because the system is quite different. SPG621 is the LTE version and I think 611 is the Wi-Fi version. The 621 runs on cellphone hardware very similar to the Xperia Z3 where the 611 has no LTE connectivity. It wouldn't be wise to flash a D6603 firmware on it because the hardware it too different.
Sent from my D6603 using XDA Free mobile app
I just found this:
http://forum.xda-developers.com/z3-...t-rooting-sgp611-giefroot-bootloader-t3017314
So I think it should also work on the WiFi Version (SPG611).
Dead Z3c Tab
Hansifranzi said:
Hi there,
I think my z3tc just died.
I flashed the z3c firmware (only system) via flashtools in order to gain root with giefroot.
The tablet started, but the root process failed, and I had to hard reset the tablet (vol-,vol+,on/off), after that the device would not start again.
I tried the yellow reset-knob (beside the sim slot) for 10 secs ... nothing
vol-,vol+,on/off for 10 secs ... nothing
plugged it to the original wall-charger with the original cable ... nothing, not even the led shows up.
Has anybody an idea, or is my device a case for the wastebin?
Thanks in advance!
Click to expand...
Click to collapse
This is EXACTLY what happened to me. No LEDs going on - nothing. Device 3 weeks old from Amazon Germany. I sent it in for repair, got it back today with a notice that because I had the bootloader unlocked the warranty is void and they didn´t do anything with it. BUT: When I got it back it was alive again, I could get it into fastboot mode. So I called the technician to ask how they had reset the hardware. They said they hadn´t done anything. I remember having read about a guy who had the same problem, when he packed the tablet to send it in after a couple of days he noticed it would turn on again.
So here is what I think: If you flashed the wrong boot.img or whatever and the Z3c Tab goes completely dead (no charging, no LEDs, no nothing) just wait a couple of days. May be some capacitator has to run flat or I don´t know what but just wait.
Pleas let us know if this works for you, might help other people here and I sure wonder if just letting it sit there can help when everything seems to be f*** up
Thanks for sharing your experience. I also read the post from the guy, who wanted to return it and discovered that it turned back to life.
How many days did it take from returning it to amazon to receiving it back?
Did you connect it to the computer with vol-, and the blue led came back?
It has been three days now, but connecting it to the computer or to the wall-charger didn't change a thing.
Took about 3 days to get it back. May be we have to let the battery discharge?
When I got it back (volume down + USB plugin) was working again, when I sent it in didn't do a thing, no LED. Once you have it back to fastboot mode it's really a piece of cake.
Doolittle Duckbill said:
Took about 3 days to get it back. May be we have to let the battery discharge?
When I got it back (volume down + USB plugin) was working again, when I sent it in didn't do a thing, no LED. Once you have it back to fastboot mode it's really a piece of cake.
Click to expand...
Click to collapse
I also thought about the battery, I will wait at least for monday, and then report back.
Hansifranzi said:
I also thought about the battery, I will wait at least for monday, and then report back.
Click to expand...
Click to collapse
Basically the trick here is to let the battery go dead OR disconnect the battery and reconnect it again but I suppose that would be a hastle.
Also, plugging again and again would charge the device especially if you are trying to discharge the battery fully.
If you are certain that all drivers are fully installed and it does not show any sign at all. I would suggest that hold down power + volume up/down depending on which mode you want to boot. The trick here is KEEP HOLDING POWER AND VOLUME KEY while at the same time plugging in the device to your PC. I am sure the LED would blink or something (I do not have the device but all Sony work this way)
I had a similar incident with a Sony Phone, just like your tablet symptoms but this trick worked for me.
Try that and report back to me, I would like to see what happens and if you need any help, do no hesitate to quote me back!
Good Luck and make sure you flash the RIGHT FTF this time
Hnk1 said:
Basically the trick here is to let the battery go dead OR disconnect the battery and reconnect it again but I suppose that would be a hastle.
Also, plugging again and again would charge the device especially if you are trying to discharge the battery fully.
If you are certain that all drivers are fully installed and it does not show any sign at all. I would suggest that hold down power + volume up/down depending on which mode you want to boot. The trick here is KEEP HOLDING POWER AND VOLUME KEY while at the same time plugging in the device to your PC. I am sure the LED would blink or something (I do not have the device but all Sony work this way)
I had a similar incident with a Sony Phone, just like your tablet symptoms but this trick worked for me.
Try that and report back to me, I would like to see what happens and if you need any help, do no hesitate to quote me back!
Good Luck and make sure you flash the RIGHT FTF this time
Click to expand...
Click to collapse
Thanks for the answer!
I just plugged the tablet into the usb-port of my laptop while holding VOL- and POWER, the led showed no signs, same as computer, also no signs. I will try again on Monday, the battery is surely dead until then. Hope dies last.
That guy must have been me Had the exact same story happening with a Galaxy Tab S. Looked like hard bricked, back to Media Markt with it, no, no, we won't lift a finger you evil tinkerer - and then it suddenly worked again. I had realized they must have done something. Because how would the see that my device's software had been tampered with if they didn't turn it on?!
Anyway, I tried that convoluted rooting method on my brand spanking new Z3Tc (is that the official abbrev.?) However, managed to get into flash mode somehow. It's embarassing for somebody like me but I'm on unrooted stock now... after about 20 Android devices, none of which wasn't rooted or an alternative ROM all the way
Good luck on reviving your tablet!
Hansifranzi said:
Thanks for the answer!
I just plugged the tablet into the usb-port of my laptop while holding VOL- and POWER, the led showed no signs, same as computer, also no signs. I will try again on Monday, the battery is surely dead until then. Hope dies last.
Click to expand...
Click to collapse
Led or any othehr signs are useless as long as the device is detected. Had it ?
Try power + volume up as well while flashtool running. It'd give you a better idea of detection. Even try power + both volume up and down.
Also plug in to Sony Official tool and see if that can help you repair it ? It might detect it as well.
Hnk1 said:
Led or any othehr signs are useless as long as the device is detected. Had it ?
Try power + volume up as well while flashtool running. It'd give you a better idea of detection. Even try power + both volume up and down.
Also plug in to Sony Official tool and see if that can help you repair it ? It might detect it as well.
Click to expand...
Click to collapse
When my Tab was dead none of the above worked, also "lsusb" in linux showed that it was not detected.
Concerning the question of what the technicians at MediaMarkt or support.com might have done: I know they used the "emma" software from the sony developer homepage to read out my z3c Tab. That apparently gave them the readout that the bootloader was unlocked. They sent me the screenshot together with the notice that they did not repair anything. So may be download "emma" for Windoze and hook it up to that... I use Linux with FlashTool which is supposed to be the same software (?). However, when my Tab was dead, FlashTool just said no device connected.
BTW: This is also the first (of many) Android devices that I now use UNROOTED. All others were rooted. It was also DEFINITELY the last-ever Sony device I ever bought. The hardware is nice, I need it waterproof because I use it on my motorbike. But this stupid rooting procedure is so screwed up that I will never ever buy Sony Android again!
I was really up and going for Sony, checking the internet on when the new z4 phone comes out, but my z3c tab user "experience" has now taught me better: Never again Sony!!!!!!!!!!!
Thanks for all the responses.
Using Windows 8.1 I tried:
USB-Plugging with all combinations of Power, Vol+, Vol- running
PC Companion
Emma
Flashtool
No Reaction at all.
Maybe the battery is still not empty.
Hope dies last.
Doolittle Duckbill said:
When my Tab was dead none of the above worked, also "lsusb" in linux showed that it was not detected.
Concerning the question of what the technicians at MediaMarkt or support.com might have done: I know they used the "emma" software from the sony developer homepage to read out my z3c Tab. That apparently gave them the readout that the bootloader was unlocked. They sent me the screenshot together with the notice that they did not repair anything. So may be download "emma" for Windoze and hook it up to that... I use Linux with FlashTool which is supposed to be the same software (?). However, when my Tab was dead, FlashTool just said no device connected.
BTW: This is also the first (of many) Android devices that I now use UNROOTED. All others were rooted. It was also DEFINITELY the last-ever Sony device I ever bought. The hardware is nice, I need it waterproof because I use it on my motorbike. But this stupid rooting procedure is so screwed up that I will never ever buy Sony Android again!
I was really up and going for Sony, checking the internet on when the new z4 phone comes out, but my z3c tab user "experience" has now taught me better: Never again Sony!!!!!!!!!!!
Click to expand...
Click to collapse
I will look into rooting Z3 compact without pre-rooted firmware / flashing any zip via recovery. There are few methods and Lollipop is a bit hard to crack but we would find it out soon enough! I will put up a guide in few hours and you can see if it works for you!
I think the support for your tablet is lacking and a need for an actual developer to sort things out.
I am not sure about EMMA much but usually I know about JTAG is used to recover hard brick devices. Giving it to Sony is always better option with an impression that you left it charge over night and it wouldn't turn on again. Always works!
Don't worry. It wouldn't be the first tablet hopefully!
Forgot to mention in my previous posts: when I got my tablet back from service, the battery was almost empty (<2%). That gives some support to the notion that you have to drain the battery to unbrick.
Note to would-be buyers who need root: stay away from this tablet (and probably Sony in general). The rooting procedure described in several threads here will drive you mad. It´s catch-22 all the way. (... after step 28 do step 11 unless your device is not LTE then do step 31 and you´re screwed with bootloop or hardbrick...) What a pile of sh**t!
Just tried again to plug it in,
sadly neither the computer nor the tablet showed any reactions in emma or flashtool.
Will try again in a few days.
Hope still is not dead.
Doolittle Duckbill said:
Forgot to mention in my previous posts: when I got my tablet back from service, the battery was almost empty (<2%). That gives some support to the notion that you have to drain the battery to unbrick.
Note to would-be buyers who need root: stay away from this tablet (and probably Sony in general). The rooting procedure described in several threads here will drive you mad. It´s catch-22 all the way. (... after step 28 do step 11 unless your device is not LTE then do step 31 and you´re screwed with bootloop or hardbrick...) What a pile of sh**t!
Click to expand...
Click to collapse
Nah you just need to read all the threads stick to the one you most understand and be cautious on every step
in my case i thought i needed root but after all the process and setting up my device it didnt feel right so I went back to stock the nice thing is that i have a backup of the TA partition just in case :victory:
I didn't touch the device for a week now.
But nothing has changed, still bricked. I will sell it as broken.
Hope has died. :crying: