Related
So basically I've just unlocked my bootloader last night. Used three hours to do so. And Before I slept, I flashed DoomKernel v06-1113 and everything was fine. SO I decided to flash DoomKernel V06 as it is said to be highly recommended for the rom I want, "FeraLab" So, I flashed V06 and the next thing that happen was the phone just stucks at DoomKernel Logo. Lasted for 20mins or so. I decided to pull out the battery and inserted it again. Stucked at DoomKernel Logo AGAIN but this time the screen gets dimmer after 4 secs or so. And the whole thing just seem to reboot again. And it goes on and on and on. Decided to take out the battery and just leave it like this hoping it would somehow work the next morning. The same problem just go on and on. But there was once, the whole thing fully rebooted and finally start up. I tried putting the freq to max on Set CPU and it went into reboot again. Straight. Now things just go back like before. Kept rebooting over and over again. I'm hoping for an answer ASAP as I'm gonna need to use my phone for a really really long time later this afternoon. Am going out for basketball practice now and will be checking for any replies. PLEASE AND THANKS IN ADVANCE.
Am gonna try using PC companion to repair. Hope it's a correct choice cuz I dont seem to be able to enter the xrecovery mode
Still waiting for more guidance. Help is much appreciated
PC companion never got to fully repair it cuz the part where they prepare the computer to update took too long and it never moved. Decided to try downloading SEUS to repair.
Still waiting for more guidance. Help is much appreciated
rickyX10User said:
PC companion never got to fully repair it cuz the part where they prepare the computer to update took too long and it never moved. Decided to try downloading SEUS to repair.
Still waiting for more guidance. Help is much appreciated
Click to expand...
Click to collapse
it would seems like ur x10 cant handle OC. i suggest u try the FS version
check it at DL thread.
http://forum.xda-developers.com/showpost.php?p=21214246&postcount=1356
here is the thread. try the 3rd option (FS)
remember to flash the wifi module as well
Thanks for your reply but like I said, I cant seem to enter xrecovery. How am I able to flash the rom?
allright buddy i will tell you exactly what you need to do
first thing go to this link
http://forum.xda-developers.com/showthread.php?p=21214246#post21214246
and download the medium overclocked version of the doom kernel which means the v06-1113 doom kernel i have the same problem my phone reboots as well if i used the 1228Mhz version it is just that it can't handle itand you have got that one flashed on your phone so go ahead and flash the v06-1113 doom kernel through flashtool an then it will let you go to xrecovery and i am also using the FeraLab v4
and it works perfect and you can visit the FeraLab rom page by clicking the link below
http://forum.xda-developers.com/showthread.php?t=1458001
Problem solved. Thanks for your help anyway
What I did was I used PC Companion to repair it and flashed v06 1113 into it. Thanks alot for your time and help =)
rickyX10User said:
Thanks for your reply but like I said, I cant seem to enter xrecovery. How am I able to flash the rom?
Click to expand...
Click to collapse
LOL the link i provided is for kernel, .ftf file. it was meant to be flash by flashtool.
as u know, the kernel provide 3 type of kernel (details at Doom's thread), once u flash the kernel, u will able to enter the boot manager (or any recovery that u want)
just wanted to clarify.
glad ur problem solve, but using this method would be easier as u does not need to reconfigure again. personally experienced it b4
But I thought you'll need to turn on your phone, get it connected to FT with it recognizing your phone, then select the file you want to flash, unplug it, turn it off and then enter flash mode. My phone din't seem to be able to be recognized by FT while it was soft bricked
rickyX10User said:
But I thought you'll need to turn on your phone, get it connected to FT with it recognizing your phone, then select the file you want to flash, unplug it, turn it off and then enter flash mode. My phone din't seem to be able to be recognized by FT while it was soft bricked
Click to expand...
Click to collapse
Hi ,
Now i have revert it to2.3.3 ginger bread and it is successfully running. Please suggest which andriod 4 version should i go for my mobile
sanjays183 said:
Hi ,
Now i have revert it to2.3.3 ginger bread and it is successfully running. Please suggest which andriod 4 version should i go for my mobile
Click to expand...
Click to collapse
My suggestion is don't go for ICS ROMs... they eat battery and your phone will have to be charged once every 10 hrs... so stick to gingerbread... go for tech devils ROM which is super light and long battery....
Sent from my Transformer TF101 using xda app-developers app
udupa82 said:
My suggestion is don't go for ICS ROMs... they eat battery and your phone will have to be charged once every 10 hrs... so stick to gingerbread... go for tech devils ROM which is super light and long battery....
Sent from my Transformer TF101 using xda app-developers app
Click to expand...
Click to collapse
well, i kinda agree in some of ya point that ics in x10 does eat more battery energy, but X10 it've done its best for 4" screen resolution 480*854, single core 1GHz with only 288MB RAM max. Many people still looking forward for it in ics though. And battery hours in ics (if just message, wifi, phonecall, alarm) can stand up to 3days (until battery 10% left) depending governor and frequency ya set. But if HD gaming, gingerbread still works great because it'meant for gaming including emulating games.
Whitefang
sanjays183 said:
Hi ,
Now i have revert it to2.3.3 ginger bread and it is successfully running. Please suggest which andriod 4 version should i go for my mobile
Click to expand...
Click to collapse
Depends to person liking. For me, Xperia S ICS CM9 by senior Vashista reddy. Great RAM freed and smoothness. Enough for wifi, call, music, 6MP camera uncompressed, but not video camcording or play. Older version still works great and smooth. But newer version jellycream got some fixes needed to be implemented. hope helps.
Whitefang
rickyX10User said:
PC companion never got to fully repair it cuz the part where they prepare the computer to update took too long and it never moved. Decided to try downloading SEUS to repair.
Still waiting for more guidance. Help is much appreciated
Click to expand...
Click to collapse
Hello friend, you cant repair your x10 thru seus or pccompanion coz youre using a custom kernel, my advice is flash a different kernel like thkernel then let it boot, if it successfully booted then try flashing again doomkernel.. Press thanks button if i helped you buddy. :thumbup:
Sent from my X10i using xda premium
So, sort of long story, i'll cut it short
-Got an old X10, had stock 2.3.3
-Rooted it
-Did not unlock bootloader, got kinda scared.
-Tried to install FeraLab custom ROM, it failed probably because of sdcard permissions; i accidentally wipe /system /data /cache
-stuck at first Sony Ericsson screen
-Somehow managed to flash a 2.1 stock rom with flashtool, after an hour of different combinations of enterring flash mode and pulling the battery
-Tried to install FeraLab again, this time it went through
-After install, rebooted, phone shut down during boot up process
-Will not turn on at all. Even when plugged into a PC, wall, not plugged in, pulling battery, etc.
I think what happened is that FeraLab needed a newer baseband than the 2.1 stock rom had. Does anyone have any suggestions on how to get this sucker to even turn on? Not a single LED is on when plugged in, giving me the impression that it's not charging.
If the battery has drained out, it might take some time before it kicks in and indicates that it is charging.
If the ROM has failed somehow, it might not show that it is charging at all, but might be charging.
Either way: Let it charge "blindly" for a while, and see what happens.
Once it does boot up to some level or shows life-signs, let it charge fully before you'l attempt a ROM flash.
The flash/recovery mode needs a full battery, and reason is that the external power isn't used even when connected while in flash/recovery mode.
If you happen to be in bad luck, and the ROM failed as a result of a drained battery, you might have to charge the battery externally. Use an external battery charger made for 3.6 volts Lithium Polymer batteries, and make sure to align the + and - terminals properly.
I can recommend the multicharger from Powerbase, called C-734U:
http://www.powerbasehk.com/product.php?id=148
Using it myself to charge the X10 battery, as well as other batteries from other devices I have.
EDIT:
(For some reason, powerbase has taken back that it'll charge Lipo batteries, but when I bought mine, it was described as a li-ion, li-poly and Ni-MH charger, and it't ability to charge li-poly batteries was the very one reason to why I bought it.
I suspect PowerBase does not want to take responsibility if anything happens to the li-poly-batteries, as they are known to be more dangerous than other types.)
I've left it on the wall charger all night, no response or anything. Luckily, I bought a new battery a few days ago, so when that comes in, hopefully it will be charged enough for this thing to boot.
Do me a favour are u able to take screebshot of settings, about phone menu and post it here? Need to see ur baseband and kernel
Sent from my X10i using XDA
laneyofdeath said:
Do me a favour are u able to take screebshot of settings, about phone menu and post it here? Need to see ur baseband and kernel
Sent from my X10i using XDA
Click to expand...
Click to collapse
Dude his phone wont start up. How come he'll be able to take a screenshot
Sent from my LT26i using xda premium
king-iyokan said:
Dude his phone wont start up. How come he'll be able to take a screenshot
Sent from my LT26i using xda premium
Click to expand...
Click to collapse
Yeah, i'm not sure what he expected. But, good news! Now for some reason my phone started blinking red whenever I tried to turn it on! I guess the battery completely ran out or something. It also blinks every now and then when plugged in, so I guess it's charging. The previous owner of this phone said that it had some battery problems, so that's why I ordered that new battery. I'll let it charge for awhile and let you guys know what happens.
Okay, after getting my new battery, the phone will still not turn on. I think i've figured out two behaviors:
1. If the battery is nearly completely out of charge, it will flash a red light
2. If the battery has charge, it will not do anything at all.
Anyone know how to fix this?
While trying to turn on the phone, after long-press power button, do you get a flash from status led & short vibration?
From my XPERIA X10S v8.2 on kCernel @ 1.19ghz
ToledoJab said:
While trying to turn on the phone, after long-press power button, do you get a flash from status led & short vibration?
From my XPERIA X10S v8.2 on kCernel @ 1.19ghz
Click to expand...
Click to collapse
No vibration, the red LED flashes three times, and that is , as I said before, what happens when the battery seems to not have any charge. If I have a charged battery it does absolutely nothing.
Have you removed sim & sd card and tried. I know it sounds dumb but when I flashed a bad kernel I had to try to connect flash mode like 10 times. Finally I left the phone unplugged from pc, started flashtool and started flashing. I only put battery in phone just before holding back key. I never connected USB until tool said to dis-connect phone and connect in flashmode.
i wish you luck, I know how I felt when it went wrong
From my XPERIA X10S v8.2 on kCernel @ 1.19ghz
FireFreek said:
So, sort of long story, i'll cut it short
-Got an old X10, had stock 2.3.3
-Rooted it
-Did not unlock bootloader, got kinda scared.
-Tried to install FeraLab custom ROM, it failed probably because of sdcard permissions; i accidentally wipe /system /data /cache
-stuck at first Sony Ericsson screen
-Somehow managed to flash a 2.1 stock rom with flashtool, after an hour of different combinations of enterring flash mode and pulling the battery
-Tried to install FeraLab again, this time it went through
-After install, rebooted, phone shut down during boot up process
-Will not turn on at all. Even when plugged into a PC, wall, not plugged in, pulling battery, etc.
I think what happened is that FeraLab needed a newer baseband than the 2.1 stock rom had. Does anyone have any suggestions on how to get this sucker to even turn on? Not a single LED is on when plugged in, giving me the impression that it's not charging.
Click to expand...
Click to collapse
Try to flash any latest kernel via flashtool . Go for doomkernel . I think its software issue . Try this first .
Almost same here please help..
Last night battery ran out of charge & phone switched off.. then i plugged the charger it doesn't charge.. after some time i tried turning on.. Vibrates with the green LED but nothing happens then..
Note: This is not the 1st time i'm letting my phone drain, but facing this problem for the 1st time..
Rom : Spikelabs GB Gaming rom
Kernel : Ferakernel v23 beta6
I tried another battery, charger, data cable.. Tried flashing stock & spikelabs kernel., but of no use..
Any help is greatly appreciated..
Thanks in advance.. :good:
Something like that happened to me not long ago!
I was trying to flash some ROMs and I messed up then my phone wouldn't turn on!
But Miracously, I could flash a Stock 2.3.3 which fixed the problem!
At first, I used Sony PC Companion, which helped a lot- and after I screwed it for the second time, I used FlashTool-
I don't know if this was helpful, but I hope your x10 will be fixed soon!
yeah try the PC Companion first, it helped me too a couple of weeks ago
No luck...
Hi friends..
Tried to repair using PC companion, but was able to connect only in flash mode, unable to proceed software update..
I previously tried flashing stock GB using flashtool thrice. Still couldn't switch on the phone.. What else may i try..
Thanks friends..
ashok weird said:
Hi friends..
Tried to repair using PC companion, but was able to connect only in flash mode, unable to proceed software update..
I previously tried flashing stock GB using flashtool thrice. Still couldn't switch on the phone.. What else may i try..
Thanks friends..
Click to expand...
Click to collapse
try flashing kernel other than spikelabs (e.g. feravolt,doom,achotjan,zkernel..etc.)
sanababitz said:
try flashing kernel other than spikelabs (e.g. feravolt,doom,achotjan,zkernel..etc.)
Click to expand...
Click to collapse
Tried Ferakernel, Stock GB kernel, etc bro.. No luck..
Flashed Stock GB firmware more than 3 times still no luck :crying:
SEUS not working _ couldn't connect to network..
SUS does not have x10 enlisted
Went to 3 service shops at - Ritchie street, Chennai. They simply said harware issue (Short in board) and gave back the phone.
Now given at a better service centre. Will get back on monday it seems. Will update the status friends..
Thanks..
Here also they said the same reason friends.. Short in board..
Is there any way i could recover the phone???
Hey guys i've a problem with my x10
So one night i was playing with it than the other day the phone would start
so i thought yeah right might be the battery or something. i took it to my friends x10 it was with 87% charged so i exclude this
Than i tried to flash with flashtool a new kernel and i get stuck at 9% or 15% depending on the kernel i use.
With SEUS it starts to repair but it says. No new updates avaiable after a few moments.
Some information regarding my phone
Unlocked Bootloader
FXP KERNEL
MM TEAM MIUI V4
The phone vibrate but doesn't start or load the kernel.
What do i do?!
Srry for my bad english
Thx in advance
Usrle flashtool to reflash kernel or firmware.
already did but i get stuck at 9% or 15% flashing the kernel
I'm downloading a full generic rom x10a
having similar problem
Hi, I had similar problem as well
X10i running FXP CM7 suddenly just wont boot n charge after I turn off the phone
it wont boot after flashing anything (firm or kernel) except the official firm
now that I end up with a cap R bootloader but flashtool claim that bootloader is rooted
do I still keep the bootloader unlock?
i guess you have a locked bootloader since the original firmware is loading just fine even tho rooting has nothing to do with the bootloader it self. i'm only guessing.
I'm stuck at. Flashing Loader
I bricked my phone last week and it got stuck in a boot loop.
I downloaded the x10a generic Stock ROM and flashed it via Flashtool and it worked like a charm.
Hope this helps.
[XBOCT]™ said:
I bricked my phone last week and it got stuck in a boot loop.
I downloaded the x10a generic Stock ROM and flashed it via Flashtool and it worked like a charm.
Hope this helps.
Click to expand...
Click to collapse
But that way you weren't at a brick point.
You get brick when u get those 3 blink red LED and the phone doesn't do anything
By the fact that your phone were able to load the kernel. i guess
same problem repeat
Hi, just confirm that the bootloader remain unlock as long as the flashtool claim its ROOTED
had you try other than official 2.3.3 ftf?
because I just got the same unable to boot problem repeated again
this time cant get boot on even stock 2.3.3 firm
but I was able to boot up and charge on 2.1, then get root, recovery and kernel (w/o unlock bootloader again) and go straight to custom ROM with no problem
mooving said:
Hi, just confirm that the bootloader remain unlock as long as the flashtool claim its ROOTED
had you try other than official 2.3.3 ftf?
because I just got the same unable to boot problem repeated again
this time cant get boot on even stock 2.3.3 firm
but I was able to boot up and charge on 2.1, then get root, recovery and kernel (w/o unlock bootloader again) and go straight to custom ROM with no problem
Click to expand...
Click to collapse
i'm using
X10a_2.1update1_r2.1.A.0.435_Generic.ftf
And it get stuck at Flashing loader
Idk but i can "read" the kernel when i dump the propriets but i can't "right" when i try to flash something
Anyone?
guys?
you said your phone is "bricked"
I'm not sure if you know what that means.
If you say you've bricked your phone then no one can help you.
A brick is a brick. It doesn't matter if it weighs a few kgs or a few hundred grams. A brick can't receive phone calls.
And your phone isn't even a normal brick... You wrote that it's "really bricked"
Are you building a house anytime soon?
LJE said:
you said your phone is "bricked"
I'm not sure if you know what that means.
If you say you've bricked your phone then no one can help you.
A brick is a brick. It doesn't matter if it weighs a few kgs or a few hundred grams. A brick can't receive phone calls.
And your phone isn't even a normal brick... You wrote that it's "really bricked"
Are you building a house anytime soon?
Click to expand...
Click to collapse
maybe i'm wrong idk maybe is a soft brick. thats why i'm asking for some help.
almomdegal said:
But that way you weren't at a brick point.
You get brick when u get those 3 blink red LED and the phone doesn't do anything
By the fact that your phone were able to load the kernel. i guess
Click to expand...
Click to collapse
The red led blinking rapidly three times means the battery is "out of juice".
I've said it earlier: Several X10 devices have reached an age, where battery failures are fairly common due to charge cycles and/or age. Specially if one got it just after the launch.
Anyhow, what you can do, is let the device charge "blindly" for a while, and a while I mean for half an hour to a few hours. Then it should, out of the blue, jump into "active" charging (With the battery screen showing offline charging)
If this doesn't happen you might have to charge the battery externally.
...or even replace the battery.
-"Why?", one might ask.
Reason is that the flash mode only works with a charged battery.
If it empty, it won't engage the flash mode at all. Stupid design, yes, but that is how it is.
Worst thing is, that the battery does deplete/discharge while in flashing mode. That is why it's so important it's fully charged and fully working, before one engages in flashing activities.
See this post for more information about this: http://forum.xda-developers.com/showthread.php?t=1642154
Try wotanserver's flashtool...
http://www.wotanserver.com/en/
Good luck
SysGhost said:
The red led blinking rapidly three times means the battery is "out of juice".
I've said it earlier: Several X10 devices have reached an age, where battery failures are fairly common due to charge cycles and/or age. Specially if one got it just after the launch.
Anyhow, what you can do, is let the device charge "blindly" for a while, and a while I mean for half an hour to a few hours. Then it should, out of the blue, jump into "active" charging (With the battery screen showing offline charging)
If this doesn't happen you might have to charge the battery externally.
...or even replace the battery.
-"Why?", one might ask.
Reason is that the flash mode only works with a charged battery.
If it empty, it won't engage the flash mode at all. Stupid design, yes, but that is how it is.
Worst thing is, that the battery does deplete/discharge while in flashing mode. That is why it's so important it's fully charged and fully working, before one engages in flashing activities.
See this post for more information about this: http://forum.xda-developers.com/showthread.php?t=1642154
Click to expand...
Click to collapse
Didn't work, i even use my friends battery to flash it and it didn't work
almomdegal said:
Didn't work, i even use my friends battery to flash it and it didn't work
Click to expand...
Click to collapse
Well, if the battery issue was fixed, and you're sure the battery is fully charged, then try this: (Quoting from my other post)
I've charged/replaced the battery, and are having trouble with starting up. Earlier flash failed. Now what?
Don't worry. It's pretty darn hard to truly brick this device. Even if the screen remains black, there's still hope.
Once that the battery issue has been dealt with, you can move on:
Download the latest Flashtool and the proper global firmware (FTF-file) for your device from here:
http://forum.xda-developers.com/show...ight=flashtool
1: Extract/Install the Flashtool to a folder of your liking.
2: Copy the ftf-file to the "firmware" folder in the Flashtool folder you just created above.
3: Start Flashtool. Click the Bolt icon (flash). A Window appear. There, choose "flashmode". Cllick OK.
4: A new window appears. In the list on the left, choose the Generic firmware you downloaded and copied into the "firmware" folder. Should have a similar name as the file itself. (Or manually open the ftf-file from the "..." icon on the top right.)
5: Hit "OK. Follow the instructions you get on the screen:
1 - Unplug the device.
2 - Power off the device. (Unplug and replug the battery to be sure it really off, and not stuck in black screen)
3 - Press the "back" putton, and hold it down while performing the next task.
4 - Plug the device into the computers USB.
Click to expand...
Click to collapse
Forced flashing should now start.
Click to expand...
Click to collapse
time to accept the fact that it is really brick
Hi @almomdegal,
if you try flash using another full charge batt n its not work, I think this forum is no longer works for u anymore.
I own a faulty X10 as well, random shut down (no warning at all) then wont boot n charge
reflash it, revive for few days and dead again, and reflash....
now it is really dead, no problem appears and it show flash successful and it just wont boot or charge but vibrate non stop
I just send the phone to service center and the board need to be replace
so its time to send to the real professional to solve it, coz this problem ain't software downloaded from internet can solve anymore
mooving said:
Hi @almomdegal,
if you try flash using another full charge batt n its not work, I think this forum is no longer works for u anymore.
I own a faulty X10 as well, random shut down (no warning at all) then wont boot n charge
reflash it, revive for few days and dead again, and reflash....
now it is really dead, no problem appears and it show flash successful and it just wont boot or charge but vibrate non stop
I just send the phone to service center and the board need to be replace
so its time to send to the real professional to solve it, coz this problem ain't software downloaded from internet can solve anymore
Click to expand...
Click to collapse
yeah i guess so.
I just needed this closure i'll send it to service today
First of all, I wanted to say hello since this is my first post here :victory: and also please if I am posting wrong or if this question has been answered before forgive me, but I have already searched on google and on this forum and found no related posts Ok now about my problem:
I have a "Sony Ericsson Xperia X10mini Pro" with MiniCM10-4.1.0-20130416(mimmi) and 2.6.32.60-nAa-jb-05 kernel installed. Yesterday I decided to go back to U20_nAa-14_2.6.29.6-nAa-14 kernel and MiniCM7-2.2.1-mimmi-UNOFFICIAL because of wifi problems. I have done the flashing process with flashtool a lot of times in the past and I can't be wrong with it this time.
The problem started after flashing my kernel. Flashtool flashed the U20_nAa-14_2.6.29.6-nAa-14 kernel fine and phone was OK ready to reboot, so I unplugged the USB cable to start it on recovery so I could install Minicm from SD, but since I unplugged the cable the phone is DEAD! No led and no charging! :crying: When I try to reflash it, flashtool doesn't recognize it, I am pressing the back button and plugging it in but the phone is not recognized. It is not charging when I am plugging it on the charger and its not even trying to boot. I tried different cables, different battery (from a friend with the same phone) and nothing. Is there a way to force flash it back? Please any help will be appreciated since I have tried everything I know...
This has happend to other users too reasently.
I'm not sure if it only happens when going from JB to GB or it also happens when going from GB to JB.
We need to investigate why/how it happens and how to prevent it.
I always recomend to do a battery stat whipe just before a planed kernel-flash. I had simular problem once (no charge, no boot, no nothing) after a kernel-flash. I solved it by putting in a battery from another Mimmi (my wife has the same model). For some reason everything worked fine doing so. After battery stat whipe, the phone worked with my own battery again.
Best advise for others is for now: When you want to flash new kernel, first do a SEUS/PC Companion repair
This should be written into all install-instructions and mentioned again and again to avoid same problem for others.
I'm not sure how the other users solved this. Was it only by JTAG?
Thank you for your answer! :good:
First of all, there was no battery wipe option on this release of the kernel As I said before I have done it a couple of times in the past and every time with battery wipe, except this one and besides, I already tried your solution with my friends battery with no luck... So probably I am looking for another solution.
And one last thing about your post, what is "JTAG"?? I have seen it on other posts before but without explanation as to what it is, the only JTAG I know of is on the xbox360 And if its a possible solution how can I possibly do it? Is there a post with instructions?? (I will search on my own too now, but a recommended guide from someone who knows better is much appreciated!)
Emperor.dk said:
This has happend to other users too reasently.
I'm not sure if it only happens when going from JB to GB or it also happens when going from GB to JB.
We need to investigate why/how it happens and how to prevent it.
I always recomend to do a battery stat whipe just before a planed kernel-flash. I had simular problem once (no charge, no boot, no nothing) after a kernel-flash. I solved it by putting in a battery from another Mimmi (my wife has the same model). For some reason everything worked fine doing so. After battery stat whipe, the phone worked with my own battery again.
Best advise for others is for now: When you want to flash new kernel, first do a SEUS/PC Companion repair
This should be written into all install-instructions and mentioned again and again to avoid same problem for others.
I'm not sure how the other users solved this. Was it only by JTAG?
Click to expand...
Click to collapse
zero2048 said:
Thank you for your answer! :good:
First of all, there was no battery wipe option on this release of the kernel As I said before I have done it a couple of times in the past and every time with battery wipe, except this one and besides, I already tried your solution with my friends battery with no luck... So probably I am looking for another solution.
And one last thing about your post, what is "JTAG"?? I have seen it on other posts before but without explanation as to what it is, the only JTAG I know of is on the xbox360 And if its a possible solution how can I possibly do it? Is there a post with instructions?? (I will search on my own too now, but a recommended guide from someone who knows better is much appreciated!)
Click to expand...
Click to collapse
I'm pretty sure he flashed the x10blrelock.ftf instead of the u20 kernel and that is why his phone went dead.
A JTAG for our phone will do basically the same thing as a JTAG for the xbox, it restores original phone-state, but you need special equipment to do it, which is quite expensive. Most repair-shops will have one.
SmG67 said:
I'm pretty sure he flashed the x10blrelock.ftf instead of the u20 kernel and that is why his phone went dead.
A JTAG for our phone will do basically the same thing as a JTAG for the xbox, it restores original phone-state, but you need special equipment to do it, which is quite expensive. Most repair-shops will have one.
Click to expand...
Click to collapse
Thank you for the answer about jtag, I also checked for myself and found about the expensive equipment and propably its not the way for me
But about the kernel I am pretty sure it was the right file...
I know that a dead phone means bad kernel but its a process that I have done before a lot of times with success on mine and other phones My best guess is that something interrupted the process (bad usb cable?) or corrupted downloaded kernel file If that's the case is there an alternative solution? :crying:
zero2048 said:
Thank you for the answer about jtag, I also checked for myself and found about the expensive equipment and propably its not the way for me
But about the kernel I am pretty sure it was the right file...
I know that a dead phone means bad kernel but its a process that I have done before a lot of times with success on mine and other phones My best guess is that something interrupted the process (bad usb cable?) or corrupted downloaded kernel file If that's the case is there an alternative solution? :crying:
Click to expand...
Click to collapse
Usually, whatever you flash, even if it goes bad, flashmode is still available because that doesn't get tampered with, the only true hardbrick i've ever seen is when flashing that x10blrelock.ftf, which happens quite a lot lately.
Just for fun i even formatted my entire phone once, no kernel, no rom, completely empty, and flashmode was still there so it could be recovered.
I noticed that in some older versions of flashtool you sometimes had to click the kernel you wanted twice in order to get it to pick up the right one. Normally there's not much difference you can spot (most .ftf's just contain a loader and a kernel), but i had full SE firmware in .ftf format, which contained other sections too, and that's where i noticed it didn't always pick it up right at the first time of clicking.
SmG67 said:
Usually, whatever you flash, even if it goes bad, flashmode is still available because that doesn't get tampered with, the only true hardbrick i've ever seen is when flashing that x10blrelock.ftf, which happens quite a lot lately.
Just for fun i even formatted my entire phone once, no kernel, no rom, completely empty, and flashmode was still there so it could be recovered.
I noticed that in some older versions of flashtool you sometimes had to click the kernel you wanted twice in order to get it to pick up the right one. Normally there's not much difference you can spot (most .ftf's just contain a loader and a kernel), but i had full SE firmware in .ftf format, which contained other sections too, and that's where i noticed it didn't always pick it up right at the first time of clicking.
Click to expand...
Click to collapse
I understand what you mean and its really easy to make the mistake!! But well, still I don't think I made it but I guess there is nothing more to do anyway Thank you both for your help and I hope soon to return the favor on this forum :victory:
Can you tell me an average cost about the recovery process according to your experiance in your country?? Is is expensive in general?
zero2048 said:
I understand what you mean and its really easy to make the mistake!! But well, still I don't think I made it but I guess there is nothing more to do anyway Thank you both for your help and I hope soon to return the favor on this forum :victory:
Can you tell me an average cost about the recovery process according to your experiance in your country?? Is is expensive in general?
Click to expand...
Click to collapse
Someone in this forum had it done in Latvia for next to nothing.
In the USA it will cost you, your right arm.
zero2048 said:
I understand what you mean and its really easy to make the mistake!! But well, still I don't think I made it but I guess there is nothing more to do anyway Thank you both for your help and I hope soon to return the favor on this forum :victory:
Can you tell me an average cost about the recovery process according to your experiance in your country?? Is is expensive in general?
Click to expand...
Click to collapse
I just had a look online for prices in my country, it seems to be around €25.
SmG67 said:
I just had a look online for prices in my country, it seems to be around €25.
Click to expand...
Click to collapse
Emperor.dk said:
Someone in this forum had it done in Latvia for next to nothing.
In the USA it will cost you, your right arm.
Click to expand...
Click to collapse
Emperor.dk how old are you?
SmG67 thank you again and I will delete x10blrelock.ftf just in case....
hi guys, i have the same problem too, when my rom is minicm10 and my kernel is jb-naa-05, i want to go back to MiniCM7 because of green screen camera in MiniCM10 so i go back to MiniCM7, I flashed the right kernel e10-2.6.29.6-naa-14 for my x10 mini via flashtool and after i flash the kernel, my phone does not booting up(5 mins no booting up) so i decided to use seus but seus does not recognize my x10 mini, i try flashtool, but flashtool is not recognize my x10 mini so i tried to flash my created stock 2.1.ftf(thanks to leajian) and selected x10 mini from device selection(my x10 mini is not recognize in flashtool), then i wait until it finish, when i tried to open my phone, it boots up and show sony ericsson logo and it boots up(sucess!!!)...
sorry for my english...
so for all MiniCM10 Users, Dont try to go back to MiniCM7 If your Rom is MiniCM10 because it will cause your phone to not booting up like my problem.
Renz29 said:
hi guys, i have the same problem too, when my rom is minicm10 and my kernel is jb-naa-05, i want to go back to MiniCM7 because of green screen camera in MiniCM10 so i go back to MiniCM7, I flashed the right kernel e10-2.6.29.6-naa-14 for my x10 mini via flashtool and after i flash the kernel, my phone does not booting up(5 mins no booting up) so i decided to use seus but seus does not recognize my x10 mini, i try flashtool, but flashtool is not recognize my x10 mini so i tried to flash my created stock 2.1.ftf(thanks to leajian) and selected x10 mini from device selection(my x10 mini is not recognize in flashtool), then i wait until it finish, when i tried to open my phone, it boots up and show sony ericsson logo and it boots up(sucess!!!)...
sorry for my english...
so for all MiniCM10 Users, Dont try to go back to MiniCM7 If your Rom is MiniCM10 because it will cause your phone to not booting up like my problem.
Click to expand...
Click to collapse
If you follow nAa's instructions properly, there is no problem.
What you have to do:
Wipe data/factory reset in CWM on the JB-kernel
Flash the GB-kernel
Format /system, /data en /cache, so they get back to the original sizes
Flash the GB-ROM, or restore a previous GB-backup you may have had
No problems at all...
And your phone still had flashmode available, unlike the OP of this thread, so you don't have the 'same' problem
zero2048 said:
Emperor.dk how old are you?
Click to expand...
Click to collapse
Why?
If you are asking me on a date? LOL, the answer is no :laugh:
Hi,
My x10 shut down today after experiencing massive battery drain. When I plugged it into the charger, it didn't restart. I've tried flashing two different kernels, the FeraKernel for GB and DoomKernel. I also tried flasing the evervolv ftf file as a last resort. No change.
Is it dead? Anything I can do?
Flash original firmware with flashtool, also try to charge the battery and check if it isn't broken.
Sent from galaxy n7105
jakuburban said:
Flash original firmware with flashtool, also try to charge the battery and check if it isn't broken.
Sent from galaxy n7105
Click to expand...
Click to collapse
I checked the forums for the ftf file of the original firmware..I haven't found it till now. Anybody have it? Or could someone point me in the right direction?
inadequate said:
I checked the forums for the ftf file of the original firmware..I haven't found it till now. Anybody have it? Or could someone point me in the right direction?
Click to expand...
Click to collapse
Here's some: http://www.4shared.com/file/4xFnQHGj/sony_ericsson_x10i_21a0435_ora.html
jakuburban said:
Here's some: http://www.4shared.com/file/4xFnQHGj/sony_ericsson_x10i_21a0435_ora.html
Click to expand...
Click to collapse
Thanks. But when I flashed that, it wouldn't start up properly. I saw the Sony Ericsson logo for a second or two before the screen turned off again. WHen I tried to turn it on again, the red led flashed three times.
EDIT : after plugging it in, it woke up again. Looks like the X10 really won't die!
P.S you forgot to mention that that was an Eclairs ROM
inadequate said:
Thanks. But when I flashed that, it wouldn't start up properly. I saw the Sony Ericsson logo for a second or two before the screen turned off again. WHen I tried to turn it on again, the red led flashed three times.
Click to expand...
Click to collapse
From what you're indicating it sounds like your battery is dead/not holding a charge.
[a] You probably need a new battery, or charge the existing one for a good 12hrs and then see if it still holds a charge,
If not then go back to [a]
If possible you can just use SEUS (Sony Update Service) or PC Companion to flash the stock GB 2.3 Sony firmware.
inadequate said:
Thanks. But when I flashed that, it wouldn't start up properly. I saw the Sony Ericsson logo for a second or two before the screen turned off again. WHen I tried to turn it on again, the red led flashed three times.
EDIT : after plugging it in, it woke up again. Looks like the X10 really won't die!
P.S you forgot to mention that that was an Eclairs ROM
Click to expand...
Click to collapse
Well, I have always used this ROM to repair my Xperia.
The name was 2.1, so You could have seen that it's eclair.
And if You're still having problems with phone shuting down then it's for sure the battery, I had this problem.