Related
Hi,
yes - I've read ALL the dead tytn posts and followed all Wiki options but not describe my situation.
I was having a perfectly stable Tytn for the past few weeks, didn't install anything, used it daily with no issues.
Yesterday I decided to reboot to clean the mem a bit (God knows why) and after the restart it simply came on with a blank screen.
The screen shows nothing and the backlight turns on but nothing.
I tried to put it in flash mode and yet the screen remains blank - nothing.
Took the battery out for an hour back in - dead screen.
Did a hard reset - still dead screen.
Tried a sd flash method - still nothing showed.
I even took it apart to check the cables - all in place nothing shows damage or issues or even dirt.
It doesn't show a thing no matter what I try,
ActiveSync is not connecting and all rom flashers fail to connect (error 260).
Tried mtty but didn't get the usb> prompt (just cmd>)
The wierd part is that it still recieves calls from time to time.
Did anyone face this or know of any solutions?
PLEASE HELP! This is so sad...
giliav said:
Hi,
yes - I've read ALL the dead tytn posts and followed all Wiki options but not describe my situation.
I was having a perfectly stable Tytn for the past few weeks, didn't install anything, used it daily with no issues.
Yesterday I decided to reboot to clean the mem a bit (God knows why) and after the restart it simply came on with a blank screen.
The screen shows nothing and the backlight turns on but nothing.
I tried to put it in flash mode and yet the screen remains blank - nothing.
Took the battery out for an hour back in - dead screen.
Did a hard reset - still dead screen.
Tried a sd flash method - still nothing showed.
I even took it apart to check the cables - all in place nothing shows damage or issues or even dirt.
It doesn't show a thing no matter what I try,
ActiveSync is not connecting and all rom flashers fail to connect (error 260).
Tried mtty but didn't get the usb> prompt (just cmd>)
The wierd part is that it still recieves calls from time to time.
Did anyone face this or know of any solutions?
PLEASE HELP! This is so sad...
Click to expand...
Click to collapse
the cmd> prompt means its in bootloader.
question is... have you put Hard-SPL on this device.
Hi,
Thanks for replying.
Yes I did - I've put your outstanding hard-spl 2.10 (http://forum.xda-developers.com/showthread.php?t=296722) on it and it worked great.
Can I use the CMD to somehow re-flash or do something else?
You think it's software related?
Obviously I'm a n00b I just got my 8525 yesterday, right away I upgraded to WM6 went all day today with it working fine, I installed a PockMSN and Windows Live anyways to keep it short I FIGURED I WOULD just RE-INSTALL Windows Mobile 6 to get a fresh phone (didnt know hard reset did the same) Actually it was the 3rd time I flashed the OS and RE-UPGRADED to WM6 to get a fresh phone!!!!
~heres the trouble~
In the middle of the reinstalling WM6 I accidentally reset my computer, didnt realize it right away and, got ERROR 260 I believe, anyways I followed the directions, took out the battery and reset, plugged the USB back and RAN the Offical WM6 Rom of HTC site again and it keeps getting stuck EVERYTIME at 11%, I have tried it like 10 times and it gets stuck at 11%, and I get the same ERROR. Says Communication error 260. I have tried everything I know reset the computer, changed USB cords, and Nothing, everytime it gets stuck at 11%!!!!!!
Any Ideas about how to get my 2 day old Hermes back??
(I know i did a n00bish thing and I am sorry)
same place everytime!!
I tried to reinstall Active Sync, changed USB cables, switched USB ports, nothing!! I keep getting ERROR 262 (thought it was 260 at 1st) and wont get past 11% says no connection. I do notice everytime i try this process, Active Sync isnt connected, but the Hermes is connected to the computer! Cause if it cant read the hermes it wouldnt be able to even start the update process. But 11% everytime its stops
nicknowsky said:
I tried to reinstall Active Sync, changed USB cables, switched USB ports, nothing!! I keep getting ERROR 262 (thought it was 260 at 1st) and wont get past 11% says no connection. I do notice everytime i try this process, Active Sync isnt connected, but the Hermes is connected to the computer! Cause if it cant read the hermes it wouldnt be able to even start the update process. But 11% everytime its stops
Click to expand...
Click to collapse
Perhaps you could try to flash using the sdcard method. So you would not be connected to a pc anymore. Who knows, it could solve your problem. I know one case where installing an official rom cured also a similar problem.
Quick summary of the sdcard method:
Use an empty sdcard formatted in FAT32
Copy the RUU_Signed.nbh file containing the OS to the card and rename it: hermimg.nbh
Enter bootloader mode (OK + POWER + Softreset). Normally, after the 3colors screen, you will get "Loading" followed by a description of what is on the card.
When ready, press power and... wait...
Good luck (The phone is NOT connected to the pc)
sounds good but I dont have a MicroSD card reader to do that. And I am using an Offical HTC WM6 ROM, thats all I ever used was the offical WM6 Rom from the AT&T site. Like I said, I was able to install WM6 already, but me being a complete idiot was Flashing the upgrade ROM to get the Hermes back to fresh phone factory settings. But I accidentally reset the computer in the middle of Flshing and since then I have never been able to get it to install again, everytime I turn on the phone I am stuck at the Tri-Color Screen, I am able to restart the upgrade process, but it stops at 11% says ERROR 262 and no connectivity!!
please anybody knows anything, this is the only thing I got, my mom got it for me! We cant afford to get a new one, or even fix it, it was a special present!
nicknowsky said:
please anybody knows anything, this is the only thing I got, my mom got it for me! We cant afford to get a new one, or even fix it, it was a special present!
Click to expand...
Click to collapse
Ok. I am a bit annoyed if you cannot try the sdflash method (BTW you can ask somebody having a PC to prepare the card for you.)
There are different things you can flash on your hermes. Radio, OS, Splash screens, Extended Rom,.... The most tricky thing is the radio rom as a failure there has a higher probability to brick your pda.
This is why i believe it is very dangerous to flash right away without some readings and understanding about what you do. i hope you had some experience here.
Did you first install hardspl (olipro 2.10 )? This is not mandatory but is a very good protection against bricking. (here the excellent guide of mrvanx: http://www.mrvanx.org/cms/index.php?option=com_content&task=view&id=30&Itemid=27 )
Did you flash also a radio rom? (Was it included in the "package" you wanted to flash?) If yes, i am a bit anxious that a stop at 11% is a problem... BUT, if you flashed a radio rom, it goes very, very, very... slowly. And gives the feeling that it freezes. For the "radio" part it is normal . I hope you did not stop the process too soon.
Once again, try the sdcard method. Or try to flash an official rom (most of the time containing a radio part...) and be patient. Can take till 25 minutes.
If this does not work, do not panic yet. Others had also problems before you: go there and start reading : http://forum.xda-developers.com/showthread.php?t=286755 and here http://wiki.xda-developers.com/index.php?pagename=Hermes_Unbrick
There is a hope to solve your problem. Good luck
Try to flash a radio ROM, turn the device on and if it stays at the bootloader screen (the tri colour screen) make a note of the version displayed. Hook up the device with USB cable, dont worry about activesync.
Download and unzip a radio ROM upgrade (try this one), run the exe, select your bootloader version on the screen....follow the screens through and see if it works.....radio roms take ages to flash so DO NOT disconnect your device.....if it doesnt work you most likely have a corrupted radio bootloader.............which is likely since the radio flash takes the longest ammount of time the reset probably occurred halfway through this.................unlucky
Give it a try though.
The lesson to learn here is to READ THRICE and flash once.....never ever disconnect your device out of impatience (which i suspect has happened many times on a radio flash) and be carefull these devices are expensive
mrvanx said:
The lesson to learn here is to READ THRICE and flash once.....never ever disconnect your device out of impatience (which i suspect has happened many times on a radio flash) and be carefull these devices are expensive
Click to expand...
Click to collapse
I could not say better
I know, the MicroSD method is nice, but when I got the phone the guy gave me a MicroSD card, but not the regular SD card to read it on computers ( i do have a card reader) Guys a super appreciate the replies> I am gonna try everything rite now, but real quick is my Hermes FUCT??? or is this error fixable??? It is just losing communication everytime at the exact same place, it just seems like something is fixable, but my sorry luck i cant get over the hump!! I will let ya'll know ASAP
okay, here is the thing, Every Hermes ROM update utility I have downloaded wont work, i start it and the VERIFY INFO ON HERMS windows appears about 2 minutes late I get ERROR 260 and it exits! Now when I use the OFFICAL WM6 upgrade ROM from the ATT/HTC site it seems to read the HERMES and wanna start the upgrade process, but thats where it ends at 11% No other RUU I have used or tried has even gotten that far, I just get ERROR 260 before it starts and I have to exit.
What it looks like is I cant communicate with my HERMES at ALL!! Active Sync wont see, only when I reset my computer and reset the HERMES and I plug it in a different USB port, it says Installing New Hardware and HTC USB something and then Hardware has installed and is now ready to use. But Active Sync wont recogniZe it
I'm sorry to tell you that but i think you ****ed up your phone and it is as useless as my ****ing jasjam.
please give us some detailed info s about your hermes like IPL SPL GSM STATUS....
When I am in Tri Color Mode I see.......
HERM100
IPL-1.04
HERM100
SPL-2.03
and SERIAL at bottom, then USB when I plug it in to my computer
I had upgraded to WM6 before on it, but me being a impulsive FOOL, i flashed it again to get me back to Factory Setting (didnt know HARD RESET did the same) and I accidentally RESET my computer in the middle of ROM Upgrading and ever since I cant get past 11% when I try to do it again (using the OFFICAL WM6 ROM from HTC)
and I cant get any communication with mtty although I dont know much about that app, I get a CANT load screen appear
is your phone KITL enabled.
hold the COMM manager button + POWER button + OK button (the one on the left side under the jog wheel) and reset with stylus.
if you see KITL dialogue then it is KITL enabled (MY bricked jasjam is KITL disabled)
if it is KITL enabled then read : http://wiki.xda-developers.com/index.php?pagename=PB_KITL_HERMES and your phone will be just fine.
if it is not then your phone is ****ed up just like mine
HA HA, me and my phone guy (well the guy who I bought my Hermes from) HAVE FOUND A FIX to get the phone outta Bootloader Mode and back into OS!! in my case WM6!! I have to do it 1 more time to fully confirm the method!!!!!!!! My friend is calling "SHOCKING THE PHONE" but not really shocking anything!! I am reluctant to share the method, but this site needs more people to actually HELP out others
nicknowsky said:
HA HA, me and my phone guy (well the guy who I bought my Hermes from) HAVE FOUND A FIX to get the phone outta Bootloader Mode and back into OS!! in my case WM6!! I have to do it 1 more time to fully confirm the method!!!!!!!! My friend is calling "SHOCKING THE PHONE" but not really shocking anything!! I am reluctant to share the method, but this site needs more people to actually HELP out others
Click to expand...
Click to collapse
Hey dude!
Would you kindly provide me the sulotion.
I would appreciate it.
nicknowsky said:
HA HA, me and my phone guy (well the guy who I bought my Hermes from) HAVE FOUND A FIX to get the phone outta Bootloader Mode and back into OS!! in my case WM6!! I have to do it 1 more time to fully confirm the method!!!!!!!! My friend is calling "SHOCKING THE PHONE" but not really shocking anything!! I am reluctant to share the method, but this site needs more people to actually HELP out others
Click to expand...
Click to collapse
Mmm... do i understand correctly your post? Are you hesitating to help others because your method is risky, or because you express some exasperation about people on this site? In this case, do not forget that all people here are exchanging ideas, questions etc on a totally free base without any obligation. In the limits of there knowledge. Encountering a problem after flashing a device is the only responsability of the user. We just try to help. But i prefer to believe that you found a method, still risky, that you need still to test
That said, it seems that there are an increasing number of hermes encountering a problem with the radio part. It seems that stopping a flash at 11% is a symptom of that. See some consolidation of those problems here: http://forum.xda-developers.com/showthread.php?t=349461
I hope you will find a solution for your problem and moreover i hope that none of you bought a hermes second hand with an already radio part problem. If so try always to get your money back...
I AM trying to confirm my method BEFORE i share it, because it might work on mine, and I dont wanna screw anyones hermes up more
nicknowsky said:
I AM trying to confirm my method BEFORE i share it, because it might work on mine, and I dont wanna screw anyones hermes up more
Click to expand...
Click to collapse
Why don't you answer my PMs????
Please tell me your sulotion and let me try that if you have any
My phone was working fine for sometime with DCD 3.1.2, SPL 2.40 and radio 3.39.10. Last week it starting randomly resetting when I would slide open the keyboard. Not always, but quite annoying. The past few days it started getting stuck in the bootloader on initial start. I would reset it, remove the battery, etc. Still it would go to the bootloader. I even tried the exitbl utility and although it sends the data and executes the reset, it still goes back to the bootloader. Screen says:
TITA100 MFG
SPL-2.40.Olipro
CPLD-9
I figured it was a bug with the rom or whatnot, so I (microsd) reflashed it with the latest official Sprint rom. It still goes into the bootloader. If I hit the reset button enough times, it will occasionally boot up. No idea what's goin on here. Don't understand how it could be random either.
Any ideas?
do you have the wire that you plug in for headphones?
it's the headphone/ USB plug?
if so plug it in and just push the soft reset button
it should work
Ok, that worked like a charm, thanks!
Question is it still enters the bootloader when I reset or turn off/on the phone without the adapter. Should I reflash the bootloader?
i have found no info pointing towards what is doing it. i've re-flashed with no luck
Is there a way to flash the bootloader off just the memory card? Can I copy the Hard_MFG_SPL_2.40_RUU_signed.nbh file to a card and rename it?
Figure it's worth a try.
I've got the exact same situation as you guys... Just wanted to chime in on it.
cpujunky said:
Is there a way to flash the bootloader off just the memory card? Can I copy the Hard_MFG_SPL_2.40_RUU_signed.nbh file to a card and rename it?
Figure it's worth a try.
Click to expand...
Click to collapse
i think i read on another forum that you can not flash off the memory card for a bootloader.. but i do not know
Try a hard-reset and then flash to another pre-built or Kitchen built ROM that uses the 2.40 bootloader.
You must boot into the WinMo OS and get connected with Activesynch to program a bootloader. At least none of us have yet managed to figure another way to do it.
Is there a way to flash the bootloader off just the memory card? Can I copy the Hard_MFG_SPL_2.40_RUU_signed.nbh file to a card and rename it?
Figure it's worth a try.
Click to expand...
Click to collapse
Do NOT, I repeat do NOT attempt to update the SPL with the memory card. The unlockers are developed to first load a temporary bootloader, then flash with an RUU once using the temporary. You will mess up your phone.
Thanks... I was having the same problem that the OP was having until I found this thread. It seems like headphone adapters other than the Sprint one works. Also, if you're stuck in the bootloader, there is no reason to flash any roms because it will have no effect at all.
Also, as an alternative, you can take out the battery for a couple hours.
By the way, I'm running dcd 3.1.2 and radio 3.37
So we know that flashing a new ROM doesn't work, and flashing different radios doesn't work. We also know the headphone adapter will get you to boot up normally, so no stuck buttons or anything. This has to be a bootloader bug or phone defect or bent usb pins or something. Has anyone tried relocking the phone? I can't express how annoying it is to carry around a headphone adapter in case you need to reboot.
Thinking,,,,,
I stopped where you see in my signature as everything works for me, but I wonder if maybe you flash back to stock, relock, put it back exactly as you started if that would straighten it out. If it still fails stock then some nice new defect has been found. If it works then go forward but only as far as I did ans see if it is stable as with mine,,,,,maybe somthing in the new ROMs???????
cpujunky said:
So we know that flashing a new ROM doesn't work, and flashing different radios doesn't work. We also know the headphone adapter will get you to boot up normally, so no stuck buttons or anything. This has to be a bootloader bug or phone defect or bent usb pins or something. Has anyone tried relocking the phone? I can't express how annoying it is to carry around a headphone adapter in case you need to reboot.
Click to expand...
Click to collapse
i have relocked also. i've think i've done everything except rip the phone apart and look at the usb pins
This is not a rom issue, it's a bootloader issue. I've flashed, tested, and used all released roms and non-released (internally tested) roms numerous times on several different titans and have never seen this issue. I'm not doubting the existence of the issue, but the rom will have nothing to do with the device being stuck in the bootloader.
My guess is that something went wrong while unlocking or it's a hardware defect on a certain batch of these phones.
there was some talk over at ppcgeeks about there being something about relocking and flashing and something... however. my phone worked great and then one day it just started and nothing changed on the phone for like 3-4 weeks and then it started going to bootloader
This weekend I replaced the stock bootloader on my VZW XV6800 with SPL-2.40.Olipro; upgraded radio to 3.39.10; installed dcd's Titan 3.1.2. All went well, phone was doing fine for a couple days.
Today the battery died, nothing unusual. I plugged in AC power and turned on the phone and the bootloader displayed. Did a soft reset 2 or 3 times, no change. Disconnected AC, popped out the battery, let it sit while I search and found this thread.
I used a can o' air to blast out the USB/power port on the phone. Put in the battery, powered the phone, and the OS loaded just fine. Soft reset the phone and again could only get to the bootloader. Poppped out the battery again, found my USB/headphone adapter, connected it, returned the battery and powered the phone, and the OS loaded just fine.
This is a long way of saying I'm experiencing the same that's been reported in this thread. Is there a fix for this issue? It seems like an issue with the device to me. Was there any confirmation that there was a "bad batch" of phones and is a hardware issue with the XV6800?
I am also experiencing this same problem.
I flashed to 3.1.2, then to 3.2.0 today...nothing changed. It still loads the bootloader when i do any kind of a reset without the usb or the headphones plugged in.
The only odd thing that i can comment on during my experience is that my USB cable failed on me and I had to replace it. Seems odd, but perhaps that can shed some light on the problem.
Did anyone find a solution to this problem? Is it a hardware issue?
hey guys ...
there is the whole story
My friend's HD2 device was working in strange way, When restarting it gives a white screen and the HTC logo and freeze at this screen and then after a large number of re-starting it works, but when re-restart it again it return to the white screen
After a Hard Rest through the sound buttons the top and bottom were formatted but the device remain standing at the white screen after a Hard
the only solution to me was upgrade to new Rom and after read in the forum that This problem can be a lack of Compatibility between the Rom and the radio, but I think that the device had not been updated b4 by a lack of awareness of my friend, and then check the SPL version ,it was 1.42.000 (still locked) then try to ulock it by HSPL2_RUN as posted in some thread
it done right and the message "we hacked .." and enter boot-loader and checked it became 1.42.spl then I tried to upgrade by the following Rom:
RUU_Leo_HTC_WWE_GCC_1.43.488.1_Radio_Sig ned_15.26.50.07U_2.04.50_22_2_Ship
When updating the device whenit reached 9% did not complete the upgrade untill the upgrade process stopped by itself so I did restart the black screen appeared within a triangle inside the exclamation point.
now I started to be panic, and then search the net and found the advice from someone to use Task29 before the upgrade and when I run the program worked fine and after restarting the white screen returned with the HTC logo inside
I tried again to upgrade the same Rom and returned the same result ,searching again and found many advise to upgrade the SPL to version 2.0 which is recommended by most members
After the successful conversion of the SPL took off the device and swithched to boot loader to make sure the validity of conversion and the back of the version then after restating the white screen appeared and when I tried to reboot again the device turned off, I tried several times and did not work I said maybe the battery and when i connect the charger it did not ship and the orange led did not spark, tried the USB method but same result
I tried another charger and a another usb cord and it did not work and I check the battery by an electronics specialist, He assured that the battery is fully charged.
And now the device does not function at all, not even shaking when running and screen or charging
please guys i need ur argent assistance ...even a thought may help
Note: This is not the first time for me unlocking and flashing thin , my last devices was: JAM - k-jam - Jazjam - Omnia (current)
king roro said:
hey guys ...
there is the whole story
My friend's HD2 device was working in strange way, When restarting it gives a white screen and the HTC logo and freeze at this screen and then after a large number of re-starting it works, but when re-restart it again it return to the white screen
After a Hard Rest through the sound buttons the top and bottom were formatted but the device remain standing at the white screen after a Hard
the only solution to me was upgrade to new Rom and after read in the forum that This problem can be a lack of Compatibility between the Rom and the radio, but I think that the device had not been updated b4 by a lack of awareness of my friend, and then check the SPL version ,it was 1.42.000 (still locked) then try to ulock it by HSPL2_RUN as posted in some thread
it done right and the message "we hacked .." and enter boot-loader and checked it became 1.42.spl then I tried to upgrade by the following Rom:
RUU_Leo_HTC_WWE_GCC_1.43.488.1_Radio_Sig ned_15.26.50.07U_2.04.50_22_2_Ship
When updating the device whenit reached 9% did not complete the upgrade untill the upgrade process stopped by itself so I did restart the black screen appeared within a triangle inside the exclamation point.
now I started to be panic, and then search the net and found the advice from someone to use Task29 before the upgrade and when I run the program worked fine and after restarting the white screen returned with the HTC logo inside
I tried again to upgrade the same Rom and returned the same result ,searching again and found many advise to upgrade the SPL to version 2.0 which is recommended by most members
After the successful conversion of the SPL took off the device and swithched to boot loader to make sure the validity of conversion and the back of the version then after restating the white screen appeared and when I tried to reboot again the device turned off, I tried several times and did not work I said maybe the battery and when i connect the charger it did not ship and the orange led did not spark, tried the USB method but same result
I tried another charger and a another usb cord and it did not work and I check the battery by an electronics specialist, He assured that the battery is fully charged.
And now the device does not function at all, not even shaking when running and screen or charging
please guys i need ur argent assistance ...even a thought may help
Note: This is not the first time for me unlocking and flashing thin , my last devices was: JAM - k-jam - Jazjam - Omnia (current)
Click to expand...
Click to collapse
Hi,
Since you have enough experience in flashing custom ROM, I would suggest you the following ways:
1. Make sure battery is at least 50% and the battery pins are not bent
2. Format your micro sd card to fat 32
3. Find and download the CORRECT STOCK ROM. You can download it from htc website if your hd2 is non branded, or you can download it from your carriers website if your hd2 is a branded one. Make sure the downloaded file is not corrupt due to download process
4. Extract the downloaded file using 7 zip or winrar. Find the file named: RUU_signed.nbh Then, rename it to: leoimg.nbh then copy it to the root directory of your micro sd card
5. Go into boot loader and follow the onscreen instruction. If therenis no hardware issue, it should work.
Good luck ...
thanks m8 but I've checked the pins and changed the battery with fully charged one ..
but it's no boot loader mode ... its completely off
thanks 4 ur support
Not offering solution, just an observation,,,, hanging at HTC screen and only occasionally booting, plus flashing hanging at. 9% is a bad sign, sometimes associated with a stuck radio, and/or/caused by thermal issues.
Try chilling the phone with stock nbh ready to go on SD card, in sealed bag in fridge/freezer for a while, then try to SD flash.
If flashing starts, (white screen blue writing) keep an eye out for "rsa radio fail" or similar.
if the flash goes well, but then later the problem returns, it's pretty conclusively hardware.
thanks buddy for the advise but as I mentioned b4 ...
the device doesn't boot anymore ... and yeah it's Hardware bug I think.
best regards
Hi, I unfortunately don't know a lot about what I am doing here (the root of all my trouble), I'll try to get the info straight:
Motorola Droid Razr (XT910), bought in Dubai, using it in UK, so I didn't receive OTA updates. I decided to try update to ICS using RSD Lite, but the flashing got stuck at system_signed. I gave it a lot of time (hours) before I switched off the phone and tried again, which is when things started going haywire:
During my following attempts, the battery ran low, so I couldn't go on trying (soft brick). I made a patched "factory cable" as per instructions in this forum somewhere, the cable works and powers the phone for flashing.
Now all it does is coming up with the fastboot screen, which reads:
AP Fastboot Flash Mode (S) (Flash Failure)
0A.6C
[...]
Device is LOCKED. Status code: 0
Battery OK
OK to Program
Transfer Mode:
USB Connected
...which suggests to me it would be ok to be flashed, if only I could get it to accept the files. Being a big numpty, I am unfortunately not quite sure what was the exact version that was on there before (big mistake, I know that now), it was 2.3.6 and I suspect it must have been a MEA version, since it was bought there(? - also, when I first switched it on, all was in arabic).
What I have tried so far was:
* using several different fastboot firmware files with RSD Lite 5.7, all of which do not get over the step '1/xx flash cdt.bin "cdt.bin_signed"' - it just hangs supposedly "In process..." forever. I noticed all of these have an "ota" folder (although they vary considerably in size between <1 and 2.5 GB) - maybe all the ones I downloaded are only updates? Is there an actual, base operating system image somewhere?
After many failed attempts, I got desperate and tried files for different regions at random. The ones I tried so far:
SPDREM_U_01.6.5.1-73_SPU-11-M1-2_SIGNEuropeAustraliaEMEA_USASPDRRTGB_HWp2b_Service1FF_fastboot.xml
SPDREM_U_01.6.5.1-73_SPU-11-M1-2-ULB_1C.85P_0A.6B_DATDE_CFC_HWp2b_SIGNED.xml
SPDREM_U_01.6.5.1-167_SPU-15-M2-3_SIGNEuropeAustraliaEMEA_USASPDRRTGB_HWp2b_Service1FF_fastboot
SPDREM_U_01.6.7.2-180_SPU-19-TA-11.6_SIGNEuropeAustraliaEMEA_USASPDRICSRTCEE_HWp2b_Service1FF_fastboot.xml
SPDREM_U_01.6.7.2-180_SPU-19-TA-11.6_SIGNEuropeAustraliaEMEA_USASPDRICSRTGB_HWp2b_Service1FF_fastboot.xml
SPYDERIRD_U.01.26.0_SPD-IRD-21_SIGN_ASIA_RETAIL_HKTW.xml
SPYDERIRD_U.01.26.0_SPD-IRD-21_SIGN_MEA_RETAIL.xml
The only thing I am quite sure about is that it is not LATAM.
* I tried manually flashing the various image files with moto-fastboot, fastboot, and eprj-mfastboot, both the Windows and the Linux versions, with pretty much always the same result: it would flash some files (e.g. ebr, mbr, devtree), but not what I think are the crucial ones: boot, system, also logo.bin. As there are so many possible combinations, I have not tried every file from every firmware I downloaded with every possible program, but as far as I can tell, the results were the same. I did get some error messages about signing (indicating wrong region) sometimes, but most of the time it just hangs forever while supposedly transferring the files.
* I also tried the DroidRAZRUtility, both 1.51 and 1.6, which both invariably fail at the first step of flashing the "allow-mbmloader-flashing-mbm.bin" file on there.
So, I am out of ideas now. Please, someone tell me I have overlooked something obvious. Also, please tell me I haven't bricked the thing for good.
Is there not a way to write something new into it's memory on an even more basic level (I am thinking Linux' dd here), or to read out which region it is currently locked to? I repeat, all I get is the Fastboot screen, I can get into the Fastboot menu, but none of the options gets me anywhere else, (stock) recovery does not work... My last idea is that it might still be a power issue despite the "factory cable", and to try and crack it open and power it at the battery contacts for flashing - but the fact that some flashing works, and the other files don't fail because it goes dead, but because it rejects them, suggests to me it is not a power problem.
Any suggestions appreciated, thanks!
Try flashing SPDREM_U_01.6.7.2-180_SPU-19-TA-11.2_SIGNEuropeAustraliaEMEA_USASPDRICSRTGB_HWp2b_Service1FF_fastboot
with rsd lite.
Those failures are because of two things:
1. You are trying wrong sbf for another region
2 and/or you are trying to flash an older firmware.
Please note that now your only bet is to flash ICS firmware, and try various regions untill you find your right one.
Also if you manually flash use eprj-mfastboot , others fail to flash corectly.
Again for the power issue, when RSD throws an error , look at the phone, if it says "Low battery, cannot program" then the factory cable is bad, if not there is no power problem.
Don't worry your phone is not dead, you only need to find the correct sbf file, try more variants with rsd lite, it must work.
Mine had problems flashing correct sbf's, it was my system. Even with correct drivers and lastest RSD it would not work, nor with my other laptop, but working fine on my old xp install on a macbook. I could however install stuff individually using fastboot flash command. Sorry that I dont have a solution but I just wanted to let you know that sometimes it can be your computer/os install.
still trying
@Killer2k8: Thanks for the encouragement, I will try with the file you suggested with eprj-mfastboot.
As per power: I seem to have tried so many times that the battery is way deeply uncharged (I hope it isn't permanently damaged once I get the phone to charge at all again), so anyway, I crack'd'er open and tried powering directly at the battery contacts (battery disconnected, of course). As you would guess from what you wrote, that did not make any difference to my problems... But also, it proves my factory cable is good, as I can even flash the few files that work if no power is connected at the battery contacts, powering through the cable only. Some files will transfer correctly, and when it says "writing", the phone will just reboot, causing an error - that's why I thought of power issue, e.g. the actual flashing process requiring more power than just the transfer... Anyway, that issue did not go away even with direct power. - Will see what happens once I find the right files for me...
I'm good with flashing ICS, that's what I wanted to do in the first place. And thanks for the encouragement!
@drolgnir: Thanks, I had the same idea, as initially I had tried everything from Win7 running in VirtualBox (at first, I only found all the tools for Win, should've really researched better before starting this), I thought maybe it doesn't have the proper low-level access to the USB ports. Anyway, since trouble hit me, I tried also on three different Linux machines (2 different dirtros), and also again on the virtual Win, and on many, many different USB ports on these (just in case it was a USB power issue), all to no avail. I guess Killer2k8's suggestion sounds most promising at the moment... Cheers anyway.
no luck - situation deteriorating..?
Sorry for the many posts, I hope someone is still reading this...
So, I tried the file you suggested. I flashed manually, not RSD, with "fastboot" from eternity project, which is the Linux equivalent to "eprj-mfastboot.exe", as far as I can tell (download from the same post as the Win version).
I could flash cdt.bin, ebr, mbr. Note that these are all just 16kB.
When trying logo.bin, it sent it ok, but during 'writing logo.bin...', the phone just switched off. After restart, same again. Same also with boot_signed.
Since then, things got worse: whenever I try to switch on now, it flashes ~1/4 of the red "M" logo, then flashes the AP fastboot screen, and repeats that a few times before staying off (sometimes not, just switches off right away). I can still get into the Boot Mode Selection menu by holding all three buttons, but selecting AP fastboot there has the same effect. Starting with power&Vol- button shows the fastboot screen immediately, but again only for a flash...
The only thing that will stay on is the SBF Flash screen, but I don't know what to do with that..?
So, I still smell a power problem, but neither applying external power, nor using the factory cable alone made a difference. The cable is ok, I re-checked. The fact that the SBF Flash screen stays on suggests that it is not a stuck power button (someone had that problem, apparently), am I right?
So, any suggestions from here? Thanks..
Although this doesn't help, I have pretty much the exact same issue. However, I do know what/where my phone is from, it requires the central Europe update. But apart from that the issues are identical; it only boots into the flash failed fastboot menu, and any RSD attempts have failed at cdt.bin, while using the fastboot tool does not work either as I get preinfovalidation flash errors. The utilities don't work either.
Now, as you did, I also tried quite a few different versions of the firmware, and none of them worked. So what I was wondering is, is there a way for us to find out exactly what version the phone 'thinks' it is on, so we can find the same/a newer version of the firmware to update it to? Because I am quite certain I am using the files from the right region, so it must be the version that is too old.
update: still struggling, but giant leap further! Please read my tale...
...just in case anyone might find this useful, I'd like to give an update on my "patient":
I actually managed to flash ICS on there! Kind of.. What I did, was:
With the battery unplugged, I supplied external power to the phone, additional to the factory cable. The issue was that it would often flash small files, but for larger files would successfully "send" them, but in the "writing" phase the phone would just switch off. So, I supplied carefully monitored 3.7V to the contacts, which seemed to make a difference, but in the "writing" phase, Voltage dropped to below 3V where it would again switch off. Ok, you can charge a LiIon battery with max. 4.2V, and you should normally charge the battery before flashing, so I tried again while providing 4.2V. And - Success!! Voltage would drop to ~4V during "writing", but it stayed on, and allowed me to further test which Firmware the device would actually accept.
I do not believe that applying 5V from an USB cable directly to the (plugged-in) battery contacts, as mentioned in the forums somewhere, is very healthy for the battery. I reconnected the battery and tried charging it directly from the contacts, but I made sure the Voltage would always stay below 4.2V. Occasionally in my exploits, the charging circuitry would actually spring into action (confirmed by a drop and fluctuations in Voltage, and the faintest of noises from the phone itself), and I used that of course to squeeze some life back in, but most of the time it would not charge at all. I can not say what combination of flashing attempts, rebooting, un- and replugging the cable, switching and changing the charging current,... actually triggered the charging process occasionally, sorry. I could not reliably reproduce it.
In the process, I also tried the DroidRazrUtility 1.8, which interestingly flashed the AP fastboot to v 0A.74, but of course failed further on...
With the new AP fastboot, I thought maybe something more might now work, and at last I found it would now miraculously accept:
SPDREM_U_01.6.7.2-180_SPU-19-TA-11.6_SIGNEuropeAustraliaEMEA_USASPDRICSRTGB_HWp2b_Service1FF_fastboot.xml and
SPDREM_U_01.6.7.2-180_SPU-19-TA-11.6_SIGNEuropeAustraliaEMEA_USASPDRICSRTCEE_HWp2b_Service1FF_fastboot.xml
Fantastic!
First thing, before any actual booting, was to try if I could finally charge my battery again, and at last - yes!
At about 70%, I got adventurous, and unplugged the charger to put it in another power outlet. This made the phone actually boot up, but I thought that's not too bad now... But:
Now I have the following issue: After being freshly flashed (I tried several times now), it will charge as long as I don't actually switch it on, ONCE, but when it boots, after asking the setup questions and a little while on, it will switch off on its own, and then it's stuck in some variation of the bootloop (M dual core logo, pulsing M forever, OR rebooting ever and ever again at the pulsing M, OR just stuck at the M dual core). At least I now have a recovery menu. Erasing cache and data DON'T solve the issue (as proposed many times in the forums). I read a hint that it might be a kernel issue, or that it might be caused by a wrong radio.img (CDMA on a GSM phone). I checked and tested the latter by deactivating the radio in the extended settings, but it would still switch off after a short while (and it had defaulted to GSM, as it should).
So...am I stuck to wait for some new Firmware to come out, that might fix the issue? Or what should I try? Thanks in advance...
Resolved!
Long read, but I finally managed to do it. Basically, I am not 100% sure what happened, but I have a hunch:
After I thought I had solved the power issues by at least being able to charge the battery once after each re-flashing, I tried to fix the issue about the phone randomly switching off (and on - it wouldn't stay off!). I read that it might have to do with flashing failures (no error message??), or incorrect kernel or radio images...
Not long, and I ran into familiar problems again: It would flash the smaller files, but not system and cdrom; it would successfully "send" the files, but never stop "writing" them (I waited for somewhere between 10 min and an hour at each attempt), only way to stop the process was to switch off the phone, which certainly is not healthy during flashing...
...so battery started to go down again and I started to more and more clearly face a power issue again (I had disconnected the external power and didn't want to risk that McGyver approach again). As it happened, I also 'got some new USB 3.0 external hard drives at this time. I found that one would readily power up on all my USB ports, the other one could not get enough power even from some supposed 3.0 ports..
...which made me try flashing the very same firmware I was just trying (with the factory cable, of course), all the smaller files of which worked on the one computer but not the large ones (indicating I had the right firmware, at least):
SPDREM_U_01.6.7.2-180_SPU-19-TA-11.6_SIGNEuropeAustraliaEMEA_USASPDRICSRTGB_HWp2b_ Service1FF_fastboot.xml
, on another computer, on the one USB 3.0 port that had proven to supply the most power - and taa-daa! It wrote it, very quickly, without complaining!
And it booted alright (after charging it first, just in case). And it stayed on (and off, when I eventually rebooted it). I am running that ever since, and it seems ok...
Originally, I had aimed for:
SPDREM_U_01.6.7.2-180_SPU-19-TA-11.6_SIGNEuropeAustraliaEMEA_USASPDRICSRTCEE_HWp2b _Service1FF_fastboot.xml
, but I think the differences are minimal and I don't want to risk anything going wrong again, right now.
In conclusion, to me the main issues were
- finding the right firmware, stupidly not having paid attention to the original version number, and
- all sorts of different power issues!
The factory cable did not solve all of my problems.
Recharging the battery (eventually) did not solve my problems.
ADDITIONALLY, it needs to be flashed from a USB port supplying sufficient power!
This might point into the direction drolgnir suggested, but for me, it was not an OS/driver problem, but definitely power (same, fresh install of Fedora Linux on the two machines that did, and didn't work, one of them alternatively running Win 8; the Linux Mint computer I also tried doesn't have USB 3.0, the USB 2.0 ports - including an externally powered USB hub - did not work). @drolgnir: maybe it was power for you too, but you didn't notice because it was a different OS too?
...I hope this overly detailed report might help someone else too...