Hello everyone, I know what you're going to say but I did a very wrong move.
I tried flashing recovery image through Rom Manager. It gave me four options and I chose Vega Advent. Now after a reboot, it doesn't even boot. I tried to connect to my PC but the USB doesn't detect a thing. I tried pressing the power button for about half a minute and then I tried pressing the power button together with the volume + and - and all together, but still nothing. I fully charged the battery until the light was green but this didn't make any difference.
The NVFlash always gives me "USB device not detected".
I don't know what to do. I'm in a hurry as I'm leaving the country in a couple of days and I don't have the time to argue with woot.com
I learned a lot from this forum in my HTC Hero, LG Optimus, Samsung Tab and the Asus Transformer. You are my last hope. Is there anyway I can unbrick this? Can I hard reset the device? Can I remove the battery and put it back again? Is there anyway out of this?
Please direct me to the right direction. thanks in advance...
Did you download the adb drivers and boot your gtab holding ppower and vol-
Check out http://viewsonic-gtablet-for-dummies.webs.com/
Mantara said:
Did you download the adb drivers and boot your gtab holding ppower and vol-
Check out http://viewsonic-gtablet-for-dummies.webs.com/
Click to expand...
Click to collapse
Well, I downloaded the usb drivers for the NVFlash. And yes I tried booting the device this way but the PC didn't detect it. The notification of new devices never came up.
What do you think I should do?
What os is your PC running?
You're effed.
You probably got the worst case of rom manager bombshelled. Permanent loop in apx mode + usb recognition borked.
I'm guessing you know how to get into apx mode by power button and volume -. If you haven't tried it, then I strongly you go to the website linked in my signature and go to nvflash page. I just included nvflash stock files with CWM pre-installed.
If you have been using apx mode all this time and nvflash still can't recognize your usb, then you have a nice life.
Windows XP 32 bit
goodintentions said:
You're effed.
You probably got the worst case of rom manager bombshelled. Permanent loop in apx mode + usb recognition borked.
I'm guessing you know how to get into apx mode by power button and volume -. If you haven't tried it, then I strongly you go to the website linked in my signature and go to nvflash page. I just included nvflash stock files with CWM pre-installed.
If you have been using apx mode all this time and nvflash still can't recognize your usb, then you have a nice life.
Click to expand...
Click to collapse
I tried to use your guide, well not from the start unfortunately. I downloaded all the files but I can't get the PC to recognize the gTab or even detect anything when I plug it in.
If I send it back to viewsonic, do you think they can refund back my money or at least send me a replacement (though I'll be leaving)??
Then like goodintentions said check out the link and do it start to finish. The links there are the right files.
I have beard of people recovering from this. Just make sure you have the right drivers installed. They are on the link above.
Check it out, try it start to finish and report back. We are here to help
Mantara said:
Then like goodintentions said check out the link and do it start to finish. The links there are the right files.
I have beard of people recovering from this. Just make sure you have the right drivers installed. They are on the link above.
Check it out, try it start to finish and report back. We are here to help
Click to expand...
Click to collapse
Thanks a lot. I'll try this first thing in the morning as I don't have access to a PC now. I'll definitely report back if the PC recognized the device. Because when it says "USB device not found press any enter to continue" it stop after I press enter. There is no way to make it start to finish...
ahmadshawki said:
Windows XP 32 bit
Click to expand...
Click to collapse
Here's the problem. I didn't think to post the driver for xp 32 because... well, I didn't think anyone was using it nowadays. Going to bed now. You should, too. Check back tomorrow. I'll work modify the website after I get back from my lab.
goodintentions said:
Here's the problem. I didn't think to post the driver for xp 32 because... well, I didn't think anyone was using it nowadays. Going to bed now. You should, too. Check back tomorrow. I'll work modify the website after I get back from my lab.
Click to expand...
Click to collapse
Don't know what to say. This is the best place where someone can get some real help. Just a small question, do you think if I had access to a Windows 7 32 or 64 bit or even Linux, it will help detecting the device? 'coz I can do that...
http://www.slatedroid.com/topic/171...ther-11-or-12-babased on.sed-images-g-tablet/
Link to files and nvflash I used on XP 32. Hope it healps
Xp64 is standard so you can find those files easy but this is what I used and I'm on 32
Mantara said:
http://www.slatedroid.com/topic/171...ther-11-or-12-babased on.sed-images-g-tablet/
Link to files and nvflash I used on XP 32. Hope it healps
Xp64 is standard so you can find those files easy but this is what I used and I'm on 32
Click to expand...
Click to collapse
I'm checking this out now and I'll report back if it worked. Thanks a lot...
http://www.myadventvega.co.uk/SystemUSB.zip
This is the adb driver I used
I wanted to add something. The device feels hot or warm to be precise from the back. Now after unplugging it for about five hours. Do you think it is running and this is only a software problem?
it might be in apx mode now. It is a blank screen. Hold power for 30 seconds and release. That will make sure its off. Then connect it to your PC and hold power volume -
I just helped vvvccc a little over a month ago... see link; my post starts as post #8. Before that, did you try pluggin into a different USB port and/or use a shorter USB cable on the PC?
http://forum.xda-developers.com/showthread.php?t=1056860
While you are at it, you may want to flash just the CWM once your computer recognizes the gtablet in apx.
http://forum.xda-developers.com/showthread.php?t=1058649
If this doesn't work... there are two more options floating around but one involves opening the gtabled up.
--- BTW, stay away from Rom Manager, it's the reason I wrote up the instruction to just flash CWM ---
Any news/progress?
Unfortunately none. I guess I'll go to bed now and tomorrow I'll have access to a linux pc. May be that will be a better idea. Thanks a lot for your support. I'll update you once I do it...
It was indeed working. It stayed like this for more couple of hours. I went to sleep and when I got up it was cold. I pressed the power button and it WORKED. Just like that. Now I shut it down once again and left to charge.
Thanks a lot everyone, I'm so proud I belong to this community.
One last question, what should I do now? Do I still have to NVFlash? Should I flash the right recovery now? Also, which Rom is recommended? At least to start with, knowing that I'm on 1.2.
Related
Hi everyone, i need ur help please. I have a t-mobile vibrant (sgh-t959). I tried the CM on it. After installing the su kernel, it bricked. Now it keeps rebooting with the samsung galaxy s gt-I9000 screen (the vibrant screen no longer comes up). I can't even get to download mode by pressing vol up + vol down + pwr buttons. Please help me. I m kinda desperate ...
http://forum.xda-developers.com/showthread.php?t=836815&page=6
Although I didn't have the exact same problem, I had a very similar problem. The above link will give you more details about the problem I was having and how I solved it (thanks to click1's suggestion).
I could not get into download mode no matter what sequence of keys I pressed and my phone hanged on the "samsung vibrant" screen. IF your phone is detected by Odin or the computer when you plug it in (doesn't have to be in download mode and your computer doesn't have to be able to show you the usb drives - just as long as there is a confirmation that a usb was connected is enough), then Android SDK will help you force the phone into download mode.
If this doesn't work, your next bet is to physically make a JIG for it:
forum.xda-developers.com/showthread.php?t=819551
From what I have read, this last one physically forces the phone to go into download mode by using the 5th pin on the MicroUSB key.
I know how you feel - I just got my fixed last night and my problem seemed very unique, I wish I could offer more help but I hope these will work for you.
Thank you very much. It finally came back to life. Feel so much better now!
downnload mode, I hold both volume buttons in and connect the usb and it I get into download mode everytime
rickyx said:
Thank you very much. It finally came back to life. Feel so much better now!
Click to expand...
Click to collapse
No problem, I'm glad that solved your problem. I'll see if I can put this solution on the Noob guide so others can see it easily before they resort to making a JIG.
osugsxr said:
downnload mode, I hold both volume buttons in and connect the usb and it I get into download mode everytime
Click to expand...
Click to collapse
the newer vibrants are hardware locked so you can't get into download mode that way. This is why you have to use the SDK to do it.
FriendlyCanadian said:
No problem, I'm glad that solved your problem. I'll see if I can put this solution on the Noob guide so others can see it easily before they resort to making a JIG.
the newer vibrants are hardware locked so you can't get into download mode that way. This is why you have to use the SDK to do it.
Click to expand...
Click to collapse
Does this mean if the sdk will not recognize that the device is connected then i have to make this JIG Thing? because my phone is stuck at the connect phone to pc screen.
raziel26 said:
Does this mean if the sdk will not recognize that the device is connected then i have to make this JIG Thing? because my phone is stuck at the connect phone to pc screen.
Click to expand...
Click to collapse
Yes, make it or buy one. I know who sells them for a VERY reasonable price. If you're interested Pm me for more info.
okay found a solution for now, my issue was related to ROM manager with the SD card, kept getting wrong MD5 Sum!! Really pissed me off about this since I was running through ODIN correctly,
Solution...
Updated the rom with Eugene froyo!! This brought me out of boot looping and now I have a rom on my phone so I can go back to the basics of flashing I hope, I am going to give it a try to see what happens
raziel26 said:
Does this mean if the sdk will not recognize that the device is connected then i have to make this JIG Thing? because my phone is stuck at the connect phone to pc screen.
Click to expand...
Click to collapse
No...being the noob that I am, I'm constantly finding new ways to brick my phone. So tonight, I bricked it with the phone to PC screen. ADB can't detect it and neither can odin. This is FIXABLE, I tried the method here:
http://forum.xda-developers.com/showthread.php?t=771247
Method 3 worked for me. Even if you have a hardware locked phone, I think there is a method around this which involves taking the battery out and putting it back in but I don't remember where I read this in the forums....I know I did read it though, you have to search to find it. Try these before you resort to making the JIG.
Sorry to sound incompetent, however i recently tried to install Honeycomb onto my G tab. In short i REALLY ****ed up.
I thought "No big deal i can just NVflash."
I've never had this happen before but the tablet just stays in the gtablet boot picture after the nvflash. Any advice? Thanks in advance
My website in signature. Code red. Read instructions!
hmm seems promising. However ive tried another package like this and had the same bootloop result. I'll post how it goes. Thanks
salzhao said:
hmm seems promising. However ive tried another package like this and had the same bootloop result. I'll post how it goes. Thanks
Click to expand...
Click to collapse
No, you haven't tried something like that. HC has a different data structure than everything else. You need to follow my code red to flash into and out of HC. Many people have skipped a step here and step there because they're not "dummies". I swear, if you don't follow my instructions right down to the letter, you're on your own. After a couple dozen people who aren't "dummies" deciding to skip a step here and a step there, I'm no longer giving personal support.
@Goodintentions
What if I was in the middle of an NVFlash Process and the USB plug came lose before it was able to finish?
Thats my situation as of current. I can't tell if the Unit is on or off..
I'm trying Code Red and Foward on your site.. But without knowing if the device is powered on or off I'm not having any luck with my PC recognizing the device..
APX drivers are properly installed as I have done NVFLash Before but this is first time the USB plug came loose during the process..
Suggestions??
Push the little white button inside the unit?
You can always hold the power button and vol - button. If after 2 minutes or so nothing happens then you know it was on and you just turned it off. Then turn it on in apx mode again. If it turns on it will go into apx mode. Try nvflash again. Correction. Try code detox.
goodintentions said:
You can always hold the power button and vol - button. If after 2 minutes or so nothing happens then you know it was on and you just turned it off. Then turn it on in apx mode again. If it turns on it will go into apx mode. Try nvflash again. Correction. Try code detox.
Click to expand...
Click to collapse
I got it going, NVFlash resulted in a bootloop but at the very least I can work with that and get into recovery!
Thanks dude!
I've just spent many hours trying to revive my AT&T I777 phone that was running CM9 until I tried to flash it back to bone stock GB, then ICS.
First, I used ODIN to flash the standard default UCKH7 Gingerbread ROM from Sammy via One-Click "I777_UCKH7_OCD_No_BL.7z". After performing the ODIN, the phone flashed successfully and rebooted into a boot loop "Rethink Possible".
I searched for hours to find a solution, but one solution lead to another problem, and so on...
Currently:
- I cannot get into recovery mode, but it boots reliably into download mode. Tried the 3 button tango in EVERY way, but it will only go into DL mode.
- I've tried many different ODIN flashable images per recommendation in this forum, even the one that contains all of the extra files (recommended by creepyncrawly). All flashed fine, but none fixed the boot loop issue.
- Most recommendations say to "wipe/factory reset" to fix the bootloop issue, but I can't do that since I can't get into recovery.
- Tried to do ADB REBOOT RECOVERY, but can't get the driver to connect and list the device. The install guide says to enter "debug mode", but I can't even boot the phone.
- Tried Kies and the phone was not recognized in either DL mode or boot loop. Was hopeful Kies could reinstate the firmware.
I have a physically PERFECT SGS2 I want to sell, and unless I can fix this boot issue, it's nothing but a brick now. Any advice is much appreciated! Pulling my hair out so far...
tone_la said:
I've just spent many hours trying to revive my AT&T I777 phone that was running CM9 until I tried to flash it back to bone stock GB, then ICS.
First, I used ODIN to flash the standard default UCKH7 Gingerbread ROM from Sammy via One-Click "I777_UCKH7_OCD_No_BL.7z". After performing the ODIN, the phone flashed successfully and rebooted into a boot loop "Rethink Possible".
I searched for hours to find a solution, but one solution lead to another problem, and so on...
Currently:
- I cannot get into recovery mode, but it boots reliably into download mode. Tried the 3 button tango in EVERY way, but it will only go into DL mode.
- I've tried many different ODIN flashable images per recommendation in this forum, even the one that contains all of the extra files (recommended by creepyncrawly). All flashed fine, but none fixed the boot loop issue.
- Most recommendations say to "wipe/factory reset" to fix the bootloop issue, but I can't do that since I can't get into recovery.
- Tried to do ADB REBOOT RECOVERY, but can't get the driver to connect and list the device. The install guide says to enter "debug mode", but I can't even boot the phone.
I have a physically PERFECT SGS2 I want to sell, and unless I can fix this boot issue, it's nothing but a brick now. Any advice is much appreciated! Pulling my hair out so far...
Click to expand...
Click to collapse
From powered off, how long are you holding power and vol+ and vol- to get into recovery? On both mine and my wife's phones, I have to hold all three down until the second time the Sammy logo flashes up on the screen. Most people seem to get it after the first time, but I've heard of a few others like mine...
Sent from my SGH-I777 using Tapatalk 2
dandrumheller said:
From powered off, how long are you holding power and vol+ and vol- to get into recovery? On both mine and my wife's phones, I have to hold all three down until the second time the Sammy logo flashes up on the screen. Most people seem to get it after the first time, but I've heard of a few others like mine...
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
When I hold down the 3 buttons, it never actually shows the Sammy logo. It takes about 8-12 seconds and shows the Download prompt that says "press volume up" to continue to enter DL mode; "press volume down" to cancel/restart. Both of these work fine. If I ignore the prompt and continue holding the 3 buttons, it never does anything else. Thanks for your post.
tone_la said:
When I hold down the 3 buttons, it never actually shows the Sammy logo. It takes about 8-12 seconds and shows the Download prompt that says "press volume up" to continue to enter DL mode; "press volume down" to cancel/restart. Both of these work fine. If I ignore the prompt and continue holding the 3 buttons, it never does anything else. Thanks for your post.
Click to expand...
Click to collapse
Unplug the USB when you do that
Sent from my Galaxy Nexus
Stop using brick. It turns on it is not a brick
Sent from my GS4 running CM11 Kandy Kane
Pirateghost said:
Unplug the USB when you do that
Click to expand...
Click to collapse
It does the same thing whether the USB cable is plugged in or not. However, you gave me an idea...
This phone has been sitting in the drawer for a few months since I got my GNex. When I charged it up, after unplugging the charger the icon stayed with a "plug" symbol on the notify bar as if it was still connected to the charger.
Is it possible the phone is stuck thinking there's a cable plugged in and that's why I can't 3-button boot to recovery? Seems like I've read about other people having connector issues. Does this sound plausible? And if so, what's the best remedy?
tone_la said:
It does the same thing whether the USB cable is plugged in or not. However, you gave me an idea...
This phone has been sitting in the drawer for a few months since I got my GNex. When I charged it up, after unplugging the charger the icon stayed with a "plug" symbol on the notify bar as if it was still connected to the charger.
Is it possible the phone is stuck thinking there's a cable plugged in and that's why I can't 3-button boot to recovery? Seems like I've read about other people having connector issues. Does this sound plausible? And if so, what's the best remedy?
Click to expand...
Click to collapse
A simple Google search is the best remedy. This is one of the most asked questions on this forum.
tone_la said:
It does the same thing whether the USB cable is plugged in or not. However, you gave me an idea...
This phone has been sitting in the drawer for a few months since I got my GNex. When I charged it up, after unplugging the charger the icon stayed with a "plug" symbol on the notify bar as if it was still connected to the charger.
Is it possible the phone is stuck thinking there's a cable plugged in and that's why I can't 3-button boot to recovery? Seems like I've read about other people having connector issues. Does this sound plausible? And if so, what's the best remedy?
Click to expand...
Click to collapse
Could be...Sounds like a symptom of bad or dirty usb port. Try cleaning gently with tooth brush and rubbing alcohol. Dry with canned air if you have some.
Sent from my SGH-I777 using Tapatalk 2
Phalanx7621 said:
A simple Google search is the best remedy. This is one of the most asked questions on this forum.
Click to expand...
Click to collapse
I've tried very hard to not "waste" anyone's time by doing my research, searching, and thinking; BEFORE posting. My question above is not so much "how" to clean the port, but "does this symptom I'm experiencing sound like a 'bad port' issue?". Believe me, I've done tons of searching to try to solve this problem before posting so that I can be worthy of receiving assistance.
And to the guy who says, "don't use the term brick". Sorry I said "Apparent brick"; just looking for some neighborly help to get my phone working again. At any rate, I very much appreciate any advice to help me get this fixed.
Trying hard to keep the forum clean and think for myself when possible!
dandrumheller said:
Could be...Sounds like a symptom of bad or dirty usb port. Try cleaning gently with tooth brush and rubbing alcohol. Dry with canned air if you have some.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Thanks so much for this post, I will do this and post again with the results. Much appreciated!
tone_la said:
Thanks so much for this post, I will do this and post again with the results. Much appreciated!
Click to expand...
Click to collapse
I should elaborate a little for safety's sake - probably a no brainer, but in case - TAKE YOUR BATTERY OUT BEFORE CLEANING THE PORT. Don't know if it matters or not, but I wouldn't want you to short stuff during cleaning - rubbing alcohol IS part water.
Adb wait-for-device reboot recovery
Plug in your phone and let it attempt to boot. If you need adb, use the link in my signature for adb portable. It includes batch files to reboot to download or recovery modes.
This issues the reboot command if at any point in the boot process your phone is detected.
You might want to install the android sdk and ensure you have the nexus drivers installed.
Sent from my SGH-I777 using xda premium
Red_81 said:
Adb wait-for-device reboot recovery
Plug in your phone and let it attempt to boot. If you need adb, use the link in my signature for adb portable. It includes batch files to reboot to download or recovery modes.
This issues the reboot command if at any point in the boot process your phone is detected.
You might want to install the android sdk and ensure you have the nexus drivers installed.
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Well, I cleaned the heck out of the USB port with rubbing alcohol and a toothbrush, followed by a thorough drying with compressed air. Yes, battery removed during the process; thanks for that! Unfortunately, same exact symptom. Only goes into DL mode and boot loop.
I'll now try your portable adb suggestion and see if I can get a connection.
Does anyone else have any thoughts on what may have gone wrong and/or anything I can flash via ODIN to fix the issue? Many thanks!
Installed your portable adb and followed your instructions. Ran the recovery_mode batch file and adb initialized (daemon not running, starting daemon...) followed by red text "Waiting for your device to be detected". I already installed the Android SDK yesterday and the following modules are installed: Android SDK Tools, Android SDK Platform-tools, and Google USB Driver
Powered on the phone and after a few seconds the "Rethink Possible" logo showed up and shortly thereafter, I heard the computer beep indicating it connected with the phone. Win7 device manager shows "SAMSUNG Mobile USB Modem" under the Modems category.
However, the portable ADB continues to show "Waiting for your device to be detected" and the boot loop continues. Did the same thing in DL mode, same result.
I reinstalled the Samsung I777 driver from Samsung's site. Going to reboot my PC now to see if that makes a difference.
Reboot did not help. Seems like the phone is not being identified as "Android Composite ADB Interface", and therefore ADB cannot see the phone. I've looked for other drivers, but no matter what I've tried, the SGS2 I777 shows as "SAMSUNG Mobile USB Modem" under the Modems category in Win7 Device Manger.
Any advice on ADB here? Doing the best I can, but keep running into stops. Thank you
tone_la said:
Reboot did not help. Seems like the phone is not being identified as "Android Composite ADB Interface", and therefore ADB cannot see the phone. I've looked for other drivers, but no matter what I've tried, the SGS2 I777 shows as "SAMSUNG Mobile USB Modem" under the Modems category in Win7 Device Manger.
Any advice on ADB here? Doing the best I can, but keep running into stops. Thank you
Click to expand...
Click to collapse
Try in Linux? Make yourself an ubuntu live CD and go from there? As long as you have the most current drivers, it should work in Win - unless the problem is a totally hosed USB port??
Tried these? http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-II-i777-USB-Driver-for-AT-T.shtml
dandrumheller said:
Try in Linux? Make yourself an ubuntu live CD and go from there? As long as you have the most current drivers, it should work in Win - unless the problem is a totally hosed USB port??
Click to expand...
Click to collapse
Why would it work better in Linux? I'm willing to try this, but fairly unfamiliar with Linux.
Phalanx7621 said:
Tried these? http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-II-i777-USB-Driver-for-AT-T.shtml
Click to expand...
Click to collapse
I used the Samsung drivers. Kinda leary of these drivers from softpedia. They download as SETUP.EXE and seem like inauthentic/spyware.
After many many hours of frustration and dead ends, I've finally recovered my phone! YAYYYYY!!!!!
Here's how I got it done...
- No matter what I flashed, I kept getting the boot loop. This was really throwing me for a "loop" when I thought I was flashing standard original Sammy full ROM with ODIN; yet that wasn't enough to recover the phone.
- Something was missing with the boot process, so I started looking for CWM that I could flash via ODIN. Most sites had the zip CWM file, but only a few had the TAR file. Finding a valid file proved more difficult than I thought with all the download sites that went offline for legal reasons. But I did find one!
http://www.mediafire.com/?bjhx33o4viz8tza
The above link is for file name: SGH-I777_ClockworkMod-Recovery_5.0.2.3.tar
- Once I installed the above via ODIN, all of a sudden ADB recognized the phone and I was able to run: ADB REBOOT RECOVERY
It's very possible that the 3-button recovery may have worked too, but when I saw the device show up on ADB, I didn't want to take the chance.
- The device then rebooted and entered RECOVERY mode! FINALLY!!!!
- I then did a factory reset / wipe and rebooted the phone. It came up just fine, NO MORE BOOT LOOP!
Thanks to those who replied to this thread. The responses helped me think hard about what was going wrong and ultimately I dug up a solution.
I just recently downloaded SlimBean 3.1 and was trying to upgrade to that from 3.0. So I did my usual procedure: wipe, clear cache, format /system. Then I proceeded to installing Slimbean 3.1, then the kernel (Semaphore_JB_2.6.5sv) and finally the gapps for SlimBean. But the boot animation was taking too long (>10 minutes), when it usually doesn't when I install a SlimBean ROM, so I pulled the battery and repeated the process. Now I realized that once in a while (about 10 seconds) it would give a small vibration and on occasion when I retried to install, it would give me a 'Whoop' sound (when that happens, it's about every ~5 minutes). Anyone know what the problem is so I can fix it? Thanks!
Did you try getting it to boot, then go back and flash kernel?
I've felt the vibrations but never any sound. Don't know why that would happen.
I am Jack's smirking revenge.
samsgun357 said:
Did you try getting it to boot, then go back and flash kernel?
I've felt the vibrations but never any sound. Don't know why that would happen.
I am Jack's smirking revenge.
Click to expand...
Click to collapse
Yeah I've tried getting it to boot many times.. I just tried flashing the Semaphore kernel over the ROM in CWM, no good. Still stuck at the SlimBean boot animation as always and there's still the vibrations every 10 or so seconds.
I'm trying to use Heimdall for the first time now to see if it can help solve my problem. I've just done the zadig thing, but now I'm not quite sure how to proceed, I don't know what to put in the Heimdall Firmware Package.
EDIT: S**t, I tried flashing a kernel via Heimdall, failed for some reason, and now it's bricked with the 'phone ! pc' icon, can't get into download mode with 3 button combo. I just keeps going back to the 'phone ! pc' icon, I think it might be hard bricked. Odin isn't reading my device. No luck with one click unbrick either...This is not my day..
Pull battery, connect USB then hold button combo while popping battery back in. (With Odin on obviously)
I am Jack's smirking revenge.
samsgun357 said:
Pull battery, connect USB then hold button combo while popping battery back in. (With Odin on obviously)
I am Jack's smirking revenge.
Click to expand...
Click to collapse
Thanks for the reply. I tried doing that, still a no-go. Popped battery out, removed sd card/sim, put usb in, held vol. up and down keys, popped battery in. It keeps going back to the 'phone ! pc' screen and Odin's still not reading my device. I really am afraid that this might be a hard brick rather than a soft brick..
You aren't hard bricked, if you were you'd see nothing. The goal now is to try and get DL mode.
Have you tried to run Odin even though it doesn't give com port? Don't know if that will work but try it.
Try only vol up or only vol down and see if that works.
I am Jack's smirking revenge.
^ what he said. Try the up button only after you plug in the USB.
Sent from my Galaxy Nexus using Tapatalk 2
tylerxian said:
Thanks for the reply. I tried doing that, still a no-go. Popped battery out, removed sd card/sim, put usb in, held vol. up and down keys, popped battery in. It keeps going back to the 'phone ! pc' screen and Odin's still not reading my device. I really am afraid that this might be a hard brick rather than a soft brick..
Click to expand...
Click to collapse
I had better success with this one - Pull out battery, wait 10 sec, reinsert. Connect USB to PC port. While holding vol up & down, connect USB to the phone.
Are you on Froyo or GB bootloader?
samsgun357 said:
You aren't hard bricked, if you were you'd see nothing. The goal now is to try and get DL mode.
Have you tried to run Odin even though it doesn't give com port? Don't know if that will work but try it.
Try only vol up or only vol down and see if that works.
I am Jack's smirking revenge.
Click to expand...
Click to collapse
I sure hope so.. I've tried inserted the stock eclair PDA in Odin, along with the s1_odin_20100512.pit file, clicked start and was presented with "<OSM> All threads completed. (succeed 0 / failed 0)". I think one of the reasons why Odin isn't recognizing my Vibrant is because of the drivers (even before the brick). I'm always presented with "The last USB device you connected to this computer malfunctioned, and Windows does not recognize it." The drivers I downloaded were the latest from Samsung's site.
I tried both, still went into the 'phone ! pc' screen. Also tried using USBDeview to uninstall the Samsung drivers, and then, as always, when I plug in the Vibrant, it gives me the message mentioned above where Windows doesn't recognize the device. It'll install some Unknown Device's drivers, which don't work. I thought it might have been the zadig thing I did for Heimdall, but I guess not.
ioancr said:
I had better success with this one - Pull out battery, wait 10 sec, reinsert. Connect USB to PC port. While holding vol up & down, connect USB to the phone.
Are you on Froyo or GB bootloader?
Click to expand...
Click to collapse
Just tried, still went into the 'phone ! pc' screen. I believe I'm on the GB bootloader, it's been a while since I flashed a bootloader so I'm not quite sure, but since I managed to install SlimBean 3.0 before(required the GB bootloader), I'm assuming it's that.
tylerxian said:
I tried both, still went into the 'phone ! pc' screen...
Just tried, still went into the 'phone ! pc' screen. I believe I'm on the GB bootloader, it's been a while since I flashed a bootloader so I'm not quite sure, but since I managed to install SlimBean 3.0 before(required the GB bootloader), I'm assuming it's that.
Click to expand...
Click to collapse
Then you changed also the way you get to download mode. Instead of pressing both vol up & down, use ONE only, the volume up button. Don't give up, you will have to retry many times to get there, your phone is still OK.
Have you tried the Heimdall One-Click package? It was the only one that saved me many times (and long time ago, fortunately).
ioancr said:
Then you changed also the way you get to download mode. Instead of pressing both vol up & down, use ONE only, the volume up button. Don't give up, you will have to retry many times to get there, your phone is still OK.
Have you tried the Heimdall One-Click package? It was the only one that saved me many times (and long time ago, fortunately).
Click to expand...
Click to collapse
I couldn't get only vol. up or down to work. I have the one-click packager downloaded, but I don't know what to do with it. From the start it says 'Select a Heimdall tar.gz for one-click".
Heimdall One-Click has everything built-in, it doesn't ask anything. Go get it here, the official thread http://forum.xda-developers.com/showthread.php?t=1278683
Make sure it shows "package designed for SGH-t959" when open.
ioancr said:
Heimdall One-Click has everything built-in, it doesn't ask anything. Go get it here, the official thread http://forum.xda-developers.com/showthread.php?t=1278683
Make sure it shows "package designed for SGH-t959" when open.
Click to expand...
Click to collapse
That was the same thread I got mine, however the download links didn't work anymore in the OP's post. So I got mine here: http://forum.xda-developers.com/showthread.php?t=1278683&page=6, first post of the sixth page.
tylerxian said:
That was the same thread I got mine, however the download links didn't work anymore in the OP's post. So I got mine here: http://forum.xda-developers.com/showthread.php?t=1278683&page=6, first post of the sixth page.
Click to expand...
Click to collapse
It's not the one I have. It should be 280 Mb at least. I'll try to upload it somewhere, now I'm busy, sorry.
ioancr said:
It's not the one I have. It should be 280 Mb at least. I'll try to upload it somewhere, now I'm busy, sorry.
Click to expand...
Click to collapse
Thanks, I'd really appreciate it if you did. Hopefully before Tuesday, if I can't get anything to work in getting the Vibrant to boot to download mode, I might just have to ship it over to mobiletechvideos or something to install the unbrickable mod. That's also when I get my usb jig, so if that doesn't work either I'll send it in.
Try this link
It's 198 Mb jar file.
ioancr said:
Try this link
It's 198 Mb jar file.
Click to expand...
Click to collapse
Thank you! Though, it's not recognizing the phone, still shows disconnected. Then again, it might be a problem with my computer drivers not seeing my device/installing incorrect drivers (i.e 'Unknown device' and 'Port Failed'. This will definitely prove useful if I do get it to go to download mode or for future problems, if I manage to get it fixed.
tylerxian said:
Thank you! Though, it's not recognizing the phone, still shows disconnected. Then again, it might be a problem with my computer drivers not seeing my device/installing incorrect drivers (i.e 'Unknown device' and 'Port Failed'. This will definitely prove useful if I do get it to go to download mode or for future problems, if I manage to get it fixed.
Click to expand...
Click to collapse
Try to uninstall the current USB drivers, reboot PC and then use Zadig from Heimdall suite (1.3 or 1.3.1) to install them. It perhaps will not recognize it as a phone, don't bother, it's enough to make it just visible to PC (check search all devices or something like that in preferences of Zadig).
ioancr said:
Try to uninstall the current USB drivers, reboot PC and then use Zadig from Heimdall suite (1.3 or 1.3.1) to install them. It perhaps will not recognize it as a phone, don't bother, it's enough to make it just visible to PC (check search all devices or something like that in preferences of Zadig).
Click to expand...
Click to collapse
I uninstalled all the drivers related to the Vibrant using USBDeview, like the blank unnamed driver and the 'Port reset' one, then rebooted. But it's still not visible as a device. I'll post a screenshot of this.
Here's what usually happens. If you take a look at the last line in USBDeview, that's usually what the Vibrant comes out to be, just a blank line with no description.
{Solved}I have an Azpen A727 i bought from MicroCenter that I bricked.
I found out the solution to unbrick the tablet. First you need the firmware for the version of Android your A727 came with (Jelly Bean or KitKat) which i will provide the links for or you can request from Azpen (which i did and got a response for in 30min), 2nd you need a flashing tool called PheonixUSBPro and a "key" to flash your firmware on the bricked tablet.
1. Follow the instructions on this page for flashing firmware and downloading PhoenixUSBPro here http://www.azpenpc.com/download/detail.php/id-2.html or use the Backup here https://drive.google.com/folderview...JrLUZEYTFjOVF2ajJISy1pdkVCSTgzVlk&usp=sharing
2. a. Firmware and "Key" for A727 Jelly Bean https://drive.google.com/folderview?id=0B53yZ1fbVqxJVnNFSkY2cjFoRjQ&usp=sharing
b. Firmware and "Key" for A727 KitKat (For some reason we have two different versions. If one doesn't work try the other)https://drive.google.com/folderview?id=0B53yZ1fbVqxJZGx2SDVPcWhsWmM&usp=sharing
Note: If anyone is having trouble with PhoenixUSBPro detecting your tablet try holding down the power button and plugging in your tablet from the micro-USB side then press the power button 10 times. Then Windows should be installing the driver so PhoenixUSBPro should detect it now. It worked for me in Windows 7.
If anyone has any problems let me know . Thank you @viper2110 for providing the community with the KitKat firmware.
bricked as well
Were you able to get the device working again?
I bricked mine messing with it today and am trying to fix it.
Have the stock recovery so far if you still need it let me know. xda wont let me attach for some reason
buellonsholes said:
Were you able to get the device working again?
I bricked mine messing with it today and am trying to fix it.
Have the stock recovery so far if you still need it let me know. xda wont let me attach for some reason
Click to expand...
Click to collapse
Yep i fixed it. I edited the first post with the solution
thank you
treecheetahdolo said:
Yep i fixed it. I edited the first post with the solution
Click to expand...
Click to collapse
still trying to figure out adb, livesuit, and eclipse all at once but here we go.
nothing like jumping in and just figuring out whats what lol
no luck
treecheetahdolo said:
{Solved}I have an Azpen A727 i bought from MicroCenter that the camera wasnt working so i decided to install a custom ROM on it instead of bringing back to the store. I was able to root it. But once I flashed a custom ClockWorldMod from http://forum.xda-developers.com/showthread.php?t=2532464 i was bricked.
I found out the solution to unbrick the tablet. First you need the firmware which i will provide the link for or you can request from Azpen (which i did and got a response for in 30min), 2nd you need a flashing tool called PheonixUSBPro and a "key" to flash your firmware on the bricked tablet.
1. Follow the instructions on this page for flashing firmware and downloading PhoenixUSBPro http://www.azpenpc.com/download/detail.php/id-2.html
2. Firmware and "Key" https://drive.google.com/folderview?id=0B53yZ1fbVqxJVnNFSkY2cjFoRjQ&usp=sharing
If anyone has any problems let me know
.
Click to expand...
Click to collapse
Can 't figure out why but after trying many times phoenixpro fails me (trying to use key but red button and green button both arent there)
livesuit wont run either unsure why
only thing i have up and running is sdk manager and im working on learning the steps with it
anyone who can help it would be appreciated. using a windows 8
Very important:
Originally Posted by dsulliii View Post
1) Make sure your A700 is turned off. (Do NOT have the micro-USB end plugged into your A700 at this time, that is for later.)
2) Start LiveSuit on your computer. (The COMPUTER end of your USB cable should be plugged into ONLY your computer at this stage.)
3) Select the ROM that you want to flash to your A700.
4) Hold down the Vol button on your device (I usually hold it down Vol-, not Vol+, but I believe that this device does not matter which.)
5) While holding down Vol, plug the micro-USB end of the cable into your A700. Keep holding down the Vol button.
6) While still holding down the Vol button, WITH the USB cable now connected between your computer and your A700, press and release the A700's Power button 10 times, and wait for a second to a few.
7) The LiveSuit program will detect your A700 going into download mode and begin prompting you for what to do.
8) Follow LiveSuit's recommendations, including formatting. It will take less than 5 minutes.
This wasn't clear to me from the original post.
However I followed the original link and figured it out.
Hope that clears it up for anyone else.
.....
WarezAppz said:
Very important:
Originally Posted by dsulliii View Post
1) Make sure your A700 is turned off. (Do NOT have the micro-USB end plugged into your A700 at this time, that is for later.)
2) Start LiveSuit on your computer. (The COMPUTER end of your USB cable should be plugged into ONLY your computer at this stage.)
3) Select the ROM that you want to flash to your A700.
4) Hold down the Vol button on your device (I usually hold it down Vol-, not Vol+, but I believe that this device does not matter which.)
5) While holding down Vol, plug the micro-USB end of the cable into your A700. Keep holding down the Vol button.
6) While still holding down the Vol button, WITH the USB cable now connected between your computer and your A700, press and release the A700's Power button 10 times, and wait for a second to a few.
7) The LiveSuit program will detect your A700 going into download mode and begin prompting you for what to do.
8) Follow LiveSuit's recommendations, including formatting. It will take less than 5 minutes.
This wasn't clear to me from the original post.
However I followed the original link and figured it out.
Hope that clears it up for anyone else.
Click to expand...
Click to collapse
i'm feeling really dumb here i read that too and am pretty sure i have gotten it into this mode. but its the livesuit software thats the problem i cant get that or the other ones i mentioned to even run. anything i do get to run (phoenix and sdk) dont seem to run correctly. windows 8 is annoying me this week. im trying to get one of my old windows 7 computers up and running and ill try again i guess
WarezAppz said:
Very important:
Originally Posted by dsulliii View Post
1) Make sure your A700 is turned off. (Do NOT have the micro-USB end plugged into your A700 at this time, that is for later.)
2) Start LiveSuit on your computer. (The COMPUTER end of your USB cable should be plugged into ONLY your computer at this stage.)
3) Select the ROM that you want to flash to your A700.
4) Hold down the Vol button on your device (I usually hold it down Vol-, not Vol+, but I believe that this device does not matter which.)
5) While holding down Vol, plug the micro-USB end of the cable into your A700. Keep holding down the Vol button.
6) While still holding down the Vol button, WITH the USB cable now connected between your computer and your A700, press and release the A700's Power button 10 times, and wait for a second to a few.
7) The LiveSuit program will detect your A700 going into download mode and begin prompting you for what to do.
8) Follow LiveSuit's recommendations, including formatting. It will take less than 5 minutes.
This wasn't clear to me from the original post.
However I followed the original link and figured it out.
Hope that clears it up for anyone else.
Click to expand...
Click to collapse
Im pretty sure LiveSuit wont work on the A727 because the CPU is different. The A727 uses an Allwinner thats why we have to use PhoenixUSBPro. Sorry for my late response I dont have internet anymore so I got lucky today getting online, lol.
treecheetahdolo said:
Im pretty sure LiveSuit wont work on the A727 because the CPU is different. The A727 uses an Allwinner thats why we have to use PhoenixUSBPro. Sorry for my late response I dont have internet anymore so I got lucky today getting online, lol.
Click to expand...
Click to collapse
Yeah, sorry I was using PhoenixUSBPro, guilty of not mentioning that.
Anyone else have any luck unbricking the A727 with this method?
Look what I ran across
SDK for Allwinner CPUs?
Now will this aid in someone creating a Android 4.4 image for an Azpen a1023 or at least a custom CWM or TWRP? for one?
answer soon back.
WarezAppz said:
SDK for Allwinner CPUs?
Now will this aid in someone creating a Android 4.4 image for an Azpen a1023 or at least a custom CWM or TWRP? for one?
answer soon back.
Click to expand...
Click to collapse
I dont know but BLuFeNiX started this thread where he did a CWM for an A700 http://forum.xda-developers.com/showthread.php?t=2532464
treecheetahdolo said:
I dont know but BLuFeNiX started this thread where he did a CWM for an A700 http://forum.xda-developers.com/showthread.php?t=2532464
Click to expand...
Click to collapse
Yeah I was aware of that, but that's for an A700
and I am actually interested in A1023, not sure the A700 will work for the A1023
Question. Frozen after reimage.
Hi all! I was able to reimage my A727 with PhoenixUSBPro and the firmware and key linked in the OP, but when it reboots and comes up to the initial screen, it's frozen. Won't take any input. The only thing I can do is force a shutdown with the power button. Am I doing something wrong? Thanks.
TMBackstrom said:
Hi all! I was able to reimage my A727 with PhoenixUSBPro and the firmware and key linked in the OP, but when it reboots and comes up to the initial screen, it's frozen. Won't take any input. The only thing I can do is force a shutdown with the power button. Am I doing something wrong? Thanks.
Click to expand...
Click to collapse
I dont know. Have you tried pressing the reset button?
treecheetahdolo said:
I dont know. Have you tried pressing the reset button?
Click to expand...
Click to collapse
Yup, tried the reset button and resetting back to factory. Still frozen.
I just redownloaded everything from the OP onto a Win 7 Pro x86, instead of on my Win 7 Ultimate x64 system, ran the upload, and it is working fine now. Thanks for all the help. :good:
TMBackstrom said:
I just redownloaded everything from the OP onto a Win 7 Pro x86, instead of on my Win 7 Ultimate x64 system, ran the upload, and it is working fine now. Thanks for all the help. :good:
Click to expand...
Click to collapse
Wow interesting. Im surprised it made a difference. Im glad you have everything up and running now
treecheetahdolo said:
{Solved}I have an Azpen A727 i bought from MicroCenter that I bricked.
I found out the solution to unbrick the tablet. First you need the firmware which i will provide the link for or you can request from Azpen (which i did and got a response for in 30min), 2nd you need a flashing tool called PheonixUSBPro and a "key" to flash your firmware on the bricked tablet.
1. Follow the instructions on this page for flashing firmware and downloading PhoenixUSBPro
2. Firmware and "Key"
If anyone has any problems let me know
Click to expand...
Click to collapse
I also have an azpen tablet that comes up with the azpen logo when switching it on and it just stays there.
I did try your solution above but does not work. The device does not seem to be picked up in PhoenixUSBPro.
In windows device manager it did pick up the device as "USB Developer". I instlled the Google drives and now it shows as "Android Composite ADB Interface". But PhoenixUSBPro still does nit pick it up.
Any ideas what else I can try.
viper2110 said:
I also have an azpen tablet that comes up with the azpen logo when switching it on and it just stays there.
I did try your solution above but does not work. The device does not seem to be picked up in PhoenixUSBPro.
In windows device manager it did pick up the device as "USB Developer". I instlled the Google drives and now it shows as "Android Composite ADB Interface". But PhoenixUSBPro still does nit pick it up.
Any ideas what else I can try.
Click to expand...
Click to collapse
Are you holding down the power button and volume down button while plugging in your tablet like Azpen said?