hello all
yesterday i wanted to flash a friend tp2
when i flashed it it went to 100% and then it gave a rom code error
i restarted the phone in bootloader to flash a other rom and it wanted to read the image on the sdcard
wich resulted in red serie of digits on top of the screen 00058002
and the phone turned off
i deleted the image from the sdcard and tried it again
i came in bootloader and i saw threu the spl text rom upgrade error
now everytime i enter bootloader it turns off the phone in 5 sec
i managed to run a task 29 one time by resetting the phone multiple times
can some one help me
owww its not fixed
i managed to get stock rom on it again but during the custimizsation the phone turned off:S
and now i have the same problem again
edit: i dont know how but its fixed
Related
Hi,
I have flashed x2h's 6.5 rom few months back and today i have tried to flash it again but it gives a error : 260 and the device shutdown and when i try to start it, it wont start and then I unplugged and plugged the battery then my mobile starts. I tried it several times to flash it (by rom and by camera & reset buttons) but the bootloader not comes.
Help me,
ehmafia
So today i tried updating my Three locked Xperia X1i, Donwload went fine but it decided to crash half way through installing the update and is now stuck on that Colourfull Lined Screen. saying "upgrade ROM code error" Now ive tried restarting the download and the updater says it cant read the phone and wont do anything! can someone please help on the situation.
Providing you HardSPL'd first just get yourself a KOVSIMG.NBH file (for the XPERIA, I recommend Sutyi's SECOND ROM) put it on your microSD card and start up in boot loader mode. You can search how to start in boot loader mode easily enough.
I havent HardSPL'd, I just bought the Xperia and thought i should officially update it, Didnt know it would cause this. there should be some easy fix to it.
Hello all,
as the title says, one of my touch diamond's is stuck in bootloader screen.
I didnt do anything in between it working and not working, it was on my desk, put it there working, got it 5mins later, and it was in bootloader screen (tricolor screen).
What i've already done to try and fix it:
flash it with the original HTC rom, flash completes succesfully, phone reboots to tricolor screen, so no solution there.
install mtty and format the phone, this completes, reboot the phone, again goes to the bootloader.
reflash the phone with original rom after cleaning it with mtty, flash again completes succesfully but when it reboots after flashing it just goes to bootloader again.
Tried to flash a Hardspl: stuck at 0% and stays there. so that doesnt work.
BUT! when in mtty i give the "boot" command, it DOES start to boot WM. but then again, when i turn the phone of, and on again, or it reboots because of first start after flash, it goes to bootloader again. The VOLDOWN button is NOT stuck, cause when it boots i can use the vol buttons perfectly fine.
Anyone got an suggestion in how to unbrick it? i have a second, perfectly working diamond here too, if that helps in any way.
Some more info ive just seen in mtty, when i told it to boot, it said ONE BAD BLOCK IN CE, remove block ---- to ---- (dont know the exact numbers anymore)
hi..i had something like that...
just download this.
"RUU_Signed_1_93OliNex_HSPL_UnsignedEdition"
it's only 1.7MB and it's will make it work.. atleast it did the job for me...
Hi,
My T mobile touch diamond stuck in bootloader screen? Any experties to help me please.
Thanks in advance.
I recently tried to update HTC HD7 firmware after a hang issue. I had hard reset the phone and the phone now boots in bootloader mode. I cannot exit the bootloader mode. Also, I may have tried flashing the device with RUU_Schubert_hTC_Asia_WWE_2.20.841.02_Radio_5.65.09.11a_22.44.50.15_NoDo
When the ROM version of the phone is 2250.09.12302.707. Now my phone is unusable. It starts in bootloader mode any attempt to flash it with other 707 ROMs RUU_Schubert_hTC_Asia_WWE_1.57.707.02_Radio_5.52.09.16_22.33a.50.10_Signed_SCHUBERT_RELEASE fails with a update error 270: saying the ROM file is corrupt please help. My phone is unbranded.
Thanks,
Please help
The windows phone support tool 'might' be able to help you out here.
://support.microsoft.com/kb/2530409
Unfortunately as a noob to the forums I can't post links. Add http to the above to make it into a link.
I had the same problem, but i managed to solve!!!
Invert the flash order from this thread: http://forum.xda-developers.com/showthread.php?t=1000520
Flash b2 (big one) first and ignore the error then flash b1 (small one) and the phone will boot
Now guys my phone is toast. It does not work beyond the bootloader mode. I tried flashing the device but the process gets stuck at 0%. I tried formatting the SD card but the same tricolor boot screen appears. What the hell has gone wrong? Anyone who can help me thanks a million. I would really appreciate it.
did you try flashing one of these 707 roms ?
http://forum.xda-developers.com/showthread.php?t=888747&page=20
if u stuck in bootloader mode, pull out the battery , and install it back again
It could be a faulty USB port during the flash process. Try another USB port.
As I said in the title. The phone's memory seems to be read only.
I can access the fastboot mode of the phone and issue commands like flashing the recovery but it doesn't seem to update anything on the phone even though I get the "OKAY" message.
My phone is unlocked and until last night I was running CyanogenMod on it just fine. But now I can't flash a new recovery or access it. I have TWRP installed but everytime I try to boot into recovery the phone gets stuck on the logo screen and flashes every couple of seconds.
If I try to start my phone normally I get the cyanogenmod logo on start up (even after flashing stock) and the phone never actually boots up.
Anyone had the same problem before? If you need more details I'll reply ASAP.
My phone is the retail European XT1068 Dual Sim. Thank you in advance for any help.
Same issue here (I'm MrPowerGamerBR on Reddit), the more I read about trying to fix this issue, the more I start thinking "this phone is dead, move on..."
There isn't no fix for this, the only way to fix is replacing the logic board.