A few years back I purchased a Flytouch II / Superpad. Installed several custom roms and had no issues. It sat in my parts box for a while and I figured I drag it out and see what I could use it for.
Initially it booted fine (running Tim6...I think) once it was up and running it started lagging and would not respond (Screen got too hot and it stopped seeing my touches)
One of the icons on the screen was a shutdown script pre-loaded. Apparently it had pressed this, the script popped up and I tried to hit close before it shutdown, The script closed and after a little more playing I shut it off by holding the power button down, then sliding the power off slider that came up.
The next day I went to power it up and it just freezes on the android logo screen. No bootanimation, nothing.
Since I'm not shy about taking stuff apart it carefully took it apart and removed the internal sd card (4gb) and made a backup of it using dd. I then loaded an sdcard v4 image I found online, it still just hangs at the green android screen.
Also tried several "brick fixes" here on xda.
If I boot it without an sdcard it says "No Card in Machine!!!" so I think the systems is ok hardware wise.
Any ideas of other steps to take?
Got it figured out. Feel kind of silly.
Just needed to format both cards to fat32 and add the two files from tim6a back to the external card. It booted, reflashed and away it went.
Phew, thought I was going to have to rig up a touchscreen for my computer
Related
I went to upgrade to the ultrafast, ultralight ROM, found here:
http://forum.xda-developers.com/showthread.php?t=665081
I installed it through Active Sync. It worked fine until I got the setup screen. (Yes, I followed all the instructions found here, for noobs: http://forum.xda-developers.com/showthread.php?t=448008) However, as soon as I do the initial reboot and then go to set up the screen it won't set up. I touch the screen on the cross hairs and it sits there for 5-15 minutes. Then it moves to the next cross hair. Fine, I have all day! So once I get to the last crosshair it starts all over again. This has happened 5 times. So I ditched that ROM and moved to Timlol's, to see if that would make a difference. I installed it from the MicroSD card. Same thing. I have reinstalled it now 5 times from the card and every time the same thing.
Ideas?
Update
I tried the Remote ScreenAlignment and that didn't help. When I activated the skip button it left me the message "No screen alignment information can be found for your device." However, I figured it out. I can't believe how easy it was. Instead of tapping the screen I held the stylus on the screen until it jumped to the next crosshair. Blush. I never ran into this before, having had 2 Touch Pros for the last 9 months.
Moved as not ROM Development.
Try placing welcome.not file on the root of storage card have attached as have to make sure welcome.not and noy welcome.not.txt
my hd2 Radio version is 2.05.51.05_2
when i try to launch android i get a black screen with a couple of lines ending with "jumping to kernel" and then it fades
what should i do ?
please help
I had that problem to start as well. I did a little more digging and I read that if you copy and paste the contents of the Android folder straight to the root of your sd, it would work. And it did. I booted up and got most functions to work. I'm having a couple other issues now though,
3g not working consistantly
after leaving it on overnight, I was able to turn it on 4x. The fifth time, when i tried to turn it on the 5th time, my power buttons on the bottom came on but no screen. I had to pull the battery to reboot to WM
GUYS, AFAIK you wont get droid running well (if at all) with a xx.51 radio. You will need to flash a .50 one, then you should be rolling.
Head over to the hd2 android forum and read the sticky guides, very useful and informative
Also ensure card is formatted fat 32 or it wont boot.
Hi there,
I'm having an issue with the my XT720 and hopefully someone can help, or has at least seen something similar. When the phone goes unused for a minute and the screen times out, I can not get it to come back on as expected. If I press the power button, the lights under the four buttons power on, but the screen stays off, and both the screen and buttons don't respond to being touched (ie no noise, no feedback, nothing). If I hold the power button down, it will not stop or start, and I have to do a battery pull (the phone has not been rooted). If I press the power button to lock the phone manually, it can come back to life, but not after a timeout.
This started happening when I replaced the sd card that was included with a new one. I've had occasional issues where it will decide that I don't have an sd card inserted (also fixed by a few battery pulls), so I figured time to get a new / faster sd card. The new one has worked fine in my PC to store data, but once I put it in the phone, this happens.
If I switch back to the old sd card, the screen problem goes away. I've tried formatting the sd card from the phone (as well as from my pc), and it doesn't help.
Any ideas or input is appreciated.
Thanks,
Brandon
I had a similar unpredictable problem. I'm not sure what the core of the problem is but sometimes I suspected the SD-card as you did.
Sometimes the phone didn't show up the display even after a battery pull out. The thing that always helped in MY case was to pull out the battery for 1 hour and the problem disappeared for 1-2 months...
Hope this will help.
did you in anyway modify your phone? that includes rooting etc
i had this problem before but it stopped after i cleared my davik cache and it re populated the directory after i rebooted it. worse case scenario, you might want to try reflashing it.
I've not modified it at all. No rooting, no flashing, nothing. And I'm not keen to reflash it as it's from Wind in Canada, and there is no Wind rom posted. I know others are compatible, but I suspect it would make it harder to get warranty service if it has a BrightPoint rom on it (though I guess I should check the build number and see if it's the same).
I (occasionally) have the same problem. I, on the other hand, have had this issue since I bought the phone back in August of 2010. My phone is rooted, sometimes overclocked, and running standard android 2.1update1. What happens to my phone is that it is in lock mode and I press the lock button and all that happens is the 4 buttons below the screen illuminate but the screen itself does not. To solve it, I do a battery pull and it is back to normal. I don't know specifically what causes it because apparently this problem is also happening in unrooted XT720's. BTW I have never changed my SD card from the 8GB one that came with the phone.
I hate to hear about this issue but I'm glad I'm not the only one having it. I just got my XT711 a few days ago and the screen has done the same thing a few times to me also. I know 1-2 times I just picked up my phone and it did it, another time was when my camera froze, and once even when I paused Angry Birds game until the screen shut off, that time when I pushed the lock/ power button the 4 bottom lights came on and I could here the sounds from my game but my screen was blank. Hasn't done it in a couple of days, so hopefully it just had the flu! If anyone finds out what it is, let me know also because I've seen people with all models of XT phones having it.
Try another SD Card
Thank you, yes I have a new class 10 sd card ordered, so hopefully that cures the problem
Hi All,
Saw a few posts with similar things such as random reboots and bootloader issues, however my issue seems a little different. I already know the first few things I'm going to try but would just like a little bit of input.
The tf700 isn't my first transformer tablet, I had a prime back during release and replaced it with the 700 after my friend broke the screen. I have plenty of experience with flashing the devices and putting on custom roms etc. My infinity has been on JB since the OTA update came (infinity is 100% stock). I use the device every day extensively and it is in the keyboard dock about 99% of the time.
Today while checking my email the device randomly froze, went to a black screen, and then started up at the first asus logo (has happened before so I was not that surprised). After getting to the second splash screen with the silver asus logo I let it sit for about 15 minutes where I continued to get the loading animation. I decided to restart and go into the bootloader menu and thats where I noticed some issues.
Once in the bootloader it seems that Volume UP (to change between RCK, Data wipe etc..) is always recognized as Volume DOWN, meaning I cannot switch between any of the bootloader tasksJust realized they changed the input even though the bootloader text still has ICS commands listed. That leaves me the option of waiting 10 seconds for a cold-boot or starting the RCK. Unfortunately either task I decide to do freezes the screen on the bootloader. I know that the device is responding at first because of the highlight over RCK fading in and out, and then it freezes. Prior to the freeze the prompt always reads Signature Match when trying to cold-boot or start the RCK. Restarting the device again leaves me stuck on the first splash screen, and never progressing after that. I am somewhat concerned about possible corruption from this.
Currently I am letting the power drain all the way down while in the dock and will try charging it to see if that brings it out of this brickish state. In addition I also have a micro-sd in the device, as well as an SD card in the dock.
Other than power draining I would really appreciate some advice, because of freezing in the bootloader I am unsure whether I would be able to perform any sort of modification to overwrite whatever has been corrupted.
Thanks in advance,
Jon
jallweiss said:
Hi All,
Saw a few posts with similar things such as random reboots and bootloader issues, however my issue seems a little different. I already know the first few things I'm going to try but would just like a little bit of input.
The tf700 isn't my first transformer tablet, I had a prime back during release and replaced it with the 700 after my friend broke the screen. I have plenty of experience with flashing the devices and putting on custom roms etc. My infinity has been on JB since the OTA update came (infinity is 100% stock). I use the device every day extensively and it is in the keyboard dock about 99% of the time.
Today while checking my email the device randomly froze, went to a black screen, and then started up at the first asus logo (has happened before so I was not that surprised). After getting to the second splash screen with the silver asus logo I let it sit for about 15 minutes where I continued to get the loading animation. I decided to restart and go into the bootloader menu and thats where I noticed some issues.
Once in the bootloader it seems that Volume UP (to change between RCK, Data wipe etc..) is always recognized as Volume DOWN, meaning I cannot switch between any of the bootloader tasksJust realized they changed the input even though the bootloader text still has ICS commands listed. That leaves me the option of waiting 10 seconds for a cold-boot or starting the RCK. Unfortunately either task I decide to do freezes the screen on the bootloader. I know that the device is responding at first because of the highlight over RCK fading in and out, and then it freezes. Prior to the freeze the prompt always reads Signature Match when trying to cold-boot or start the RCK. Restarting the device again leaves me stuck on the first splash screen, and never progressing after that. I am somewhat concerned about possible corruption from this.
Currently I am letting the power drain all the way down while in the dock and will try charging it to see if that brings it out of this brickish state. In addition I also have a micro-sd in the device, as well as an SD card in the dock.
Other than power draining I would really appreciate some advice, because of freezing in the bootloader I am unsure whether I would be able to perform any sort of modification to overwrite whatever has been corrupted.
Thanks in advance,
Jon
Click to expand...
Click to collapse
Seems like you only have RCK option on your device. I would download the full JB .16 version from the Asus site, unzip it and rename the new unzip file to EP201_768_SDUPDATE.zip on your PC, plug in your micro SD card (make sure no other zip file(s) on the root of your micro SDcard), then copy this file to the root of your micro SD card, remove the micro sDcard and plug it back to your tf700, Hold down volume down and power button and let it boot to the RCK (by default) see if the device perform the update.
buhohitr said:
Seems like you only have RCK option on your device. I would download the full JB .16 version from the Asus site, unzip it and rename the new unzip file to EP201_768_SDUPDATE.zip on your PC, plug in your micro SD card (make sure no other zip file(s) on the root of your micro SDcard), then copy this file to the root of your micro SD card, remove the micro sDcard and plug it back to your tf700, Hold down volume down and power button and let it boot to the RCK (by default) see if the device perform the update.
Click to expand...
Click to collapse
Thanks buho,
Full power drain and repower didnt seem to fix it.
I gave it a shot with the update and I still got the message saying that the signature matched and then freezing at the bootloader trying to use the update. As I edited in my post I found that the bootloader commands had been swapped, so I can get to the other options to work. However all of them freeze the bootloader, I cant get any kind of USB recognition at all.
Unfortunately things may have gotten even worse...
I figured since I just need the device to work I would do a full wipe, I started the data wipe, got the freeze after a bit of text. I left the device for about 20 minutes hoping it would go through with the wipe. It was still frozen on the bootloader so I reset the device again... After resetting I cant even get into the bootloader anymore, power button + volume down does nothing.
So currently Im stuck on the first splash screen, unable to access the bootloader. I would appreciate any help at all.
Just to update, I can get APX mode to function right now, but I am not really sure where I can go from there...
Hey everyone, I'll start by saying I'm new to these forums, so go easy...
I've had an S7 (Verizon SM-G930V) for probably 3 years, recently it randomly glitched/locked up (screen had strange color bars through what I was looking at) phone restarted and then was stuck in a boot loop. It's never been wet or dropped hard and is in really good shape. I shut it off and attempted to re-start with the same results... Got a new S20+ so I at least have a device, but I'm determined to get the lost month on the old S7 back since I had a backup from early Feb.
I tried a new battery since that was mentioned, didn't change anything, however in messing with trying to get the phone to boot have discovered a few strange message screens and behavior...
1. Phone will eventually stop responding to key presses, have to pull battery connector, wait, then it will re-boot, but every time the blue 'Recovery Mode...' is displayed. If I touch nothing, it will boot and start 'installing updates' but eventually lock and restart. At one point it made it as far as the Verizon screen, then died.
2. I can get the phone to to into the recovery menu and it will respond to commands. I've tried restart normally, boot to safe mode, and shut down phone normally, all of which result in the same restart and recovery mode message and then the lock during the update.
3. I have successfully made it to the download mode screen a few times, but don't have the knowledge of what needs to be done there and which files I would need to upload to it to make that work. (phone was totally stock rom) It had recently updated to the latest version available from Verizon which I think was 8.0?
4. Now I have found a new error screen which I have not seen before... The little Android guy has X's in his eyes and a large yellow sign with ! in it says 'No Command' and then the phone restarts? It also during that finally responded to being plugged in via USB charging, however normally it shows no signs of charging other than being warm and actually charging the battery (verified with a meter)
5. When the phone is on, it gets warm quite quickly (it's still split open and the tin covers are warm, but not hot)
Hopefully someone can help out. I wouldn't say there's anything too critical on there, but there are some pics I'd really like to have back :crying:
Thanks everyone!
bigblkyj said:
Hey everyone, I'll start by saying I'm new to these forums, so go easy...
I've had an S7 (Verizon SM-G930V) for probably 3 years, recently it randomly glitched/locked up (screen had strange color bars through what I was looking at) phone restarted and then was stuck in a boot loop. It's never been wet or dropped hard and is in really good shape. I shut it off and attempted to re-start with the same results... Got a new S20+ so I at least have a device, but I'm determined to get the lost month on the old S7 back since I had a backup from early Feb.
I tried a new battery since that was mentioned, didn't change anything, however in messing with trying to get the phone to boot have discovered a few strange message screens and behavior...
1. Phone will eventually stop responding to key presses, have to pull battery connector, wait, then it will re-boot, but every time the blue 'Recovery Mode...' is displayed. If I touch nothing, it will boot and start 'installing updates' but eventually lock and restart. At one point it made it as far as the Verizon screen, then died.
2. I can get the phone to to into the recovery menu and it will respond to commands. I've tried restart normally, boot to safe mode, and shut down phone normally, all of which result in the same restart and recovery mode message and then the lock during the update.
3. I have successfully made it to the download mode screen a few times, but don't have the knowledge of what needs to be done there and which files I would need to upload to it to make that work. (phone was totally stock rom) It had recently updated to the latest version available from Verizon which I think was 8.0?
4. Now I have found a new error screen which I have not seen before... The little Android guy has X's in his eyes and a large yellow sign with ! in it says 'No Command' and then the phone restarts? It also during that finally responded to being plugged in via USB charging, however normally it shows no signs of charging other than being warm and actually charging the battery (verified with a meter)
5. When the phone is on, it gets warm quite quickly (it's still split open and the tin covers are warm, but not hot)
Hopefully someone can help out. I wouldn't say there's anything too critical on there, but there are some pics I'd really like to have back :crying:
Thanks everyone!
Click to expand...
Click to collapse
If what you've described is correct, all of the solutions involve flashing the stock firmware which will of course wipe the device.
Were your photos not stored in a folder on the SD card?
There is a chance you can recover the device using Samsung Kies with the emergency recover option but if you've encountered the "no command" screen it's not looking good.
Unfortunately I did have an SD card installed, but I normally kept my camera pics on the phone's memory, since I have had an SD card fail as well and lost everything on there.
So this took an unexpected turn yesterday pretty much right after posting this... I've been messing with the phone, unplugging the battery each time, and have managed to get into different menus which kept making me think that something still had to be working if I could do that. Well, after leaving the No Command message on the screen it magically booted into the Recovery menu with (finally) the option to wipe the cache partition, which I did and rebooted normally. Believe it or not, it booted normally and into the OS like nothing ever happened?!
I instantly plugged it into my PC and ran Smart Switch which started taking a backup! About 25% though the device restarted again and was really warm to the touch on the RF covers inside. Bummer...
So I figured heat was now the issue for some reason... I waited for it to cool and then reinstalled the SD card and figured, if I could get it to boot long enough, the SD card is a quicker transfer and I'd just use ES File Explorer to try and do a photo dump to the SD card and see how far it would get. It actually made it all the way through and gave me enough time to grab some other stuff before getting hot and restarting again.
I believe the overheating is being caused by my opening of the device though... Currently I have the antennas removed and the speaker so that I'm able to quickly access the battery connector (which BTW seems to be the trick here to this working) But inadvertently, without the larger wireless charging coil in place, it relieved the pressure on the motherboard and broke the thermal paste connection between the chipset and the copper heatsink (I didn't tear it down further to check, but I can hear the 'sticking and peeling' when you press down on it).
I think what I'm going to do is apply pressure with a chip clip or something similar (non conductive) and see if I can grab a backup again before it restarts. After the cache wipe the phone seems to understand that it's plugged in and charging now which is a new thing as well...
Sorry for the long winded posts, but if this at all helps even one person with the same situation as I have, maybe that'll be worth getting lost in here