Hi there,
I was running SPL3.5 & AP4 on an Athena X7500 previously but making a hash of the new/old roms to install, i flashed AP Touch by PK.
I am now unable to get into windows mobile's Today screen as the customisation process which runs config & AP Touch.tsk keeps resetting the device. Each attempt i re-flash (i tried multiple ROMs, ranging from AP Touch again, AP3newSPL, and AP4.0 again) results in an error asking me to check my USB connection to the device. I suspect its because i do not have enablerapi anymore(???) inside the device. I am unable to install enablerapi into the device since it keeps resetting! deleting files from the startup folder via PC ActiveSync / Explore to try stopping the customisation / reset process also didn't quite work, neither does it allow me to delete the AP Touch.tsk file inside the device.
Can anyone help? thanks in advance
Related
I am using CE OS 5.2.20753 Build 20753.1.4.0 PV SB on O2 Atom Exec. I am trying to flash my ROM with any of the provided ROMS in this forums rite from WM5 till Jamies latest ROM.
As a background, I have already configured my mobile in VISTA laptop using the MANUALS & RAR files, provided around a year back.
The problem is as follows:
1. I run the package, which internally unzips all the files in C:\Windows\Temp
2. DSUU starts executes and provides a screen to select OS, OS+Extended ROM, OS+Eboot only, etc....
3. I tried using both ALL, OS only, OS+Extended ROM but i get the error as mentioned below.
4. I get a screen which speaks about all the my current RADIO, ROM version and the TO BE new versions.
5. I select OK / Continue.
6. Program reboots my Atom exec and stucks in "USB CONNECTED" black screen. This continues untill i try to manually terminate the DSUU process.
7. To recover from this, I remove the battery manually and insert and start the phone.
8. Phone starts working from the stage where I started flashing with new ROM.
I am totally confused as i tried a lot of ROMS rite rom Wm5, WM6 & WM6.1 which also includes all the ROMS, which i have already used in the past on the same phone.
Gurus, please suggest the possible wayout, as i am stuck on this ROM for a long time and unable to test all these new wonderful ROMS.
ASH
use win xp not vista in flashing roms...
Use the search function, there is an answer to Your question in some of the forums at xda-developers and it is posible to flash roms from VISTA, but after doing some reinstalation on USB drivers and some tweaking....try to find VISTA ROM UPGRADE
My experience is:
I followed the instructions and they worked 2 times and I have flashed the ROM twice, I dont know what happened to my computer because after that never again make it to work in vista.
I whish You Could!
Thanks
Thanks for the suggestions. I have flashed this mobile around more than 20 times out of which atleast 10 times in Vista.
My problem is, after flashing the current ROM, i am unable to flash on this device. i tried flashing other device from the same laptop and it works
When i start the flashing procedure, mobile enters into Boot mode and then nothing happens. i remove battery and mobile boots up with the same old ROM.
Please helppppppp
ASh
Hi All,
Yes I searched, could not find a helpful post that I could understand (unfortunately a lot of not-so-good english on these forums!).
I used the file 'windowsmobile2003se.exe' here;
http://forum.xda-developers.com/showthread.php?t=230279
It started loading fine, then when it came up with the progress bar to start updating, my device rebooted and is now stuck in bootloader.
When I try himaupgradeut.exe, it gives me a ERROR 101: Connection Error. USB is disabled in ActiveSync and I can see the device as "Microsoft USB Sync".
The USB still works (I can use mtty and xda2unlock in Windows XP and they both work fine). Is the device still recoverable?
I have hard reset (Power + Reset), removed and re-inserted battery and tried a normal reset, none of these work.
Can I please have some step-by-step instructions on how to recover the phone? The bootloader version is 1.06
Thanks.
can you get some pics?
Have you tryed leaving the battery out for 1 day or over night. Because that fixed some problems for me.
try it
flyboy
Yeah I've left the battery out overnight (about 12 hours to make sure the backup battery ran flat). It's still stuck on the boatloader.
It's just got the normal bootloader screen (Serial up top and 1.06 down the bottom) and this changes to USB when in the cradle, so the device seems to be fine.
Any ideas?
Solution found!
I HAVE FOUND A SOLUTION FOR RECOVERING FROM BOOTLOADER!
Full props and thanks go to utak3r of buzzdev.net
Please go to this thread.
http://buzzdev.net/viewtopic.php?f=8&t=36437&start=0
MODS: Please sticky this. Please.
Hi All,
I have made a script that people can use to easily flash their Himalaya without performing all the above steps manually.
My extreme and eternal thanks go to utak3r (from BuzzDev), xda-developers.com and buzzdev.net for building such great communities and for providing so much help and information (even if it is a little hard to follow sometimes!).
You can download it from;
http://members.iinet.net.au/~nomicakes/MakeSDBoot.zip
http://www.clonnyserver.com/uploads/tools/himalaya/MakeSDBoot.zip
The zip file contains the script and the tools neccesary to do this.
As above, if you aren't familar with flashing devices and the possible outcomes, DO NOT USE THIS TOOL.
Hi there,
Yesterday I tried to upgrade my Qtek 2020 to the last rom available but something went wrong and now my PPC only shows the bootloader screen.
After hours of researching on Google I found this forum and this topic. I tried to do what is in utak3r tutorial but I can't connect to my PPC using mtty (usb port can't open) and I don't know why. :\
When I try himaupgradeut.exe, it gives me a ERROR 101: Connection Error too...
And finally when I run this script made by Clontarf it fails on the last step on writing to the SD card. It gives me a Error - Access Denied.
I don't know how to solve this. Would you please help me?
Problem solved!
I have a tmous HD 2 that orinally had windows os on it. I have since tried to flash a new rom. When I originally started this process I was dual booting. The phone would start out in windows mobile 6.5 with no update and I had to phisically launch the Android rom. After this I started playing around in order to get phone to boot in android only. The SPL I have is 2.08 HSPL I was getting stuck at the t-mobile stick together screen and then I tried bootloader mode and I was able to launch boot loader mode but wont let me do anything. Originally the rom was in an unziped format and thats how i was dual booting. Then i tried the ziped format and this is where my phone has went bonkers and won't do anything, by that i mean it wont turn on in either mode regualr or boot load. tried to connect to computer and computer dosent regonize it. has anyone ran across this? and if so can you please help me out? i am a little tech savvay but not great at it. any help would be greatly apricceated. Also when i had android running on phone it was supprisingly fast and worked flawlessly!
From a previous thread here on xda.
Q; How to install cooked Rom (using Task 29)
My Install Strategy;
· Run Microsoft My Phone Sync
· Turn off antivirus software in Desktop PC (Stop Avast Anti-Virus)
· Remove SIM and microSDHC Storage Card
· RUN XDA Developers “HD2 Task 29” as an Administrator
Task 29 is not mandatory that's true, but it's a safe way to ensure that you don't have any old files remaining after flashing a new rom.
There is no harm in doing it and the easy way is to use the tool I provided in this post:
Connect your device and flash as you do with an ordinary rom, when completed (100%) press volume down and keep I pressed until the device has restarted showing the coloured boot screen, then you flash the Rom.
· Install your cooked Rom as an Administrator
NOTE 6: Please, Hard-Reset after flash process has completed.
· Add SIM and microSDHC Storage Card
· Set Time and DATE
NOTE 7: Please, Restart the phone, after first manila screen.
· Run Desktop pc FULL ActiveSync, select setup device.
I have done this but phone wont boot up in order to do a hard reset like mentioned!
Q; I downloaded and extracted the zip file from a cooked Rom, and noticed there was no ruu file attached. What to do?
You can download the SSPL_RUU, here. place the SSPL_RUU file into the map where you unzipped your cooked Rom and lounge to start.
I have done this.
What more do I need to do in order to get my phone back up and running?
Thank you in advance for help and support
Hello All!
Relative noob here...but more seasoned all the time. Firstly my viewpad device info from FTM:
SWVer=3.410
Model: FM6-001
HWVer: 107
In a nutshell: My bluetooth wasn't turning on (would turn on..then off). So tried to fix by:
1) Rooting and install CWM 5.0.2.6 (awesome tool BTW) and various ROMs, all done with success.
2) No good, oh well now want to give up. Contacted Viewsonic got RMA to return unit..however now concerned they'll not honor warranty if I rooted the device (sigh). So thought I'd return to stock. I did backup..but was already rooted when I thought of it.
3) Trying to return to stock using many versions Sutl3 and Sutlr...and on different PCs none work..once it boots to CWM menu...just stalls with error eventually.
4) Tried to install Napster's CWM with Recovery Menu to be able to return to original state with stock recovery. My version of CWM won't install it...errors out (another great tool though by the sounds of it).
5) Can't use fastboot..never sees device...although ADB works OK. Believe that the Bluetooth issue may be a hardware problem and may be effecting devices ability to work in "download mode". Note that HS-USB device is never present in device manager in Windows even though driver is installed.
So...my question...how can I return my device to stock with one of the below .nb0 files without stock recovery, sutlr or sutl3?
Files I have:
FM6-3310-0-5029-A02.nb0
FM6-3350-0-1008-A01.nb0
Can I somehow use CMW? Can I somehow use adb and "flash_image"?
Will super appreciate any thoughts!
Many thanks in advance!
Johnster25
If I remember correctly, you use SUTL3 from Viewsonic on your PC with the *.nb0 file in the same sub/directory - and just run it to flash the stock ROM or return it to factory condition, you do NOT use CWM to flash or re-install the *.nb0 file ... Part of this process involved overwriting the CWM installed on your rooted device & reversing it to become unrooted, look under the Development subforum here in this section as there's a link/discussion about how to restore, please double check on the details written up.
Also, make sure you have a mSD card in the slot - and that the USB drivers are loaded & running (they should be installed already back then) - might want to power down & restart the PC and do the same to the Vpad7.
Let us know how it go & good luck !
Many thanks for your response.
Well, what has happened when I've used SUTL3 so far is that I select the .nbo image I wish to flash, then the program restarts teh VPAD7 into recovery mode.
From what I've read, after a few moments the phone is then supposed to enter some sort of "download mode" whereby the new image is pushed across the USB cable.
It's at this point with SUTL3 seems to error out, and the phone simply remains in CWM.
I've read a few posts that suggest that not using the correct image could produce a response like this, so I'll retry again this PM having tried re-downloaded the two .nbo files I've tried, and one I've not tried.
Will let you know how it goes!
J.
Hi Again,
OK I've retried it with a fresh copy of SUTL3, and new .nb0 files. Still no good.
Take a look at the enclosed pictures. The first time I try to run SUTL3 the device not configure error shows up. By this point CWM is showing on the VPAD7. I try to run SUTL3 again in this state and now the device not detect error shows up.
So all in all it seems to me that the device when in CWM mode is not exposing an interface to the computer...or the computer lacks the driver needed to utilize the interface.
I've also enclosed a picture of my windows devices when the VPAD7 is connected, as well a copy of the drives that show up when it's connected. The only time the drives change is when the VPAD7 is in CWM mode, at which time the H: drive (where the adb program are) is not present.
So am I missing a driver?
BTW: Have tried to copy down the synchronization program that is on the H: Drive and ran it while running SUTL3...thinking somehow it acted like a bridge to the VPAD7 (I've seen some posts that suggest this). Still no good.
J.
OK..one more piece to the puzzle...or maybe off the trail...but when trying on two differnt PCs when the VPAD7 is first plugged in I get one set of driver installs...and note that the HS-USB has an error.
Later when trying to run SUTL on it...another set of driver installs...again HS-USB error.
See enclosed.
try run sutl with viewpad in FTM mode that worked for me good luck
I have same problem before..n my solution is change back CWM with old ..mine to CWM 2.5.1..found that CWM 5.0.2.6 got problem with SUT L3..and everythind done successfully..as long u can still access ur Viewpad to change CWM its ok..
Wow! Thanks so much for your reply! This would be a huge help. Any idea where I might be able to find that older version of CWM?
Alleycatzero you're a genius! Running SUTL in FTM mode has done it!
THANK YOU!!!!!!!!!!!!!!!!!!!!!!
Johnster25 said:
Wow! Thanks so much for your reply! This would be a huge help. Any idea where I might be able to find that older version of CWM?
Click to expand...
Click to collapse
This is under the Development section - just d/l and unpack the zip file, copy to mSD card & follow the instructions. This verison should be the earlier one and I personally find it worked best together with ext3 and/or ext4 partitioning as needed.
http://forum.xda-developers.com/showthread.php?t=1015005
The issues with SUTL3 and other apps not working/running has to do with the usb drivers not auto-installing & running as they should, try to uninstall Vpad7 drivers, reboot the PC - turn off any firewall and anti-virus software, connect the Vpad7 and let it finish installing/rebooting both devices again. Then, turn back on antivirus & firewall so that you will have easier time flashing rom, connecting mSD card & copying/moving files, etc.
I recently attempted flash a ROM onto my Tab3 SM-110 using TWRP, flashing that on using a .tar.md5 file which was compatible with the device. For some reason I've encountered a screen which informs me that "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again," When I attempted to flash the .zip using TWRP. I don't know if this was because the ROM was incompatible, or if it simply ran out of power before it finished, as I wasn't there to watch it. So, following the helpful instructions that the device gave me, I installed Kies. It told me that my device wasn't supported, and Emergency Firmware Recovery doesn't find the device either.
I then moved to Odin, finding the firmware for the device on Sammobile. It was the correct software for the device, and I attempted to flash it on using Odin v3.12. The program gets stuck as File Analysis, and doesn't do anything until the battery of the tablet runs out and then the screen constantly turns on and off and continuously connects and reconnects. I searched the internet for this issues, and I've tired things such as waiting to plug in the device until Odin loads the .tar.md5 file completely, checking Re-Partition in the options, and attempting to reinstall the driver. I've tried putting the file in the AL, BP, CP, and CSC sections all at the same time, and individually; Nothing seems to help. The file from Sammobile was the Canadian T110UEUAOD1_T110XACAOD1_T110UEUAOD1_HOME.tar.md5, as I bought the device in Canada.
I've even tried setting up ADB and attempting to reboot the tablet into Download mode as another forum instructed. ADB couldn't find the device, and I was stuck there too. I did everything required for the setup, including downloading the entire thing from SDK and setting the environment variables on Windows. ADB does work on my Samsung S5 phone, so it isn't an issue with ADB itself, but with the tablet.
This is a relatively new buy, and thus I really don't want to loose it. I've been trying this for about a week now, and I'm open to almost any suggestions. I've also tried changing computers, changing ports, using official Samsung chargers, etc. If anyone knows anything, even if you regret to inform me that I cannot save the device, it would save me the stress of staying up well into the night searching desperately to fix it. The device cannot boot out of this message, which means no recovery, download, or any other type of actual booting; I've tried removing the battery to prevent the screen from popping up. I'm also given limited time with Odin, as the device doesn't want to charge when plugged into anything but an official Samsung Adapter, and thus I can't spend hours with the tablet connected to the computer.
If this helps, although I'm not exactly sure if it would, here are some specific numbers and information that is listed around the device and on the screen:
Product Name: SM-T110
Current Binary: Samsung Official
System Status: Custom
H/W Version: 0.2
IC: 649E-SMT110
FCC ID: A3JLSMT110