Hello everyone here:
I have bought a Cinglar 8525 about 3 month ago. Because enthusiasm of flashing rom, I start to flash rom one week after the purchase.
I flashed the hard spl v7,and flashed new OS rom image.
During the flashing, nothing special happened.
After two months usage, one time a software stopped responding, I thought it might be network failure or something like that and simply reset the device,then the nightmare began.
The device boot into bootloader automaticlly without the pressing of OK and Power button.I tried to reset the device by push the reset pin but it does not work, the device always boot into bootloader, after a few step of tring, it turns out the device maybe dead and I pull off the battery to make the device totally shut off, then install the battery again, and leave the device black screen.
After some time, I reset the device again , it boot into the OS this time. After some configuration that need reset , I reset the device ,but again ,it boot into bootloader.
So my device is very unstable now, even "fragile". Boot, maybe into OS, maybe into bootloader.
Can someone explain this? Or help me solve it?
some addional information:
I have flashed using card-flash method with the Manufacture Traditional Chinese Version( I came from China and the phone is origionally unlocked and I have hardspl v7 on it ).
After the flash ,the device can boot into OS this first time I reset the device, but after second reset,it still goes into the bootloader.
After a long time, I plan to flash one of the cooked ROM when I purchase the device, and ready to return the device the the seller to sort it out. But after this flash, the device just RETURN to normal ! I think it maybe back in normal and I have no execuse to return the device.So I start to use it normally.
After half a month of usage , the "bootloader mode" came again,similar steps to last time it "crash" ( device halt, reset, boot into bootloader ).
May someone diagnose this?
You're running wm6.1, aren't you? Try wm 6 as its more stable or if you wanna stick with 6.1 try PDAViets roms (19701 or 19900). They're english though....
Please note the "unstable" I mentioned is not something like halt frequently,application auto close up,etc.It's the bootloader stuff.
But I thought the problem might be irrevelant to the OS version, the "crash" occur first time when I use a ROM of wm6.0 and "crash" second time when I use a ROM of wm6.1
do some reading on wm6.1, it causes stuff like what you are describing....
After deep search in my brain, the "crash" might be occured during two version of ROM and both with wm6.1 .
Can you provide some link describing this problem of wm6.1 ? I just wondering if it is my device hardware failure or not.Or due to my some improper operation during ROM flashing process. Thank you.
Use the search function. There are a heap of threads... Some people recommend flashing a stock rom THEN flashing the wm6.1 of choice. This DOES seem to fix the problem.. Cheers...
yinx said:
some addional information:
I have flashed using card-flash method with the Manufacture Traditional Chinese Version( I came from China and the phone is origionally unlocked and I have hardspl v7 on it ).
After the flash ,the device can boot into OS this first time I reset the device, but after second reset,it still goes into the bootloader.
After a long time, I plan to flash one of the cooked ROM when I purchase the device, and ready to return the device the the seller to sort it out. But after this flash, the device just RETURN to normal ! I think it maybe back in normal and I have no execuse to return the device.So I start to use it normally.
After half a month of usage , the "bootloader mode" came again,similar steps to last time it "crash" ( device halt, reset, boot into bootloader ).
May someone diagnose this?
Click to expand...
Click to collapse
Please note this, I have done it before, I 'll do some search work.
Is there some evidence or something that the 6.1 rom of 19701 kernel has solved this problem ? I really like the thread function in SMS message in 6.1 so I want to stick in wm6.1 .
I have honestly only had problems with th 19919/19202 versions of wm 6.1. Tried 19900 with no problem and REALLY liked the speed. 19213 is SLIGHTLY faster and again no problems. Try ne of these if you MUST have wm6.1. The stability seems to get better and better as the chefs progress up the versions. Cheers...
Untill now I can't get my phone out of bootloader, I've flashed many ROMs including manufacture shipped ROM, but the phone still remain in one screen.Wondering if it can work out. Frustrated....
Start from 9:00 this morning I kept flashing my phone with different version of ROM, try to get out the bootloader,but still not working.
After a reset of frustrating "not working", I put down the phone,and do some other job,when I came back,I have transfered another ROM to the microSD and ready to flash the ROM.Before flash I thought "may I reset the phone again? may be the bootloader will go away", then I reset the phone as normal, after a while , the splash screen appear! I enter the OS, thinking the bootloader problem has go away. But when I complete some setting and reset the phone again, the phone finally fall in bootloader again.
So what ......
check for bad blocks using MTTY.... On upgrading section.
Cheers...
This I also have tried out. But I see no bad block on it, and I even do a forcibly fix to the NAND and with no avail.
I have sent the phone to a service center, it is said they might going to change a chip on the phone.
Wish my phone good luck.
Hi guys,
Recently I updated my XDA Orbit with the new WM6.1 Diamondish ROM. Everything went great until I tried to install the Oops 6.1 ROM. Before trying to install the Oops ROM I tried to unlock the CID just in case (with your Artemis_USPL tool)... Half way through the setup screen displayed an error saying "Connection error... Please check the USB connection...". Just to clarify I never managed to install the Oops file.
Then I tried to install the original XDA WM6 ROM but with no luck as I got the same error again. Then I tried to start the bootloader manually (by pressing the voice recorder button along with the Reset one) and instead of the usuall 3 colour screen I got a blank white one. Afterwards the phone froze and I had to reset it so that I can use it again.
I did a small search on your website but because I wasn't able to find another similar case I decided to start a new thread.
Currently my phone works perfectly fine with my previous Diamondish ROM, but I seems that I can't install anything else.
Could it be a corrupted bootloader? If so, how can I fix it?
Any help will be much appreciated.
Thanks in andance!!!
Take out your MicroSD card and then try and flash
You were right! Once I got my memory card off my phone, the bootloader started as usual. Cheers mate!!!
Could somebody please help me?
Today I wanted to upgrade my ROM to a new version.
I succesfully upgraded my Radio and SPL, but when I tried to flas the new ROM I received an error. (I thought it was ERROR: 260)
Now Im stuck in the Bootloader and a hard reset, soft reset, or any other reset wont work.
Removed battery and started device bootloader pop up again.
Please help.
(I really don't understand what went wrong I flashed my rom before 2 times without any problems.)
Read the forum, search the internet and look at this thread: http://forum.xda-developers.com/showthread.php?t=324369
good luck, it's solvable.
I had update my HTC Imagio with a new ROM. The other people update this ROM and their Imagio work fine with this ROM. But after ROM update completed, my device restart and informs: "run FILEOP\windows\menu_FILEOP_Open failed "
any body know what this error is, and how to resolve it
thanks
Error Message
I do not know specifically what the error message indicates, but if it were me, I would re-flash with that or another ROM.
My Imagio still working well with the other ROM, but with the ROM D8C2_U1 from PDAViet, it occurs that error, and i tried re-flash that ROM many times but it doesn't work.
http://forum.xda-developers.com/showthread.php?p=8445233#post8445233
More people are experiencing this...
Hi to all
I have a Samsung galaxy s6102 and some weeks ego I entered a code (*#*#2663#*#*) which supposed to update touch firmware but it failed and touch screen never worked again.
I couldn't repair my phone even by flashing ROM an kernal. I tried method mentioned in this topic but I discovered that screencast does not work on my phone,hence I used ADB shell commands to enter the code (*#*#2663#*#*).
unfortunately just after entering the code this error message pops up: "The application com.sec.android.app.lcdtest (process com.sec.android.app.lcdtest) has stopped unexpectedly. Please try again"
I retried with different ROMs and got the same error.
I am wondering how should I erase touch firmware and flash new one and why flashing ROM and kernel do not replace this firmware?
It would be very appreciated if anyone suggest another solution for my case.
solved
after about 6-7 weeks finally I found a solution for my problem
simply flash stock kernel alone (not all of firmware) by CMW. after that touch would work again and flash any ROM you like
download stock kernel from here
I'm having an issue with mine
Touch doesn't work no matter what kernel or rom I flash using cwm
Phone won't get recognized on pc no matter what cable I use or windows I use, and I have drivers installed properly
I seem to be stuck at the stupid welcome window where it asks that I touch the android to continue
Everything was working just fine when I was on stock, but I made the stupid mistake of not making a nandroid when I flashed lu Kat custom rom and now I don't know what to do anymore
Any help would be appreciated.