Help pls i have olinex 1.40 hardspl in but my phone is stuck in bootloader with "upgrade ROM code error Please try again" i cant get out...tried hard reset nothing...tried recovery mode (volume down + reset ) nothing...cant get a usb connection help!!!!!!!!!!!!!!!!
are you sure you don't have usb connection? try running an ruu with usb plugged in see if it runs. it sounds like you tried to flash a radio from another device. try flashing a new radio.
Blazeitup123 said:
are you sure you don't have usb connection? try running an ruu with usb plugged in see if it runs. it sounds like you tried to flash a radio from another device. try flashing a new radio.
Click to expand...
Click to collapse
the bootloader shows usb when i plug it in and serial when i plug it out...when hard resetting it goes through the formatting but then just jumps back to bootloader with the message...active sync recognizes nothing but i'll try that right now
edit - ok it seems to be flashing i'm crossing my fingers
edit: ok it seems to have flashed i see my rogers main screen thank you soooooooooooooooo much
glad to hear!
just so you know you can always flash from bootloader. i have seen alot of people around here saying "oh no, my device is bricked and i'm stuck in bootloader". i lol.
Blazeitup123 said:
glad to hear!
just so you know you can always flash from bootloader. i have seen alot of people around here saying "oh no, my device is bricked and i'm stuck in bootloader". i lol.
Click to expand...
Click to collapse
lmao now i know..i was coming from an elfin, not used to diamond as of yet but now i know
Bootloader bottom says "serial" but wont switch to "usb"
Perhaps this is a known issue but I could not find the solution easily and ended up discovering it myself so wanted to share it in case others face the same.
I was try to use the mtty software to "clean" my touch diamond in an effort to get rid of some bugs in macadam 1.2 rom [great rom, by the way].
I had disabled the usb connections in active sync on my laptop [mac running windows xp in bootcamp]
I could enter bootloader easily but the bottom part of the multicolor screen kept saying "serial" and would not switch to "usb" when I connected the phone to the laptop.
What finally worked was ensuring that the phone was set for "activesync" rather than use as a "disk drive" or "internet sharing". I had assumed, wrongly, that once in bootloader the last selected option [disk drive] would be irrelevant.
So I exited the bootloader by pressing the reset key; connected phone to pc via cable; selected the active sync option; disconnected the phone; entered bootloader, connected the phone via cable again and the bottom of the bootloader changed to usb and I was able to use mtty successfully.
I wonder if this has implications for people stuck with bad flashes etc. In my case I could easily exit the bootloader and go back and select 'activesync' from the working phone. One could also hard reset if a working rom was on the phone...
BUT If one is stuck with the option of only the bootloader, would it matter on what the last selected option was [active sync or use as usb disk drive or internet sharing]?
faisal said:
Perhaps this is a known issue but I could not find the solution easily and ended up discovering it myself so wanted to share it in case others face the same.
I was try to use the mtty software to "clean" my touch diamond in an effort to get rid of some bugs in macadam 1.2 rom [great rom, by the way].
I had disabled the usb connections in active sync on my laptop [mac running windows xp in bootcamp]
I could enter bootloader easily but the bottom part of the multicolor screen kept saying "serial" and would not switch to "usb" when I connected the phone to the laptop.
What finally worked was ensuring that the phone was set for "activesync" rather than use as a "disk drive" or "internet sharing". I had assumed, wrongly, that once in bootloader the last selected option [disk drive] would be irrelevant.
So I exited the bootloader by pressing the reset key; connected phone to pc via cable; selected the active sync option; disconnected the phone; entered bootloader, connected the phone via cable again and the bottom of the bootloader changed to usb and I was able to use mtty successfully.
I wonder if this has implications for people stuck with bad flashes etc. In my case I could easily exit the bootloader and go back and select 'activesync' from the working phone. One could also hard reset if a working rom was on the phone...
BUT If one is stuck with the option of only the bootloader, would it matter on what the last selected option was [active sync or use as usb disk drive or internet sharing]?
Click to expand...
Click to collapse
This doesn't make any difference. When you're stuck in bootloader just plugin your USB and the display will state "USB" as well. You can flash a rom at this point.
Related
Please help!
I just upgraded my ROM to Ivan's latest AKU3.5 from bootloader
This completed successfully (100% successful, disconnect and restart etc)
I disconnected and reset, except it was stuck in bootloader mode
I tried the Mtty method (for the first time ever) and followed the step by step instructions...
...after a few seconds a few command lines appeared with "USB>" on the last line
I took this to mean the process had finished (?), disconnected the device from USB and tried a soft reset
the device just stayed stuck in bootloader
next, i downloaded uni_exitbootloader and ran it (as this has worked for me many times in the past). it didn't work the first few times, but i disconnected and reconnected and this time it worked. It said "data sent, you can now reset your device"
This maybe where i went wrong?
I foolishly reset the device before disconnecting it from the USB. The PC immediately said "USB device not recognised" and the screen of my Universal went blank
Now, if i soft reset, it does nothing, i cannot even put it back into bootloader using the camera, on, reset button combination.
HOWEVER, if i press the two soft keys (as if i was going to do a hard reset) i get the white screen with the black text saying "Press 0 to restore etc"
If i press 0, it says "clearing" but the screen just goes blank
If i press x, the screen just goes blank
Now i am completely unable to try and use either mtty or exitbootloader as my PC just says "USB device not recognised" and neither applications run as they should
QUESTION: Have i totally bricked my Universal?!
If not, what can i possibly do...???
As usual, i will be extremely greatful for any advice or assistance to resurrect my favourite Pocket PC!
Thanks in advance for your help.
Aaagh! I think i just realised what i did...
1. I didn't read the posting "For all those stuck in the bootscreen, try the Mamaich method" carefully enough. I didn't realise that the Mamaich method totally erased the ROM!!!
2. By not flashing a new ROM to the device immediately and instead using exitbootloader to exit the bootloader screen i now have a device that has no ROM and probably has no way of knowing how to get into bootloader mode.
Can someone confirm this?
For one, i feel like an idiot for not reading the posting carefully, but having admitted to being stupid,...
... is there anything at all i can do???
Please help...
cancel that, you already said what i was going to ask above
have you try to flash it again with original ROM? sometimes it helps!
Once in bootloader mode, try plugging it into a different USB port, one directly on the PC.
I have had this where one port says not recognised, even after having been plugged in and used for ages, then I go to flash it and it won't work.
Another port has worked for me.
Since you ereased the DOC, all you've got to do now is to reflash the default ROM.
Thanks everyone...
Only problem is, i cannot get it into bootloader mode. And every port i plug it into (so far) says "device not recognised"...
Nevertheless, i did try to reflash the device, but it just gave me the "Error 150" message. It just doesn't know the device is connected i guess?
I think if i hadn't done the Exitbootloader step then i would have been able to reflash it. However, now that i have... i'm a bit stuck... any ideas of other ways to get the device into Bootloader mode?
try
you already know there is a file called EXITBOOTLOADER but did you know that here is a file called ENTERBL ?
try it .....
Thanks dhob187!
Where might i find this file though? Did you mean to attach it?
Just one other question...
How does ENTERBL work if the PC doesn't recognise my device i.e. "USB device not recognised"? Will the application override this and push commands to my pocket pc anyway?
Or is there a way i can get my PC to stop rejecting the device when i plug the USB in?
Thanks in advance,
I believe this is the file u needed
i don't know how this utility works, but just yesterday i stuck in the bootloader after upgrading my uni to AKU 3,5 and solved with ExitBootloader.exe. CMIIW it works the same way, just plug the USB cable then execute the utility (just simple as that).....
but have u tried my earlier suggestion? my friend got the exact problem like you (blank LCD not even bootloader), he was downloaded the original EXEC ROM and try to flash with it (with original upgrade utility also). and the thing start to blink, enter the bootloader and flashing!.....after he manage to wake the device up, then he tried to flash it again with the newest ROM and succeded........
sorry for my english.....
Please don't apologise for your English, thank you for your suggestions!
I didn't quite understand your initial post... but i do now.
Does it have to be the first ROM that it was shipped with or just an original i-mate JasJar ROM?
I can't try it now, but i'm excited to go home and give it a go later tonight... what's more i'm excited at the prospect that there may be some hope for my currently rather expensive paperweight!!!
If the aforementioned doesn't work, i'll try using your attachment.
Cheers again!
it doesn't have to be the first rom that shipped with your imate, just an original one. try your luck then! never give up, keep the faith!!!
sorry, forgot one thing, just ignore the USB error (not recognized) and go for the upgrade (execute the original upgradeUt.exe)
Hi Rudy173.
Thanks for your help, but unfortunately nothing has worked
I have tried running two official JasJar Roms without success... i always get the connection error message (this is surely because the PC always says "device not recognised" when i plug it in).
Also, when i run ENTERBL.exe i just get a failure saying that ...ENTERBL.exe is not a valid WIN32 application... etc...
So unfortunately, i'm still stuck... any further suggestions anyone?
Can the i-mate service centre help me? Is it likely to be expensive?
Back in business )
Wow, not entirely sure what i did... but my Universal is ALIVE!!!
As per the previous post, nothing seemed to be working so i removed Activesync 4.5 beta and reverted to 4.1. I then tried to reflash to an original ROM and the same "connection error" problem happened.
However, next time i tried to enter bootloader, by pressing light, on/off and reset, it went straight into bootloader and i was able to reflash from there
I didn't even need to reflash with an original i-mate ROM. I went straight for Ivan's latest.
This experience has taught me a few things:
1. I have become seriously attached to my Universal!
2. You should never give up hope of retrieval!!
3. This forum is full of very nice helpful people!!!
Thanks everyone.
wow! glad to hear that!
Happy ending....................
i tried to upgrade to new kitchen image but it came up with activesync broken. now i want to revert to another image but does not know how this can be achieved.
is it possible to bring herm100 into SPLv bootloader and have it talk over USB so that a new image can be transferred?
Did you try a soft reset first, then test if you can get AS to connect, then try hard reset.
Do this while DISCONNECTED from the PC.
Sometimes after flashing a new OS, I have lost AS connectivity. A soft reset of the device, or a power cycle reboot always solved the problem.
i tried both soft and hard reset but it does not help. when it tries to activesync then it connects to "'USB" instead to "USB" - note ' before USB.
OK, you can enter bootloader and flash another image through the USB using the RUU.
slimshadee said:
OK, you can enter bootloader and flash another image through the USB using the RUU.
Click to expand...
Click to collapse
Right. Nice one slimshadee.
The other alternative is to flash using SD Card method.
I want to upgrade rom on may diamond but when conect the phone to my conputer the phone it just starts to charge. The computer does not detect him and I have activated usb conection on the phone.
I am using a standard miniusb cable used also for canon fotcamera, Nokia N95, motorola V3 (v360 L6, L7 etc.)
I did instaled Activesync on my computer but still no result.
You did no say which Win OS you are using - If Vista then you do not need activesync (AS) but windows mobile device centre or any other Win OS Before Vista then AS is what you need. AS needs to be installed before you connect your phone to the PC.
Have you restarted your PC first before install - this also helps sometimes
Try this....
Start>Settings>Connections>USB to PC and here ....uncheck the box Enable advanced network functionality
Just a reminder to please use the Internal Method when flashing a new Rom or Radio. Do not rely on your PC as errors occur more frequently.
R3PUBL1K said:
You did no say which Win OS you are using - If Vista then you do not need activesync (AS) but windows mobile device centre or any other Win OS Before Vista then AS is what you need. AS needs to be installed before you connect your phone to the PC.
Have you restarted your PC first before install - this also helps sometimes
Click to expand...
Click to collapse
I am using Win XP SP2 and I have tried every thing that you said but nothing.
band27 said:
Try this....
Start>Settings>Connections>USB to PC and here ....uncheck the box Enable advanced network functionality
Just a reminder to please use the Internal Method when flashing a new Rom or Radio. Do not rely on your PC as errors occur more frequently.
Click to expand...
Click to collapse
I did uncheck that box but without any results so now I will try internal method. But I'll have to send the file to the phone via bluetooth and see if it works.
band27 said:
Just a reminder to please use the Internal Method when flashing a new Rom or Radio. Do not rely on your PC as errors occur more frequently.
Click to expand...
Click to collapse
How much is it supose to take "Internal method"?
After pressing Vol_Down + Back button it showed the three color screen then it changed to a white screen with loading on it and it stays like that (after pressing Vol_Down + Back button I didn't press nothing else).
The Internal Method shouldn't take you any longer then 2 min. or so.
Once you have started the flashing to begin in the Grey menu....it will eventually say OK...OK
and yes
at this stage you soft reset and press vol down and centre round button.
Grey menu then gives you a choice to reset back to manufactures settings which is what you want (vol UP)......this should take an additions 2 min. if that.
band27 said:
The Internal Method shouldn't take you any longer then 2 min. or so.
Once you have started the flashing to begin in the Grey menu....it will eventually say OK...OK
and yes
at this stage you soft reset and press vol down and centre round button.
Grey menu then gives you a choice to reset back to manufactures settings which is what you want (vol UP)......this should take an additions 2 min. if that.
Click to expand...
Click to collapse
I have tried everything that you said and nothing.
The only diference is that now when I conect the cable to the phone it asks me witch mode to conect it (Activesync or storage), but the computer still doesn't see's it.
Tried another USB-cable?
chribruu said:
Tried another USB-cable?
Click to expand...
Click to collapse
I tried with 3 diferent cables.
Have you tried putting your device into bootload mode (soft reset & vol. down) and the connecting to your pc. The bottom of your coloured screen should switch from serial to usb....If this switches to USB then you are good to go with downloading what ever Rom using the RUU_
Keep me posted...
band27 said:
Have you tried putting your device into bootload mode (soft reset & vol. down) and the connecting to your pc. The bottom of your coloured screen should switch from serial to usb....If this switches to USB then you are good to go with downloading what ever Rom using the RUU_
Keep me posted...
Click to expand...
Click to collapse
It doesn't switch's to usb it only shows "serial". If I put it into bootmode while it is conected to USB it shows nothing, not "USB" or "Serial" it's blank.
I am begining to belive that there is a hardware problem in my phone.
Do you have .NET framework installed on your PC! if not, get it from http://www.microsoft.com/downloads/d...DisplayLang=en
Hi all, I have a general problem that I'm hoping someone can help me fix.
I have a Tilt 2, I performed a hard reset back to the stock AT&T rom. I am following the Hard-SPL instructions, but am having difficulties. Here are the steps I have followed:
1) Installed enablerapinew.cab to device and soft reset
2) Am running Rhodium-HardSPL from my PC, while the device is connected via ActiveSync (also showed up in Mobile Device Center as connected on Win7)
3) I am using the Automatic flash button, and I get the first warning dialog just fine. I press Next
4) HardSPL has a list of instructions, saying to make sure that ActiveSync is still connected. This is the part that has the error. When I pressed Next from the previous dialog, the phone goes black, but ActiveSync disconnects from the PC. I have to perform a reset on the device to get it out of the black screen.
I have tried these methods on both a Windows 7 Machine and my Windows XP laptop. It seems that when the phone switches into the black screen, the PC is no longer seeing it as a phone device, so it automatically cancels out activesync.
Any suggestions?
Thanks!
how long are you giving it? When it runs this your phone will reset and go into bootloader mode, so its possible that your phone is just loading. Do any on screen errors pop up?
burtonsnow8 said:
how long are you giving it? When it runs this your phone will reset and go into bootloader mode, so its possible that your phone is just loading. Do any on screen errors pop up?
Click to expand...
Click to collapse
After the first dialog box, the phone goes black and then does nothing unless I use the reset button. I let it sit there for about 10 minutes, and all it did in windows was install a Qualcomm driver. Not sure why activesync cant see the phone once it goes off. I just tried booting the phone up into bootloader by itself and seeing if any drivers installed, but nothing did.
Just tried a different USB port also, same thing.
The drivers it installs into windows when the device goes black are a Qualcomm driver, and HTC USB Sync. Nothing happens after that
try running it while in bootloader.
shut down your phone, hold the volume down and end/power key while using the soft reset button. Once in bootloader make sure it shows you are connected via USB. Run the hardspl.
burtonsnow8 said:
try running it while in bootloader.
shut down your phone, hold the volume down and end/power key while using the soft reset button. Once in bootloader make sure it shows you are connected via USB. Run the hardspl.
Click to expand...
Click to collapse
That did the trick! Thanks buddy, much appreciated!!!
Hello Everyone!
I recently tried to root my wileyfox swift but failed miserably. I did the following when fastbooting the recovery image -> fastboot flash system ****.img.
However, i realized my mistake too late, and now my phone is all messed up!
The phone doesnt show anything when i try to start it and i cant access fastboot again, to undo my mistake. My device manager recognizes my phone when its plugged in to my computer but i cant access any files.
Am i screwed or is there any solution to this?
Thanks in advance!!
Try to access the bootloader with the hardware button combo first (volume down + power / volume up + power). If you get into recovery, you will be able to get to the bootloader with adb or a menu entry. Depends on what recovery you have installed for the latter.
In case you have no access to the bootloader (proper soft brick), go for the QFIL method. Avoid using it unless there is no other option.
Here is the thread:
http://forum.xda-developers.com/wileyfox-swift/general/how-to-set-device-tampered-to-false-t3276317
Cant access bootloader.
However, tried your second option and it went well until i got "SaharaDownload fail" at the last step, and now my computer doesnt recognize the phone in device manager. It does not show anywhere that my phone is connected.
narmista said:
Cant access bootloader.
However, tried your second option and it went well until i got "SaharaDownload fail" at the last step, and now my computer doesnt recognize the phone in device manager. It does not show anywhere that my phone is connected.
Click to expand...
Click to collapse
Does the phone give any indication of being connected? Notification light, starting the display, etc?
If yes, make sure the phone is in the correct mode and check the drivers - some of the other forum members mentioned this and the gymnastics around the battery. This would be on my to-do list. The device might come up on the device manager as different one, so monitor the manager for any changes once you connect the device.
If you happen to have Windows 7 device laying at you house, you can try with it (if only not to worry about compatibility and sporadic Win10 behaviour).
It will be a good idea to check the turkish website for General Mobile 4G (one of the Android one derivatives of the hardware) where some people have faced similar problems using the same tool.
narmista said:
Cant access bootloader.
However, tried your second option and it went well until i got "SaharaDownload fail" at the last step, and now my computer doesnt recognize the phone in device manager. It does not show anywhere that my phone is connected.
Click to expand...
Click to collapse
If you need my help via TeamViewer then WhatsApp me at +27799261595 or pm me
Finally got my phone back on the device manager! However, I still get sahara error when trying the back to false method.
imgur.com/a/FsSX0
*It says no port available since i removed the phone*