Related
My wife left the window open near my only laptop that have, and a thunderstorm came through.......well you no the rest. Dead laptop after it completly dried, I get power but a driver is stuck in loop mode, so only the boot screen shows up. Well my question is do anybody on xda developers no how, or no anyone who knows how to change roms using only a wizard. I have a t-mobile mda (waiting for the fall for new pocket pc releases) with current wm6 rom crossbow reloaded 1.7. Would like to change to mfrazz xda6 (the real wizard window mobile 6 rom from ngenetics) rom. I thought I read somewhere that someone changed there rom with their pocket pc from the SD card. Please read my question thoroughly. I no theres a method by using a card reader and entering bootloader.....and so on, and so on. I have no access to any type of computer ( until I buy a new one ), and I need instructions or someone point me into the direction for changing my rom with just my pocket pc. I will continue to search forums, google, or whatever myself until we get and answer to this. Thank you all for reading my new post, and helping out in any form or fashion. Oh yeah I forgot to mention; please do not post or respond with any negativity. I no it say junior member ( noob) next to my users name , but i'm a grown ass man so respect me like one. Remember i'm the senior noob.
This is a little off topic, but have your tried booting your laptop and then pressing the F8 key before the Windows boot screen is displayed? From this screen you can try the "Last Known Good...." or try to boot into safe mode. If that doesn't work, you can try booting from your Windows CD and doing a repair installation of windows? If you can get power and it sticks at the boot screen, then some of your boot files may be corrupted. I'm assuming that you have Windows XP. Hope this helps. I don't know anything about flashing ROMs from the SD card, but have heard something about that in this forum or HoFo.
STOP TRYING TO TURN IT ON!! you're making it worse. trust me.
i work as a computer technician, i fix machines that have been spilled on all the time.
shut it down, take it somewhere to have it fixed. it might be dry on the OUTSIDE, but the inside is either
1.) still wet
2.) corroded chips that are shorting out
the only way to really tell, is disassemble it. take everything apart, REMOVE ALL ELECTRICITY to the computer, and check to see where the liquid is and what damage it has done. if you see corrosion spots, get a soft bristle tooth brush, run the part under water and use mild soap to brush it off. rinse it off, then let it dry for 48 hours minimum.
do not do this with the hard drive, optical drive, or LCD - just PCBs.
i've had dozens of computers come to me that had an entire cup of soda/beer/tea/coffee/water, etc. on it and was able to get it working. Water is the easiest to fix, as there are no sugars or anything to bond to the components.
its not the liquid that causes the problem, its the electricity running through it.
lol at this point i think im more worried about your laptop, and i am pretty sure there is a way to boot off of an sd card but im not sure, im sure somone here will know
h4ck must be a member of the geek squad!
my sony vaio laptop
when I saw my laptop it was soak and wet. I removed the keyboard pad, and unscrewed all the screws. Yes there was water on the inside, and I tried to dry it as much as possible. Went on vacation came back three weeks later. Before there was no power, when I return home I turn on my laptop and voila, it comes. I hit the f8 key and started it from its last known good config. System restarts but a small blue screen appears, then disappears. So I return to the bootscreen option and started it up in safe mode with networking. Everything came on in safe mode in a smaller screen size. I went to start/computer system/vaio recovery. Now this is were I messed up. Insted of using the last good config. check point, I used complete system recovery back to its normal state the way I bought it. all programs and software will be deleted.(just like a hard reset for pocket pc). It did a complete recovery of my hard drive c, and restore everything to factory settings. Now when it restarts a message says its missing some files and to repair this hit the "r" key and insert the windows xp cd-rom disc. I did this but it won't boot from the hard disk for some reason. Then after some time from trying to boot from the cd-rom disc, a small blue screen appears with the message: "A problem has been detected and windows has been shut down to prevent damage to your computer. The problem seems to be caused by the following file: ati2dvag. The device driver got stuck in an infinite loop. This usually indicates problem with the device itself or with the device driver programming the hardware incorrectly. please check your hardware device vendor for any driver updates. technical information: *** stop: 0x000000EA (0x81cB2440, 0x81E0A440, 0xF896DCB4, 0x00000001) ati2dvag- beginning to dump of physical memory-physical memory dump complete. Contact your system administrator or technical support group for further assistance." Sorry guys for the long story but thats everything. I know this is a forum about PDA's but i'm just responding to the response. By the way have anybody found anything yet?
I won't flame you, but this was posted in the wrong forum regardless of what ROM you are using to flash to your device. Just keeping things clean.
Yeah, you're on the right track. You need to make a note of the file it says it's missing and the directory path. Then boot using the XP CD and choose r for recovery console. Depending on the number of windows partitions, you may need to choose the correct partition and provide an administrator password. After that you will see a DOS-like prompt. Copy the missing file from the XP CD to the hard drive. The command should look something like this:
expand d:\i386\missingFile.ex_ c:\windows\system32
D: is your CDROM and C: is your hard drive. Make sure you copy it into the directory that you made a note of earlier.
Also, here is a link that talks about an infinite loop problem with ATI drivers http://www.sightsea.com/pghpchd/pages/infinite_loop.html
I just got my Captivate last Friday. Hadn't done anything complicated with it, basically I just used "Unleash the Beast" to root and sideload the thing. Ended up with some sort of weird permissions issue going on with the SuperUser app that had been installed with it, I was getting permission request loops. So I used Odin to reset it. At this point there wasn't anything really wrong, USB worked and the device appeared to the computer. So I just rebooted the Captivate into download mode using adb reboot download and went on.
So later on I grabbed SuperUser 2.3.4(?) or whatever the latest one I found online was, loaded that to do adb pull /system/apps since I realized that Unleash the Beast just deleted everything and I honestly hadn't even seen what it removed yet on the phone itself besides the list on the web site. So after the backup I odin'd again and then grabbed the files from SuperUser 2.3.4 replaced the existing files in Unleash the Beast with it. Actually ended up working perfectly for a while.
I'd used the phone for a few days, no issues, finally got my 16GB SD card from my Raphael and inserted it, had been downloading apps left and right. Well all of a sudden the phone seemed to have it's USB stop working for anything but charging. I recall plugging it into a charger or computer when I first got it and it would ask if I wanted to mount the SD cards for use, then I would just see the battery indicator charging. and I'd toggled developer usb a half billion times trying to get access and fix it.
The computer didn't see it, device manager didn't even flinch(Win7 x64) like it normally does when you plug in and unplug a USB device. Tried it with another computer and same issue. So I rebooted into recovery mode and tried that, the first several times around nothing was detected. Well my finger slipped and ended up hitting the Clear user data and cache option in the recovery mode.
At this point when it boots up, i still dont have usb access, I'm stuck in a force close loop, I can't install apps, can't seem to get it to reboot into download mode via the key commands, and installing apps is impossible since browser and market crash on start.
I've spent the night rebooting and trying to get into download mode for odin, I used to be able to get into recovery mode everytime I tried, eventually I started to see an "uknown device" show up in device manager, which I googled some info from it and all I could tell was it was Microsoft's dummy driver for devices that couldn't be found. Another weird response, it seems to be beginning to hang on the charging battery thing from time to time now.
At this point, its been under a week and I'd trade it in. Except the thing is with enough struggling you can see the apps installed. Most of them were removed but Market Access and Superuser are still in the apps list, and I'm worried about AT&T spotting that, figuring out what I've done and rejecting the claim.
just under half the time now, it boots, the other over-half of the time I get the spinning "battery loading" icon that shows up before the battery thing gets loaded, but not spinning. It pops up, and disappears, from time to time goes to show me my battery status instead of booting, even when not plugged in.
I'd like to think I haven't tried everything? quite obviously i can't run update.zip files from my 16gb sd card since it gets mounted at /sdcard/sd, and I've lost the file browser to move anything around. I've tried rewiping but that doesn't do a thing.
I hadn't gotten to the rom manager stuff yet since I wasn't planning on playing with roms if at all. and at this point that doesn't appear to be an option anymore.
Any suggestions? I was getting to continuing to reboot it till the battery thing comes up 100% of the time then goto ATT and see what they say.
So long that you can get to download mode you SHOULD be good. When you plug in the usb..you need to pull the home dropdown..select usb and tell it to mount. I may be telling you what you already know but download mode is hold both volume buttons from the battery screen...one black screen...att screen...black screen and release pwer but hold buttons. I had problems with this so what I did was unplug the usb...volume buttons...hold power and see att boot screen...(plug in usb)...black screen...att boot...black screen and release power til u see download mode. You can use Odin and set back to stock from there normally.
If the PC is showing unknown device..you are kind of stuck til you fix the driver issue. Maybe remove and reinstall or something not sure on that but that's the first order of business. Go to the dev forum and try reinstalling from there. (One click Odin downloader has teh drivers)
If your phone boots or can get into recovery or download mode you are ok. I ran into the problem where I couldnt even power it on.
Well by now I know that download mode is the holy grail to get things fixed. Recovery mode, I used to be able to get to, but didn't show up. I'm wandering if somehow my USB port got shorted or something.
The drop down option to make it mount is why this all began, it disappeared and never came back.
Trying your steps specifically, first couple times would just end up back at the battery screen. I eventually ended up at recovery mode. Did I end up at recovery mode for releaseing early or late?
I've reinstalled the Captivate drivers a couple times now and tried clearing all past installs of it. Still unknown device. At the moment I have it in recovery mode, so I've rebooted my tower into Ubuntu(Which has the sdk, but never tested with it). Since I've kept reading that Linux doesn't need drivers. Well ./adb start-server and ./adb devices still show nothing...
I can grab a fresh computer that never connected to this thing to try, but I'm kinda doubting it will do this trick at this point. I'll download the odin w/ drivers on it and try that.
hmm.... just ran over to one of the computers here that had absolutely nothing to do with android on it, no drivers, no sdk, no software, nothing.
Went to
[STOCK ROM] Odin3 One-Click Downloader and Drivers(new user=no links)
Downloaded the Windows X64 drivers, installed and rebooted
Plugged the phone in after it rebooted and I'm getting
Unkown Device, I'd pull some info from the Device Manager, but all it is reporting is scewed due to it being a usb device and Windows installed dummy drivers.
All I've got left for testing is my brother's Win7 x32 laptop, granted all I've been able to try with here has been x64 so far. Also on the first computer I was doing all this with. The drivers DID work, they WERE installed and functioning. Previously I could ADB to my hearts desire and I've used odin before. I used the same USB port, used different USB ports, tried different cables.
I had some strange issues on mine. When I would try to go to download mode. All of my USB stuff (KB and mouse) froze up and I had to plug in via PS2. I had the unknown device issue and Not sure how I fixed it. I downloaded and installed the Samsung Kies program and I also downloaded the driver. Ultimatly after banging on it for a bit it worked..not a Unknown device but it was some king of...Gadget Driver or some stuff was messing with me. Try installing Kies and see if that does anything...also make sure you remove the drivers before installing. It acted really squirrly to me too tho. From what you say..it sounds like a borked driver. Im on 32bit XP and took it home to my 64 Vista and got it working whne the 32 was jacking me around.
Just had a chance to try with Kies real quick, I'm not so much thinking i killed my drivers but that somehow the cell phone changed it's id calls. I'm going to give it a shot with kies on a fresh Vista x32 system at work. I still can't seem to get it into downloader mode, but I'm getting more consistent with Recovery and getting the thing to boot back up. If I consider the Battery screens to be your blank screens then I can get it to go recovery or "normal" boot. But still can't seem to get download mode at all.
Up until recently, I didn't get Unkown device showing up even when the system was in "normal" boot. Before, originally it would only show up in device manager in recovery mode, and then it would be the unkown device.
Just out of curiosity could you spare the driver specs for your setup so I can compare? Like Date, Version, and any Hardware IDs? I'm wandering what hardware IDs this thing is giving off since windows wont show me.
Well not sure what suddenly happened. But after enough reboot--attempts, recovery mode is finalyl appearing on my office computer as SAMSUNG Android USB Composite Device. Win Vista x32, only installed Kies and download SDK(speaking of, adb still doesn't see devices). Just finished redownloading odin(wish i'd had a thumbdrive on me when i was at home) and am about to see if I'm going to be lucky by vista somehow.
If you still keep having issues find a way to short the phone out and tell at&t that the phone just got really hot and then turned off. They should replace as a bad unit and get you hooked up with a new one.
Sent from my FroyoEris using XDA App
jonscapri said:
If you still keep having issues find a way to short the phone out and tell at&t that the phone just got really hot and then turned off. They should replace as a bad unit and get you hooked up with a new one.
Sent from my FroyoEris using XDA App
Click to expand...
Click to collapse
Well that thought has occured, that and magnets lol
I think i might have found a clue to the cause. I think it was tied to the whole usb thing. When it appeared to show up at all first time around, i had tapped the menu button while in recovery. And the natural way I'd been holding it applied just a little pressure on the usb cable. Well I got the phone to finally show all the notifaction tab options for debug and storage when i held down the usb plug in the phone down a little bit. I'm guessing that the pins for power are fine but maybe the data pins, or maybe one of the data pins is loose and thus it's an unkown device since it's not responding correctly.
I didn't have time to finish trying to fix it at work, and i'm stuck in class now. I'm'a see if i can get admin access on my terminal here and download everything while the teacher does his orientation. Otherwise i think i can fix it once i'm home now.
=====EDIT=====
Well getting the phone into Download Mode was a bit easier with Ubuntu via ADB since I don't have to wait for Windows to load the driver. Then just rebooted the box into windows for Odin. Long painful story short, I didn't setup Rom manager to be able to undo my changes when the USB port went bad/inconsistent and didn't expect those changes to complicate the recovery without USB. So I'm making sure it's a rather provable issue and going down to ATT with it. 7 Days from receiving the phone, and I'm goin in for an exchange due to bad USB. Funny.
Hi lads..
Im proud owner of Galaxy S 2 for 8month or so. Started to facing some weird problems couple days ago. First was - no WiFi connecting (No MAC Address and cant turn it off). Now Process system is not responding errors with 2 options Force close and Wait. No matter which i choose, phone does quick reboot, like when windows explorer hangs and recovers. Can it be damaged nand storage? Phone where used a lot for data storage (Around 2GB per day where written on device and erased). Still should have warranty, but its tricky, coz have no time to wait 2-4weeks. Phone never been rooted. Any tools to check internal memory health?
Thanks a lot.
If you have never rooted nor installed a custom ROM then the best thing you can do is backup using Titanium/MyBackup, restore factory defaults and start all over again.
If you have gone and changed something then you will need to give some details.
Dan
Done factory reset yesterday - no difference. Now rooted device, kinda works good, but no wifi. When i use code *#*#232338#*#* it doesnt show my Mac address, says File doesnt exists.
Ok well in your first post you mention your NAND and a lot of data transfer. You don't transfer data to the NAND, or you shouldn't be. You'll be using the 16GB internal mSD card for that.
If your MAC address has disappeared this may be a problem with the /efc mount area, which is of course in NAND. This is probably not the case though.
Now you've rooted your flash counter may have increased. I would send this back under warranty after resetting the flash counter with a USB Jig.
Unless, that is, you remember anything else you may have done to the phone like an upgrade, changing the radio/modem, or something else.
Nothing changed.. Yea you are right about Nand and internal flash drive. Will costum firmware fix it? Or should stay on current rom? Sorry my dumbness - im kinda oak in droid things..
It all depends on what the issue is. I've seen someone talking about the EEPROM being broken on similar issues like this, which requires Samsung to look at the phone.
Custom firmware can only use the parameters the hardware or /efc area can give to it in the first instance. If the wifi MAC address is gone then it's gone, simple as that.
Weird - now see MAC Address when enter code, but wifi it self is not turning on for now. It turns on, does quick scan (doesnt show any AP) and then turns off again. So will bring it to warranty service. Thanks anyway
Hello,
I'm sorry to bother you with an apparently repetitive thread, but I assure it is not.
I've been dealing with this problem for over a year now. Of course there were times that I simply gave up, but every now and then I searched all over the internet (seriously; very resilient, I am) and tried everything. Nothing seems to work.
The issue is: one day I was reading something on Google Reader and the tablet restarted. When it came back, it was in this password screen.
[AS A NEW USER I COULDN'T POST THE IMAGE - please see attachment ending in 41]
Detail: I had never, EVER set any kind of password. I don't do this with any of my devices unless I'm obliged to (as in Windows 8, this big piece of shiite).
So the thing is: I did not set a password, I did not choose to ask for a password in any situation and there isn't a single combination that I haven't tried. The thing doesn't even ask me to stop -- like 'hey, you've tried your 30k input, I think you should stop now'.
Now, for you not to start cursing me, I tried EVERYTHING that is basic and post-basic to fix it. I did wipe the data, I tried flashing another ROM, I did cold boot, factory reset, EasyFlashed, nvflashtf and whatnot. I swear to GoogleGods that I, as a non-expert-but-very-keen-on-technology, could.
Another thing that happens is when I try to enter the recovery mode, after using the nvflash, it doesn't work. The image that appears to me is this one:
[SAME THING -- attachment ending in 38]
Again: I'm not a complete noob. I know how to get into things; all I need is a simple guidance. I'm really sorry if this has been posted before and only I couldn't find it, but I won't be so if someone helps me to get it and solve my problem. I can't stand this anymore -- now it's just a matter of pride.
Thank you all.
This happened to me on my SL101 after I flashed a ROM of some sort. I used ADB commands to push the stock ROM back to it and to push another Recovery to it. Mine was in worse shape, Recovery loop, and then I finally got it to where yours currently is. My physical nor on screen keyboard would even work. Look up some ADB commands, perhaps you already know them, and attempt to either push the stock ROM or a new Recovery blob back to it.
D
DatDude123 said:
Look up some ADB commands, perhaps you already know them, and attempt to either push the stock ROM or a new Recovery blob back to it.
D
Click to expand...
Click to collapse
Yeah, well, y'know, I'm not at this level yet, but I'll dig into ADB and stuff.
I tried to use this sometime in the past, but my computer was so bad back then that I had to give up to keep my sanity. Now I've got a fairly good one (very good, considering the few things I use it for), however much less time.
Tonight is the night, though. I'll study as much as I can and I'll fix this ****. Any tip you may remember now would be useful.
Thanks.
I'm struggling with something even before I start: there's no way I can get access to the system and turn the USB Debugging on.
I know I'm not getting much attention, but I won't give up. Please just do not accuse me of spamming; I'm just a desperate geek that has been kept away from his toy.
Alright, after the childish speech, here's the latest update: I cannot use de ADB thing because there's no way I can turn on the USB debugging mode.
Or is there? The latest news is that I can get access to some system files through the ASUS File Manager (turns out it still reads the MicroSD Card, even though I could not update the device this way). So, technicians, is there a way to hack into this beast? Fu ck, I don't even know how to call it anymore.
There isn't much I can do with this File Manager. Mostly visualize the folders and rename this and that (which is the only thing I reckon might be useful).
Jesus, I'm sleepy, I can't even write properly anymore. Please someone help me. It can't be that hard.
maycondimas said:
I know I'm not getting much attention, but I won't give up. Please just do not accuse me of spamming; I'm just a desperate geek that has been kept away from his toy.
Alright, after the childish speech, here's the latest update: I cannot use de ADB thing because there's no way I can turn on the USB debugging mode.
Or is there? The latest news is that I can get access to some system files through the ASUS File Manager (turns out it still reads the MicroSD Card, even though I could not update the device this way). So, technicians, is there a way to hack into this beast? Fu ck, I don't even know how to call it anymore.
There isn't much I can do with this File Manager. Mostly visualize the folders and rename this and that (which is the only thing I reckon might be useful).
Jesus, I'm sleepy, I can't even write properly anymore. Please someone help me. It can't be that hard.
Click to expand...
Click to collapse
For some reason i thought you were on th sl101(slider) so i didnt comment. So heres the deal, any fix is going to be data destructive(nothing you can do at this point as even if you manage to pull data from the tablet, it will be encripted) You need Easyflasher(dev section) follow the instructios there (basically donwloading stock firmware from asus and by using nvflash in apx mode it will re-partition storage, and upload the stock firmware to the tf101)
If you hit any problems, post them here and ill help you further
Edit: just read you post more, if you tried easyflaher and it didnt work, please post the details of what you tried within easyflasher.
Its a strange issue, if it happend to me and id tried the things you already have, this is what id try:
-Flashing ubuntu from the dev section(i known very little about how nvflash works but it maybe only re-partitioning certain partitions, ubuntu i would imagine would require a full re-partitioning)
-alternativly (or on top of the previous idea) use one of the ubuntu installers(OLiFE on ubuntu worked the best for me, but franks tools/ newer software based on franks tools should work fine) and flash the Prime! rom on its own.
If these dont work, your last resort is asus - but thats a long shot lol
maycondimas said:
I know I'm not getting much attention, but I won't give up. Please just do not accuse me of spamming; I'm just a desperate geek that has been kept away from his toy.
Alright, after the childish speech, here's the latest update: I cannot use de ADB thing because there's no way I can turn on the USB debugging mode.
Or is there? The latest news is that I can get access to some system files through the ASUS File Manager (turns out it still reads the MicroSD Card, even though I could not update the device this way). So, technicians, is there a way to hack into this beast? Fu ck, I don't even know how to call it anymore.
There isn't much I can do with this File Manager. Mostly visualize the folders and rename this and that (which is the only thing I reckon might be useful).
Jesus, I'm sleepy, I can't even write properly anymore. Please someone help me. It can't be that hard.
Click to expand...
Click to collapse
If you can't get into anything, but you can enter APX Mode, but NVFlash doesn't work, then I'm not sure anything will as NVFlash completey deletes and recreates all the partitions on the drive
So unless you have been unlucky and downloaded a bad version of an NVFlash ROM....
I know you say you have used NVFlash but I`ll stick this here anyway
The way I restore is:
Connect tablet to PC and make sure the tablet is turned off (Make sure it is the only USB device connected other than keyboard/mouse)
Hold Volume Up + Power for a few seconds until you hear the USB connect sound on the PC, release the buttons, you are in APX mode
Install APX drivers if you have not already
Now extract this
http://www.xdafileserver.nl/Files/Asus/Asus%20Transformer%20(TF101)/STOCK%20ROMS/ICS%20.27/NVFLASH_ICS_9.2.1.27_WW_NOROOT.7z
And run "download.bat"
I think you should see some text appear on the tablet screen, and progress will be shown in the command prompt window on the PC
Wait for it to complete 100%
Its been a while so I can't remember if the tablet will reboot on its own or if you need to hold power for 30 seconds to get out of APX mode
Either way, make sure it is completely finished and reboot the tablet
Only thing I can remember going wrong with NVFlash was the first time I rebooted after a sucessful boot, it would hang on a black screen
Just hold power for 30 seconds and then power on normally, done, if it has worked you have your tablet back, if not, I think its a hardware issue > see asus
Im very keen to get this fixed/ find the issue as uptil now I thought the tf101 was virtually software invincible, you need to pay attention to what the nvflash process says, the one thing I can think of as to why nvflash didn't work is it can't write over encrypted partitions although that would make no sense why it wouldn't.
Just a suggestion... make sure you're not docked. Some people report issues when nvflashing while docked (I can't replicate those issues except with the Tubuntu tool).
Is there a solution?
I also have an error! see picture
So i reverted my K1 back to 5.1 since i was never able to get rid of the lags and battery drains with marshmallow. Everything went fine, but my sdcard wasn't recognized anymore, most likely since i used it as adopted storage in MM. So what i tried is to repartition it via adb. Sadly, and because i'm a dumb**** sometimes, i erased /dev/block/mmcblk0, which seems to be not the sdcard but the internal memory. So for now, after a restart, the tablet won't even go to fastboot mode, screen stays completely black. Is there any way of recovering it, e.g. booting from a usb device?
What does your PC say under device manager when you plug in?
Most certainly gone. The official kill switch for recalled tablets also works by erasing some of the partitions of mmcblk0.
Rackers said:
What does your PC say under device manager when you plug in?
Click to expand...
Click to collapse
i only get in running in APX mode. So as far as i read, there might be some way using nvflash to recover it, but i wasn't able to find further information about that. As there seems to be no windows driver, i connected it on my Linux System and it shows up as "NVidia device" there.
There exists a flash tool (nvflash) for this case, but it needs a code that is unique to each device. Your only option seems to be to contact NV. Maybe they will restore your mmc for a reasonable fee.
after a few chats with NVidia support, i RMAd the tablet and they sent me a replacement without issuing any fees. I mus admit, that's pretty cool and unexpected service. Now i'll just have to make a descision whether to keep my Mediapad M2 which i bought as a replacement or the K1. :\