I have a TF201 that I don't know the history on. It turns on to gears and a red triangle exclamation. The weird thing is if I tilt it, half of the screen shows android start and setup.
I figured I could find the stock rom and flash it using MicroSD, however looking everywhere I can't find a true stock rom. I can find stock roms that are modified to unlocked devices, but not true stock.
When I try to do a wipe, it says 9.4.2.7 at the top I noticed. I don't know if that helps.
Suggestions?
EDIT:
Good source for firmware
http://forum.xda-developers.com/showthread.php?t=1429873
So I found them on ASUS's site. I had no idea they were under Android on there.
However, I can't get adb to find a device on the computer because I only have two icons holding volume and power (Wipe Data, Android).
If I put a SDcard in the tablet like on a TF300T and go into RCK, it doesn't work. Android goes belly up with red triangle. Is it the name i'm using? I tried update.zip, the stock firmware name, and EP201_768_SDUPDATE like I use on the TF300T.
Also, when it's hooked up and I type fastboot device, all I get is waiting for device.
I don't know if this is because it needs to be in a debug USB mode, but I can't get there to check. It does recognize the tab on the computer when I plug it in though.
Ok, so I fixed it.
I downloaded US_epaduser9_4_2_7Updatelauncher.zip
I then put it on a MicroSD card formatted Fat32 and renamed it EP201_SDUPDATE
Then I put it in the tablet and held volume down and power until it prompted to go into RCK and no more dead android, it took and loaded.
EDIT:
DIDN'T WORK (
It loaded like it was going to work, but I am back to the gears and the red triangle.
FUUUUU.JPG
haha, I feel like I am in here by myself. However, I want to document all of this in case somebody else runs into the problem I ran into and they're a rook too.
I fixed it. I wasn't sure what ROM was originally on it and when holding volume and power I noticed the 9.4.2.7 so I assumed that was it. However, I tried that ROM and it seemed like it was going to work but kicked the gear and triangle.
I then figured what the heck and tried the newest rom I could find. The 10.4.2.18?? I think it was. Whatever is the newest on the link I put in the first post.
It ran, and rebooted and Wahla, worked.
It's important to note my directions of FAT32 and the EP201_SDUPDATE as it took me a while to realize those had to be in place properly for the MicroSD card update to work.
Related
I received a G Tablet which had been used for development work for a few months. The person giving it to me (not the dev who has left) said the tablet was working fine, but had just become frozen at a reboot after he had tried to erase personal data from the tablet. I asked him if he had erased the sd card and he said "maybe" but that he couldn't remember. I powered the tablet on and sure enough it displayed two lines on a black background, one of which said something like loading kernel.
Now, these tablets were all rooted, and had Android 2.3 on them, via one of the ROMs discussed here. I don't know which one however.
So, I tried using NVflash to flash the tablet back to a stock ROM. Tablet then got stuck in a boot loop; I would see the Viewsonic logo, then the G Tablet logo, and then this would go on forever.
So I shut it down and tried again. This time Nvflash failed almost at the last step after having written most of the image.
And so here I am now, with a totally dead tablet. I cannot power it on. No combination of power or volume up/down buttons work. The only sign of life is when I plug it into its charger, and see the charging light come on.
I confirmed again with the person who gave me the tablet that the device was working just fine before it froze at a reboot after his erasing attempts.
Is there a way out of this? I hope so. Please help!
Thanks very much
Paul
texnote said:
I received a G Tablet which had been used for development work for a few months. The person giving it to me (not the dev who has left) said the tablet was working fine, but had just become frozen at a reboot after he had tried to erase personal data from the tablet. I asked him if he had erased the sd card and he said "maybe" but that he couldn't remember. I powered the tablet on and sure enough it displayed two lines on a black background, one of which said something like loading kernel.
Now, these tablets were all rooted, and had Android 2.3 on them, via one of the ROMs discussed here. I don't know which one however.
So, I tried using NVflash to flash the tablet back to a stock ROM. Tablet then got stuck in a boot loop; I would see the Viewsonic logo, then the G Tablet logo, and then this would go on forever.
So I shut it down and tried again. This time Nvflash failed almost at the last step after having written most of the image.
And so here I am now, with a totally dead tablet. I cannot power it on. No combination of power or volume up/down buttons work. The only sign of life is when I plug it into its charger, and see the charging light come on.
I confirmed again with the person who gave me the tablet that the device was working just fine before it froze at a reboot after his erasing attempts.
Is there a way out of this? I hope so. Please help!
Thanks very much
Paul
Click to expand...
Click to collapse
I would try popping it open and unplugging the internal battery then plugging it back in. Also hit the internal reset button while you're in there. It's pretty hard to actually kill one of these tablets. PM me if you need any other help.
help
Started my own thread, didnt mean to hijack. =)
Thanks, I will try removing the battery and let you know.
As for NVflash, I believe the latest version is here:
http://www.slatedroid.com/topic/171...-using-either-11-or-12-based-images-g-tablet/
However in my case I have no idea whether I have 1.1 or 1.2 and there is no way to determine this. Which one should I choose?
Paul
Doesn't matter for NVFlash, just download all of the flash files again because it might be that you have a bad download. Also make sure you have the right drivers installed since the drivers that automatically install when you plug it in sometimes don't work.
I'm pretty sure that if it boots past the birds, the hardware is working okay, so you should run the FORMAT version for NVFlash and then I'd run just a CWM flash setup and see if you can get into CWM and delete the partitions from within that.
The best thing to flash as far as ROMs would be Bekit's 1105 which is stock OTB with a few key changes. If you can't get the 1105 to play nice, you might really have some hardware problems.
I would go with the 1.2 BL, it will give you access to the newer roms as it appears that dev for the 1.1 BL seems to be dwindeling. I upgraded mine to 1.2 the other day and it worked great.
So, heres my problem. I have 2 samsung fascinates. I screwed one up a while back and was able to pull it back together and get it into ICS on CM9 with all the proper files using Odin.
I recently got a second samsung fascinate and was attempting to flash the same files, through Odin, but was having trouble.
I was able to get CWR (I believe it was voodoo) onto the phone, but once in recovery mode and having cleared all cache's, wiped files, and factory reset, I still could not successfully instal the files from the SD card (the same ones that worked on the 1st fascinate)
SO
I downloaded another version (or so I thought), Pushed it through Odin, Odin said it passed and auto restarts the phone. The phone never comes back on.
In hindsight think that CWR somehow ended up being deleted from the phone (if thats possible without doing it on purpose) before what was pushed by Odin was actually pushed. The file might have been wrong, im not sure, I will post up the exact file name when I get home.
At this point, the phone is completely unresponsive,. No holding the volume, plugging it in, putting the battery in. Jig doesnt work, Heimdall Doesnt work, Fastboot doesnt work. No download mode, period. No lights, no vibration. Tried multiple batteries, tried assuming the screen was bad, tried multiple cables, tried plugging into wall and computer. Nothing.
Mac will not notice the device at all once its plugged in, however, PC notices and starts to wig out. I have to hold the power button down, while its plugged into the computer to allow for it to search for drivers
The driver is SEC S5PC110 TEST B/D notification.....I feel like this is for a phone other than the fascinate.
Either way, I try to download fascinate drives, or the driver its calling for, both being unresponsive.
Am I completely screwed? Or is the questions more that I found myself at the point the I have either deleted what was deemed "Un-deleteable" or do I need to take the board out and get a soldering iron?
Also, I know a developer, I have taken it to him and he looked at it and scratched his head......hopefully someone has some sort of solution. Thanks
What file did you try to flash?
I9100_APBOOT_I9100XXKP2_CL17109_REV02_eng_mid_ship.tar
This was the file I flashed. Again, in hindsight and based on what I was reading in the forum, it looked good. I have no idea what it actually is, and therfore should not have flashed it. But I was in read and repeat mode, so I didnt question much. If I can track down the exact thread I was in I will post it up as well.
Philveatch said:
I9100_APBOOT_I9100XXKP2_CL17109_REV02_eng_mid_ship.tar
This was the file I flashed. Again, in hindsight and based on what I was reading in the forum, it looked good. I have no idea what it actually is, and therfore should not have flashed it. But I was in read and repeat mode, so I didnt question much. If I can track down the exact thread I was in I will post it up as well.
Click to expand...
Click to collapse
thats what happens when you flash files for another
device to this one. there is a guide in the general section that has everything you needed. hopefully next time you do a bit more research before you get flash happy. at this point unbrickable mod is your only way out and that requires some microscopic soldering skills.
It looks like you flashed a bootloader for the Galaxy S2.
Interesting. It was in a fascinate forum talking about how to add ics to a fascinate phone.....hmm.
Hey guys, I'm really hoping someone can tell me of a solution Ive not though of.... So Ive got the note 3 from sprint. currently had 4.4.4. I shoulda just left wellenough alone, I realize, But I tried to flash just a modem via mobileOdin and upon reboot, it will say "recoverybooting" and then I get the blue android. Thats all. This was just over 6 hours ago I did this and Im dead in the water, Ive SEARCHED the internet high and low and there are other facing similar problems, but it seems like every mishap Ive read about EVENTUALLY gets fixed. This just will not do anthing with any button combo as far as recovery and/or download mode. I cant access download mode either. recovery never actually boots, just a forever frozen blue android.. Now, with the phone attached via usb to my PC, it DOES see it as COM7, BUT REGARDLESS what ive tried it just remains at the "recovery booting" spot then blue android until I pull the battery again. Please HELP.! IF ANYONE HAS ANY SUGGESTIONS I would be just delighted if you may have some other approaches to this matter. THANKS! Please let me know iTs DESPERATE!
Zscott87 said:
Hey guys, I'm really hoping someone can tell me of a solution Ive not though of.... So Ive got the note 3 from sprint. currently had 4.4.4. I shoulda just left wellenough alone, I realize, But I tried to flash just a modem via mobileOdin and upon reboot, it will say "recoverybooting" and then I get the blue android. Thats all. This was just over 6 hours ago I did this and Im dead in the water, Ive SEARCHED the internet high and low and there are other facing similar problems, but it seems like every mishap Ive read about EVENTUALLY gets fixed. This just will not do anthing with any button combo as far as recovery and/or download mode. I cant access download mode either. recovery never actually boots, just a forever frozen blue android.. Now, with the phone attached via usb to my PC, it DOES see it as COM7, BUT REGARDLESS what ive tried it just remains at the "recovery booting" spot then blue android until I pull the battery again. Please HELP.! IF ANYONE HAS ANY SUGGESTIONS I would be just delighted if you may have some other approaches to this matter. THANKS! Please let me know iTs DESPERATE![/QUOTE
Have you tried removing the battery for a couple of minutes ? If you have read a couple of my threads on NH7 4.4.4, once your there downgrading anything is risky. Here is a link to read http://forum.xda-developers.com/note-3-sprint/help/4-4-4-download-mode-t2877528 . Here is a link for a recovery from a hard brick, by creating a boot image and then copy and paste it on a sdcard http://www.rom-central.com/showthread.php?87-GUIDE-HOWTO-Recover-from-a-HARD-BRICK-N900V-NC2-NC4 there are several sites on this type of fix, I just can't remember where they are. However, I do have something that may help, on one of those sites there was a link for someone who has already created a SM-N900P Unbrick img for Sprint and I downloaded it just in case. Here is the link http://www.mediafire.com/download/l6q1152x5c9d4h6/N900PUnbrick my copy. From what I understand you need to format/erase your sd card then copy and paste the unbrick img to the sd card from a PC. Pull the battery and install the sdcard back in the device, then try and boot the phone into download mode. Here is another link http://forum.xda-developers.com/showthread.php?t=2439367 I have not had to do this so you will have to do a little reading to be sure.
Click to expand...
Click to collapse
The fact that it still shows up as COM is a good sign.
Get a hold of ODIN 3.07+ I had issues with ODIN 3.06.
Here are a few things to try:
1.Take the battery out and hold all the buttons that you normally would to boot into recovery. While holding all the buttons, plug in the usb cable. If it boots into download mode, awesome, just put the battery in before you flash.
2. .Take the battery out and hold all the buttons that you normally would to boot into recovery. While holding all the buttons, plug in the battery. Hopefully it will boot into download mode.
3. try different cables, remember regular micro usb cables work with the note 3.
Make sure you put the modem file in the phone slot, and the rom/system tar in the pda slot.
Best of luck
Thanks for the suggestions guys! Iguess time is just what it needed. I actually fell asleep after trying for so long, and when I woke up I decided to try once more and VOILA... It let me into download mode! Went back to stock and have since been rebuilding . ha! Thanks again
Welp,
I've gone & done it again. My 2nd z3v came from Amazon a few days ago, refurbished, like new. Got the 200GB card for it, went to Verizon & got the SIM, swapped it with my work phone (iPhone 4s) line.
(Now I have 2. But the 1st one was replaced for being in this same situation.)
Got home, swapped the phones back cause I really still wasn't sure I wanted to mess up this z3v with my job (landscaping = lots of dirt).
It had 4.4.4, and I let it update to the latest two part Lollipop to see what the hubbub was about (nothing).
Decided I wanted to make it basically a clone of my primary z3v, so I rooted from the update directly using GigaSPXs guide.
Successful rooted 509 achieved, but with one problem; it kept telling me I had no space left, even though the internal SD had 21 GB left. Peculiar.
Made a recovery file on my #1 z3v's SD. Copied everything from #1 SD to #2 SD, and attempted to "clone" #2 z3v by installing that latest zip copied from z3v #1, but Recovery kept saying "No File Found".
Checked all 5 recovery points I had on there, and each said the same thing. Checked other things on the SD card, and it showed them, but when I tried to open them, it said "No File Found".
Mounting problem? Made sure everything was mounted, etc. Still, same problem.
Tried wiping Dalvik 3 times, but also accidentally wiped System Cache.
Now it sticks at the SONY Xperia logo. I can get to the Sony Recovery options, but Factory Reset doesn't do anything.
Was it System Cache wipe that killed it, and can anything be done?
This time, I took some notes as I went. I was confident, but I've done this before (bricked), so I decided to list what I did as I went along. I highly recommend everyone take notes for when they screw up. LOL!
AddictedToGlass said:
Welp,
I've gone & done it again. My 2nd z3v came from Amazon a few days ago, refurbished, like new. Got the 200GB card for it, went to Verizon & got the SIM, swapped it with my work phone (iPhone 4s) line.
(Now I have 2. But the 1st one was replaced for being in this same situation.)
Got home, swapped the phones back cause I really still wasn't sure I wanted to mess up this z3v with my job (landscaping = lots of dirt).
It had 4.4.4, and I let it update to the latest two part Lollipop to see what the hubbub was about (nothing).
Decided I wanted to make it basically a clone of my primary z3v, so I rooted from the update directly using GigaSPXs guide.
Successful rooted 509 achieved, but with one problem; it kept telling me I had no space left, even though the internal SD had 21 GB left. Peculiar.
Made a recovery file on my #1 z3v's SD. Copied everything from #1 SD to #2 SD, and attempted to "clone" #2 z3v by installing that latest zip copied from z3v #1, but Recovery kept saying "No File Found".
Checked all 5 recovery points I had on there, and each said the same thing. Checked other things on the SD card, and it showed them, but when I tried to open them, it said "No File Found".
Mounting problem? Made sure everything was mounted, etc. Still, same problem.
Tried wiping Dalvik 3 times, but also accidentally wiped System Cache.
Now it sticks at the SONY Xperia logo. I can get to the Sony Recovery options, but Factory Reset doesn't do anything.
Was it System Cache wipe that killed it, and can anything be done?
This time, I took some notes as I went. I was confident, but I've done this before (bricked), so I decided to list what I did as I went along. I highly recommend everyone take notes for when they screw up. LOL!
Click to expand...
Click to collapse
Use Flashtool to flash it back to 4.4.4. After that, don't try to do your attempt again. They're two separate devices and they are both uniquely different internally.
OK, how do I use flashtool? The PC doesn't recognize the phone as anything hooked up to it. Flashtool doesn't recognize it's there.
AddictedToGlass said:
OK, how do I use flashtool? The PC doesn't recognize the phone as anything hooked up to it. Flashtool doesn't recognize it's there.
Click to expand...
Click to collapse
IIRC, hold down the down (or up) button and hook the phone to the computer. I think it should trigger recognition from there.
GigaSPX said:
IIRC, hold down the down (or up) button and hook the phone to the computer. I think it should trigger recognition from there.
Click to expand...
Click to collapse
If that doesn't work and you have connected your phone to your computer before try removing all related Sony drivers from the computer. If you are OK with registry edits you could look for any instances of your phone there too.
Komet1 said:
If that doesn't work and you have connected your phone to your computer before try removing all related Sony drivers from the computer. If you are OK with registry edits you could look for any instances of your phone there too.
Click to expand...
Click to collapse
Don't I need the drivers installed?
Yes,, reinstall them preferably from outside your computer. You are wanting the drivers on your computer to be overwritten by fresh drivers, even if they have the same version numbers. You want the computer to "think" this is the first time the phone has ever been connected to it.
Where do I get th drivers for re-installation?
AddictedToGlass said:
Where do I get th drivers for re-installation?
Click to expand...
Click to collapse
Try this. If you do take this route don't be discouraged if it doesn't work the first time. I have had something similar happen and on occasion it has taken a few tries. Windows doesn't like to let go of drivers that are already installed.
Xperia Z3 drivers
"Phone driver for Xperia Z3 (D6603, D6616, D6653, D6643, SOL26, D6708, SO-01G, and 401SO) (Microsoft Windows™ XP 32bit/64bit and later). Use drivers for debugging, or when erased from phone."
DLed the replacement drivers, but Flashtool isn't recognizing the z3v. I know I'm doing something wrong because it isn't recognizing my other (functioning) z3v, either.
So I Googled driver installation on Windows 8.1 because I remembered that it won't allow unsigned drivers without manual installation, and I needed a refresher course for all the steps. I am uncertain I successfully removed all of the previous ones, though. What I did find out, but did not know, was that putting 8.1 into that mode (where it'll install unsigned drivers) is a temporary situation. According to a poster on a blog (for whatever that's worth...), once the PC is restarted, it comes out of that "test mode", and unsigned drivers no longer work again. I usually keep the PC on, but it has restarted since I last messed with Flashtool.
Obviously I need to figure out where I'm going wrong on this to even begin work on the phone. (I miss XP.)
Details about the z3v behavior:
The screen is stuck on the SONY XPERIA logo.
Pressing the power button by itself has no effect, no matter how long I hold it.
Pressing the power button with the volume down will power it off, but it just powers back on by itself.
Pressing the power button and holding both the power button and the volume down while it cycles back on gets me into the Android Recovery menu.
From Recovery;
Selecting "Power Down" USUALLY powers it down, but sometimes it immediately restarts.
Selecting "Factory Reset" cycles it through the logo and into an attempt (Droid animation with blue bar rolling) for about 5-6 seconds, and then it restarts into the SONY XPERIA logo again.
Selecting "Safe Mode" simply restarts it the same way.
Selecting "Continue Power Up" obviously does the same.
All that is while not tethered to the PC. NO color LED comes on, except for an occasional orange while it's hooked to the PC.
Got a couple of suggestions about the PC connection:
Try a different USB cable.
Have you looked in Device Manager and removed any reference to the Sony there as well?
Here is a blog post about an Xperia S that wouldn't connect, the steps should be the same:
Connect the phone via USB and go to the Device manager on the computer. Check if you can locate the phone or any Unknown/New device that could be the phone or if you perhaps see the phone as a device. Right click it and select to uninstall.
Still in Device manager open the list for USB controllers (Universal Serial Bus Controllers) and right click each one of these controllers and select to uninstall.
When all of this is done reboot your computer and before connecting your phone again repeat step 2.
You should of course not have to do this every time you connect your phone to your computer but hopefully this could remove any error causing your phone not to connect properly.
I'M BACK!!!
And here's a lesson from one noob to all others; Never overlook the simplest things.
Komet1, your suggestion of trying a different cable struck me as desperate, but when I looked at what I had been using, I realized it was the cheap cable Amazon sent with the phone (It didn't come with a Sony charger and cable, just a crappy generic set).
I swapped cables and viola!, I now have 4.4.4 back.
I'll not be making the stupid mistake of swapping restores from one phone to another again.
Thanks all!
Important lessons for beginners...
Take notes. I'm glad I did this time because last time I bricked I couldn't remember what I had done to brick it, or what I had tried to unbrick it. It helps when you can provide detailed info, otherwise it becomes too frustrating for those who can help. It can also help keep you from panicking and going in circles.
AddictedToGlass said:
I'M BACK!!!
And here's a lesson from one noob to all others; Never overlook the simplest things...
Thanks all!
Important lessons for beginners...
Take notes. I'm glad I did this time because last time I bricked I couldn't remember what I had done to brick it, or what I had tried to unbrick it. It helps when you can provide detailed info, otherwise it becomes too frustrating for those who can help. It can also help keep you from panicking and going in circles.
Click to expand...
Click to collapse
Awesome! Been there, done that with the bricking. It's a wonderful feeling when you watch the phone respond and realize you just solved the problem.
Sure is!
DOH!!!!
Hi everybody,
Got directed to this site for being my best chance of getting my Tab 3 10.1 (GT-P5210) back up and running. Worked on plenty of computers but haven't done much in the way of tablets.
The issue I'm having goes like this:
-When connected to a charger I get the battery icon with the circle. It does not reflect that it is charging. I have gotten a new battery for it and it still does the same thing.
-When the tablet is powered on it gets as far as the Samsung Galaxy Tab 3 10.1 screen.
-I went into the recovery menu (volume up & power) and did a factory reset on it. The background shows the Android laying down with No Command underneath and then shows Error!
-Downloaded the recovery firmware (I believe that's what it is) from Sammobile. 2.28 GB file unzipped, titled P5210XXUBNK2_P5210XACBNK2_Home.tar.md5. Copied it to a microSD card and tried the update from external option. Basically got the same result as before.
-It was suggested that I root the device, so I downloaded Odin and used TWRP (I think I got the right one). It did it's thing and restarted but I'm still no further ahead.
Is there another step I should be taking? Or other files I should be using?
I haven't found and clear tutorials on this so far, a lot of the ones I've come across have links to other forums that are about as clear as mud or have dead links.
My goal is just to have a functioning tablet at the end that works basically the way it did when I first got it.
Thanks in advance!
Quiet bunch