Related
Hi,
I was upgrading my XDA Exec using Xda_Exec_Upgrade_v1.30.162.exe
My laptop died. It sometimes overheats but it hadn't happened in a while.
I now can't progress past the bootloader even after full clean reset.
Anyway. I have the O2 screen reading:
R 1.04.01
G 42.37.P8
D 1.13.82 WWE
My laptop detects a USB connection, although it says "USB Device Not Recognised". Activesync 4.1 won't detect it, however, I've tried changing settings etc but to no avail.
I've trawled the board here and found people recovering from similar situations with other devices. Am I gonna be able to restore my beloved exec from paperweight-status?
btw: am in Ireland where O2 don't support the exec and bought it from a guy in the UK who got it as an unwanted upgrade. have flashed it before just fine...but don't think I'll be able to return it to O2 as UK and IRL are not the same company...
Help?
Mark
p.s. ran BL10_RUU_UNI_V11.exe and got 101 connection error :-(
EDIT:
Fixed, using bootloader mode and re-running the upgrade. thanks
xda neo crash
You need to reinstall your windows mobile 5 system. If you are using orginal german neo rom, you can download rom from o2 web site, or you can download from this sites ftp server
thanks for the feedback,
I found the info on restarting in bootloader mode (i had previously misunderstood "bootloader") and was able to re-flash it by USB no probs.
I now have a happy XDA
Hello there ...I have about the same problem with my MDA Vario....could you explain how do I "restart in bootloader mode"?
My PPC just stucks before loading windows...
thanks
How to get bootloader mode
Ok, did a bit of a lookaround and got this (I thinkg the MDA Vario is the XDA Mini)
For Xda II and Xda IIi
- Press & hold the power button
- Press & hold the D pad (5 way directional button)
- Push the stylus into the soft reset hole - until you see the word 'Serial' on the screen.
You should now be able to follow the upgrade process above for a device stuck in Bootloader mode.
For Xda IIs
- Press & hold the power button
- Press & hold the Camera button
- Push the stylus into the soft reset hole - until you see the word 'Serial' on the screen.
You should now be able to follow the upgrade process above for a device stuck in Bootloader mode.
For Xda Exec
- Press & hold the power button
- Press & hold the Backlight button
- Push the stylus into the soft reset hole - until you see the word 'Serial' on the screen.
You should now be able to follow the upgrade process above for a device stuck in Bootloader mode.
For Xda Mini S
- Press & hold the voice command button
- Push the stylus into the soft reset hole (short quick press). Keep hold of the voice command button until you see the screen with multicolored horizontal stripes). The device is now in Bootloader mode and you can follow the upgrade process above for a device stuck in Bootloader mode.
EDIT:
The rest of the process (just in case you need to know) is as follows:
(and if you have problems open your connection settings in activesync and ensure that USB is unchecked...that is OFF. remember to reset the USB settings once you've successfully upgraded)
in 'Bootloader' mode
When this happens the device screen will be blank except for the words;
Serial
v 1.00a
The word 'Serial' should change to 'USB' when the cradle is plugged into the PC, and the version number below this will vary. When you get this screen, a soft or hard reset will not make any difference.
It is still possible to run the ROM upgrade file again, WITHOUT using Activesync (activesync will not restart anyway).
Firstly unplug the USB cradle and reboot the PC
Plug the cradle back into the USB port (this must plug directly into the USB port and not into a USB Hub/adaptor).
Now run the ROM upgrade file again from the PC. This should just run as per normal and correctly reflash the device.
Thanks bob_jesus!!
I am already in bootloader mode....Could you tell me where I can find the files to flash it? My device is Tmobile MDA Vario. Are there different files for flashing for every device? (O2 XDA mini s, MDA Vario, imate kjam...)??
Thanks again
Hi Ermoscow,
I'm sure if you trawl around the boards a bit you'll find it. I'm pretty new to this but yes, all these devices tend to have a different Rom, and each device itself tends to have a different Rom based on your mobile carrier.
e.g. I use an XDA exec which is the same as an HTC universal, they could theoretically use the same Rom but not the same rom as an XDA mini.
Again, this is all in my understanding and keeping it simple.
another idea would be to check the t-mobile site and download your rom directly from them, it should be available. if i find anything for you i'll post back.
Thank you everybody!
After managing to get to the bootloader mode I made a rom update which solved the problem!
Now it works great again!
thanks
Botloader Mode
I have a bricked MDA as I had a power outage while flashing the ROM. Can someone tell me how to recover. I find references to folks entering bootloader mode and then recovering, but I cannot find a post that tells me how to do it. Can anyone help? [email protected]
I'm desperate!
Regards,
Bob
Hi, which MDA is it because the instructions should be included in my post up above. You just need to find which XDA your device corresponds to and go from there. All that info's in this forum somewhere for sure.
Best of luck!
XDA Exec Dead after interrupted Rom Upgrade
XDA Exec Dead after interrupted Rom Upgrade
Hi
I was installing new ROM WM6.1 on autom exec when it rebooted it was showing black screen and just vibrating. as when I hard rebooted it after removing my phone battery and again press the power button it was again showing the black screen and vibrator continues it is not bootng up.
can any one help me please.
How can I reinstall the the old rom using usb
help required....
Please help....
It´s always good to READ the Wiki:
http://wiki.xda-developers.com/index.php?pagename=Uni_ROM_Upgrade
http://wiki.xda-developers.com/index.php?pagename=Uni_Stuck_Bootloader
http://wiki.xda-developers.com/index.php?pagename=Uni_Stuck_Bootloader_Serial
Keys dont work
Hey i just put WM6.1 on my xda exec and it works fine apart from the keys not working so i have to type using the touch screen and the WI-FI randomly turns off and on i was wondering if anyone else had these problems and if they could help.
Thanks
I've also been in the situation that O2 Steath is suspeded when I used MiniSD, It've just run in the blue level and after that it suspended. After I reset it the light of Call and Reject are turned on but the Screen had no sysnal. Could anybody help me to rescue my devide? And what is the problem with my device?
Namnet said:
I've also been in the situation that O2 Steath is suspeded when I used MiniSD, It've just run in the blue level and after that it suspended. After I reset it the light of Call and Reject are turned on but the Screen had no sysnal. Could anybody help me to rescue my devide? And what is the problem with my device?
Click to expand...
Click to collapse
• The device doesn't boot, I see only O2 logo. Hard reset doesn't help and the Firmware update process stops with the first message?
1. turn off the device;
2. enter engineering mode;
3. in Main menu choose Boot Config;
4. in Configuration menu choose EBOOT-Launch Image;
5. turn off the device;
6. now hard reset or upgrade firmware.
Sometimes helps another method: leave the device without the battery for about 30 minutes, then turn your O2 XDA Stealth on.
• How to enter engeneering mode?
1. turn off your O2 XDA Stealth ;
2. hold Flag, OK and Camera + press and hold Power button;
3. use navigation buttons to select the settings.
my stealth cannot boot 2
my stealth cannot boot (black screen, call and End Button are light) after i flash my stealth with wrong ram on miniSD. please any one can help me to recover my Stealth
Hi Dude even i am having tjhe similar problem with my phone, were you able to fix it ? if yes could you please tell me how did you Fix it
Have you READ here?: http://wiki.xda-developers.com/
Good luck,
o2 xda stealth wm 6.5.1
Do any one is having wm 6.5.1 for o2 xda stealth?
Regards
Jay
i'm wating for the solution too hehe
Hi all,
Just received my Vodafone-branded Diamond, and I'm afraid I already managed to brick it!
It was equipped with version "1.37.172.3 NLD" so I decided to upgrade it to the latest version.
The installation of OliNex Hard-SPL 1.93 went flawless, but the installation of ROM "RUU_Diamond_HTC_WWE-ME_1.93.456.2_Radio_Signed_Diamond_52.29.25.12_1.00.25.05_Ship.exe" stopped at about 25% with error code 302. The recovery method that came with the package didn't help, every time the upgrade stopped at the same moment.
Since the device is stuck in the bootloader, and I'm left with a non-chargeable battery, I tried the official Vodafone-branded "RUU_Diamond_Vodafone_NL_1.97.172.4_Radio_Signed_Diamond_52.44.25.24_1.08.25.08_Ship.exe" ROM. Unfortunately, this upgrade stops at 48% and throws the same 302 error.
Anyone who can tell me what I'm doing wrong, and what I can do to solve all this?
I hope I don't have a brand new, but bricked device on Christmas!
TIA and have a nice day.
Try a hard reset first. If this doesn't help google or search at XDA for MTTY.
This tool can fix your device
http://wiki.xda-developers.com/index.php?pagename=Kaiser_Stuck_at_bootloader
Try this, maybe will work
Try a Vodafone branded stock rom before mtty.
Regards,
Carty..
He already tried a stock rom....
Potential Solution
Have you looked at the thread titled,
[UPG][TRBL]How-to fix: Update/Flash doesnt work, stops at 0% or 5% (invalid model ID)
It may just be a model ID glitch that can me fixed.
Take a look. It's in this forum in a sticky by cptsunshine.
Thanks all for the help, I'll have a look at your suggestions.
The problem isn't that it stops at 0% or 5%, it stops at random percentages (depending on the ROM I use).
I also see the bootloader (red / green / blue), so it's not dead. I guess it's just that it doesn't pick up a ROM.
Besides, the bootloaders says upgrade ROM code error please try again.
Edit:
A hard reset doesn't seem to work. In the bootloader, when I press "volume down" and "enter" together, and press the "reset button" the screen goes black, but then goes back to the bootloader screen after a sec or 2.
Edit 2:
MTTY doesn't do much either, after executing "boot" the phone is showing me the Vodafone logo and that's it.
For the rest, MTTY shows me the following:
Cmd>boot
InitDisplay: Display_Chip=1
dwDirectNum: 0, dwMatrixNum: 0, dwMicroPNum: 0
Fixed new dwPSImageSize = 0x53E0000
Install Rom via Internal Memory Method
Steps from Suiller:
1. open from your PC the rar or zip archive and extract only the BIG .nbh file
2. rename as DIAMIMG.NBH
3. copy the renamed file into the root dir of your "Storage Card" or "Internal Storage" (the one of 4Gb... NOT to the internal phone memory!)
4. reset your device and within 3 seconds push together the Vol_Down + Back button (the one on the right above the hangup button) and keep pressed until the boot loader appears (the one with the color stripes)
5. soon as you see the bootloader stop to press those poor buttons
6. a very simple gray menu will appear asking you what to do, simple press the power button to perform the ROM/Radio upgrade
7. while the upgrade runs be patient and don't press again the power button, reset the device or play with it until it finishes, when finished a message "UPDATE SUCCESS" will appear, now you can safely reset your device
8. who prefer can perform a hard reset after the fresh cook (soon after reset simply press Vol_Down + Circle button, then when you see another simple gray menu choose Vol_Up to confirm format), even if this has no-sense because internal memory is pre-formatted during flash, but... there is always a but... for some unknown "scientific" reason sometimes an hard-reset can save time & headache
Let me know how it goes.
Make sure you have Net framework 3.5 installed on devices.
Nakkie27 said:
Thanks all for the help, I'll have a look at your suggestions.
The problem isn't that it stops at 0% or 5%, it stops at random percentages (depending on the ROM I use).
I also see the bootloader (red / green / blue), so it's not dead. I guess it's just that it doesn't pick up a ROM.
Edit:
A hard reset doesn't seem to work. In the bootloader, when I press "volume down" and "enter" together, and press the "reset button" the screen goes black, but then goes back to the bootloader screen after a sec or 2.
Edit 2:
MTTY doesn't do much either, after executing "boot" the phone is showing me the Vodafone logo and that's it.
For the rest, MTTY shows me the following:
Cmd>boot
InitDisplay: Display_Chip=1
dwDirectNum: 0, dwMatrixNum: 0, dwMicroPNum: 0
Fixed new dwPSImageSize = 0x53E0000
Click to expand...
Click to collapse
u can do one thing then press woluem down and reset bottom at the same time then u go to rescue mode then u wait and put in the usb stick and there stand seriel when u put in the cable it will change to usb thenu can load the firmware again
band27 said:
Steps from Suiller:
3. copy the renamed file into the root dir of your "Storage Card" or "Internal Storage" (the one of 4Gb... NOT to the internal phone memory!
Click to expand...
Click to collapse
I wish I could mate, but I cannot put files on it anymore, since ActiveSync doesn't recognize my device when it's in the bootloader.
janielsen said:
u can do one thing then press woluem down and reset bottom at the same time then u go to rescue mode then u wait and put in the usb stick and there stand seriel when u put in the cable it will change to usb thenu can load the firmware again
Click to expand...
Click to collapse
Can you please be more specific? Are you telling me how to do a hard reset? I tried as to do a hard reset, but it goes back to the bootloader instead of resetting. USB stick?
Thanks all, much appreciated. A pain this can happen, looking at the fact that I did everything exactly as described in all these flashing manuals.
Nakkie27 said:
I wish I could mate, but I cannot put files on it anymore, since ActiveSync doesn't recognize my device when it's in the bootloader.
Can you please be more specific? Are you telling me how to do a hard reset? I tried as to do a hard reset, but it goes back to the bootloader instead of resetting. USB stick?
Thanks all, much appreciated. A pain this can happen, looking at the fact that I did everything exactly as described in all these flashing manuals.
Click to expand...
Click to collapse
first push the volum down buttom at the same time press the reset buttom then the 3 color display will appear and in the buttom will stand seriel then u putt in the usb cable to ur phone whit u have attact to ur pc then it will say usb now u can load new firmware
janielsen said:
first push the volum down buttom at the same time press the reset buttom then the 3 color display will appear and in the buttom will stand seriel then u putt in the usb cable to ur phone whit u have attact to ur pc then it will say usb now u can load new firmware
Click to expand...
Click to collapse
No mate, I never had problems getting into the 3 color screen. The problem was updating afterwards, which never completed without error code 302.
Anyway, I guess I just fully bricked my device after putting SPL-1.40.OliNex (according to the guide at http://forum.xda-developers.com/showthread.php?t=416211) on it. The SPL install was succesful, but when booting I'm now not even getting to see the 3 color bootloader. All I see is the Vodafone logo with some version numbers at the bottom, but that's it. It doesn't boot further on, and I can't get a USB-connection.
Edit:
Volume down + reset brought me in the bootloader again, although it's saying SPL-1.93.OliNex.
Nakkie27 said:
No mate, I never had problems getting into the 3 color screen. The problem was updating afterwards, which never completed without error code 302.
Anyway, I guess I just fully bricked my device after putting SPL-1.40.OliNex (according to the guide at http://forum.xda-developers.com/showthread.php?t=416211) on it. The SPL install was succesful, but when booting I'm now not even getting to see the 3 color bootloader. All I see is the Vodafone logo with some version numbers at the bottom, but that's it. It doesn't boot further on.
Click to expand...
Click to collapse
that i know but as i say in the post that when u do it that way i say u can load new firmware whitout it needs to boot try my friend i have done it 3 times because wrong loading of firmware
u have to only push thoose 2 buttom then it will work because u go to rescue mode
But what will that give me extra? I can access the Hard-SPL 1.93 bootloader (3 color screen), and I can get into USB mode. It's just that the upgrade of both firmwares stop at a certain percentage.
I'm constantly trying to hard reset the device, but after pushing the reset button (with both volumn down + enter pressed down), the device just reboots back into the bootloader and doesn't give me the hard reset warning.
Nakkie27 said:
But what will that give me extra? I can access the Hard-SPL 1.93 bootloader (3 color screen), and I can get into USB mode. It's just that the upgrade of both firmwares stop at a certain percentage.
I'm constantly trying to hard reset the device, but after pushing the reset button (with both volumn down + enter pressed down), the device just reboots back into the bootloader and doesn't give me the hard reset warning.
Click to expand...
Click to collapse
u need to hold them down until it leave the 3 color display an turns into grey
Ok, finally managed to do a hard reset. Afterwards I tried upgrading to the official Vodafone NL 1.97 ROM once more, but it failed at 48% again.
Any ideas what to do? I know have Diamond with Hard-SPL 1.93 (which says upgrade ROM code error) with no working OS.
Ok all, got it finally working again!
Don't ask me why, but flashing the newest Dutty ROM (and the included radio) did work.
Thanks for all your help, and a wonderful evening!
Hi all,
I have a quit similar problem. I've read a lot, but couldn't find an answer to my problem - may bye someone can help me.
I updated my Dimond (OliNex Hard-SPL 1.93, radio 1.09.25.23 and rom dutty V4). When I start my phone most of the time (95% plus) I end up in the color screen - however some time it's starts perfect (without changing anything).
When I get stock in the color screen, I can start the phone with mtty and the command "boot".
What can I do to make my phone always start in the normal way?
Thanks!
Nakkie27 said:
Ok all, got it finally working again!
Don't ask me why, but flashing the newest Dutty ROM (and the included radio) did work.
Thanks for all your help, and a wonderful evening!
Click to expand...
Click to collapse
i smell a radio issue - last time i was trying to upgrade my radio - ended up with something similar, managed it out like you did - but now you're up - so that's good!!
try some other rom (this time without radio) - i don't think you should have any issues going forward... good luck and have fun!
Hi,
i've a big trouble.
My diamond has the belite 0.99 ROM, which was installed thanks to the hdSPL 1.34.
I never have any pb changing ROM nor Radio rom too.
But, since this week, i want to change my rom for the AZTOR HD v1 or to change back to stock HTC rom.
But, i can't!
Every time i start the process, my diamond's screen turns into black, the microsoft active sync disconnects, then, the program for changing rom tells me there is a pb of connection!?? (error 238).
So i tried to change my hdspl to olinex 1.38 signed, but same result. Sometimes, when the upgrading program runs, i got a disconnection, or sometimes, the diamond's screen shows the 3 color screen with bootloader information. But, the process for upgrading fails every times!!
Any idea to help me please ???
What about 1.40 unsigned?
http://forum.xda-developers.com/showpost.php?p=2312363&postcount=2
i tried too!
this is really strange!
i have some difficulties to change my hdspl too!
i successfully changed from 1.34 hd to 1.38 olinex, but... i tried so much time and so much methods, i can't remember how i manage this change.
The fact is, to change ROM, or to change SPL, i got same results. Disconnection, black screen or boot loader screen..
Have you tried to flash from the internal storage? therefore bypassing the need to use Activesync.
you need to rename the ROM file (.nbh file) you have downloaded to DIAMIMG.nbh and transfer it to the root directory of the internal storage.
Ensure you phone is charged.
Now you need to hold down the Volume Down AND the "<-" button (the button just above end call) and press the stylus into the soft reset hole.
This will take you into the boot loader, keep the Volume Down, AND the "<-" button's held until you reach a grey screen you will be prompted to press the power button to perform the update to your phone.
Once it reaches 100% it will show "Update Success" and just sit there, at this point perform a Hard Reset, Volume Down AND the circle button and press the stylus into the soft reset hole.
Keep the Volume Down AND the circle button's held and you will be taken to another grey screen, prompting you to press Volume Up to perform the Hard Reset.
Try flash from BootLoader screen. There is Wiki that describe how.
lobsterdave>> thx, i'll try it after work today.
Lord_BlackAdder>> Flash from bootloarder ? where can i find this in the wiki please ?
Is it the same method described by lobsterdave ?
lobsterdave >> thx very much, it worked.
but i was only able to put htc official rom, not the cooked rom from aztor.
But no matter, now i can sell my diamond...
thx a lot, and happy new year to all!
Hi everyone!
I tried to follow the instructions provided in https://forum.xda-developers.com/showthread.php?t=3523595 by @eguif (thanks for providing the instructions!) but with some changes that made my Cube go into a restart loop.
I tried to install Spanish language to my Cube (build 14393), but I used the cabs from a previous Win10 build (build 10586) (don't ask why, I am still trying to understand why I did it...).
Result: Now my Cube starts Win 10 (I can see the logo) and then restarts once and again.
Does anyone have any idea on whether I can recover the device or else will be a nice paperweight??
Many thanks in advance!!
you tried hard reset?
try:
hold power button and volume down together, when vibrate, release power and hold Volume minus until show exclamation mark
connect charger
then press in order: volume up -> volume down -> power button -> volume down.
this works with Lumia phones, don't know if it works with Cube also
Hello Alfra
Alfra said:
Hi everyone!
I tried to follow the instructions provided in https://forum.xda-developers.com/showthread.php?t=3523595 by @eguif (thanks for providing the instructions!) but with some changes that made my Cube go into a restart loop.
I tried to install Spanish language to my Cube (build 14393), but I used the cabs from a previous Win10 build (build 10586) (don't ask why, I am still trying to understand why I did it...).
Result: Now my Cube starts Win 10 (I can see the logo) and then restarts once and again.
Does anyone have any idea on whether I can recover the device or else will be a nice paperweight??
Many thanks in advance!!
Click to expand...
Click to collapse
I'm also trying to understand why you installed .cab files from an earlier version
At the moment I do not know a solution
Thanks both*for your replies.
Still feeling stupid here...*will keep my nice brick for now to remind me not to do it again ?
Alfra said:
Thanks both*for your replies.
Still feeling stupid here...*will keep my nice brick for now to remind me not to do it again ?
Click to expand...
Click to collapse
i did exactly the same with the german language pack (only mainos.production.... file) and ended up in a boot Loop. but hard reset
"hold power button and volume down together until show exclamation mark
connect charger
then press in order: volume up -> volume down -> power button -> volume down." worked fine for me. BUT: dont use this false language pack again because you will end up in the bootloop again. i had to choose english and where able to Setup win 10 14393.
now i´m searching for the right german language pack to install it over the wrong one. maybe then everything should be fine.
so if anybody knows where i can download the .cab files for 14393 please let me know. would be really helpfull
found this
https://forum.xda-developers.com/windows-10-mobile/looking-to-upgrade-cube-wp10-phablet-to-t3523595
thx to eguif
catalog.update.microsoft.com