I tried to install a custom rom and followed the instructions from this thread. All works fine until I did a fatal mistake: Instead of flashing the nAa kernel as described, I accidently flashed X10 V1 BLRelock that was previously chosen. Now my phone is completely dead, not detected by Flashtool or SEUS, I can't get it into flashmode (pressing 'back' while connecting) even after removing battery several times for different lasting periods.
Is there any chance to recover the phone or am I supposed to buy a new one?
Akrisios said:
I tried to install a custom rom and followed the instructions from this thread. All works fine until I did a fatal mistake: Instead of flashing the nAa kernel as described, I accidently flashed X10 V1 BLRelock that was previously chosen. Now my phone is completely dead, not detected by Flashtool or SEUS, I can't get it into flashmode (pressing 'back' while connecting) even after removing battery several times for different lasting periods.
Is there any chance to recover the phone or am I supposed to buy a new one?
Click to expand...
Click to collapse
Having a repair-shop JTag it may be cheaper than buying a new phone...
Well, unbricking by JTAG might be cheaper, of course - but is this the only chance? Anything I can do?
Akrisios said:
Well, unbricking by JTAG might be cheaper, of course - but is this the only chance? Anything I can do?
Click to expand...
Click to collapse
It seems to happen a lot lately, that people flash the x10blrelock.ftf, and it always bricks their phone, don't think anyone has a home-solution for that yet.
SmG67 said:
It seems to happen a lot lately, that people flash the x10blrelock.ftf, and it always bricks their phone, don't think anyone has a home-solution for that yet.
Click to expand...
Click to collapse
Can the flash-tool be upgraded to test if a custom kernel is installed before someone try to flash the bootloader relock-ftf, and then simply deny to flash x10blrelock.ftf?
Emperor.dk said:
Can the flash-tool be upgraded to test if a custom kernel is installed before someone try to flash the bootloader relock-ftf, and then simply deny to flash x10blrelock.ftf?
Click to expand...
Click to collapse
Doesn't seem to matter whether you're on stock or custom kernel, the x10Blrelock just bricks the phones. If you need to relock the bootloader for some reason use S1Tool's Restore option.
The best advice i can give at this moment is to just remove the x10blrelock.ftf from the flashtool/firmwares sub-folder so it can't get flashed by accident.
SmG67 said:
Doesn't seem to matter whether you're on stock or custom kernel, the x10Blrelock just bricks the phones. If you need to relock the bootloader for some reason use S1Tool's Restore option.
The best advice i can give at this moment is to just remove the x10blrelock.ftf from the flashtool/firmwares sub-folder so it can't get flashed by accident.
Click to expand...
Click to collapse
we should have a sticky thread (locked for no replies) with a list of read-first-warnings/what-never-to-do for our minnies. not a loong guide, just a simple list. i think it would serve an important purpose and avoid a lot of bricks for first-time-flash-users.
even I managed to brick my X10MP first time I flashed a ROM. it was loooooong before bootloader-unlock was possible, so very easy to fix.
Well guys, today the postman brought my x10mini pro back from the jtag shop. They did a quite good job by jtagging it for installing an original firmware. The issue is: This one seems to be older than the one I once had. I tried to update the software via PC Companion but there is no higher version available.
For installing CM7-2.2.1 I need Firmware Latest 2.1.1.A.0.6 with Baseband: M76XX-TSNCJOLYM-53404015 - this I had before bricking it.
Now I only have 2.1.1.A.0.54. Where do I get the latest update if not from SE itself?
Akrisios said:
Well guys, today the postman brought my x10mini pro back from the jtag shop. They did a quite good job by jtagging it for installing an original firmware. The issue is: This one seems to be older than the one I once had. I tried to update the software via PC Companion but there is no higher version available.
For installing CM7-2.2.1 I need Firmware Latest 2.1.1.A.0.6 with Baseband: M76XX-TSNCJOLYM-53404015 - this I had before bricking it.
Now I only have 2.1.1.A.0.54. Where do I get the latest update if not from SE itself?
Click to expand...
Click to collapse
I think you *should* be ok as long as the baseband is the required version, but there are original firmwares available in the x10 mini pro development section. There is a kernel+baseband package here
( And don't forget to delete the x10blrelock.ftf package from the flashtool\firmwares subfolder )
SmG67 said:
And don't forget to delete the x10blrelock.ftf package from the flashtool\firmwares subfolder
Click to expand...
Click to collapse
This was the first thing I've done after bricking the device
I now installed your linked fw/baseband version, it states the correct baseband ending with ...15 now, but the build goes to 2.0.A.0.504
OK... I did it too... I hard bricked it... now I want to repair it myself, but I will need some help.
I bought these things:
...
Segger J-Link: http://www.segger.com/jlink_base.html
...
GPG Industries u20i resurrection cable: http://www.gsmsp.com/products/Servi...e_for_U20i__by_GPGindustries__1209_19715.html
...
The cable has a battery slot that has no pins (I guess they are not needed), but I soldered them out (just in case) so the battery fits and I can set it on top of the cable so it can power the phone with the J-Link plugged on if needed.
I have a problem finding the correct config files for the J-Link to reprogram the phone. I can't get it to recognize the phone. Maybe I'm doing something wrong in the whole procedure. I don't know... I would be glad if someone experienced with Segger J-Link could help me.
I was watching videos on YouTube about resurrecting the phone with a Riff Box... then I checked, the both boxes have same pin-outs... more the J-Link has a power pin plus, that the Riff box is missing.
X10 Mini totally dead bricked
Congrats!!! Happened to me too just now.
Let me know your progress will order cables but it might take a while for me to get them hence I´m in Brazil.
Question
Akrisios said:
Well, unbricking by JTAG might be cheaper, of course - but is this the only chance? Anything I can do?
Click to expand...
Click to collapse
i found this link :
http://forum.xda-developers.com/showthread.php?p=51706478
are this method work?
Akrisios said:
I tried to install a custom rom and followed the instructions from this thread. All works fine until I did a fatal mistake: Instead of flashing the nAa kernel as described, I accidently flashed X10 V1 BLRelock that was previously chosen. Now my phone is completely dead, not detected by Flashtool or SEUS, I can't get it into flashmode (pressing 'back' while connecting) even after removing battery several times for different lasting periods.
Is there any chance to recover the phone or am I supposed to buy a new one?
Click to expand...
Click to collapse
i m also facing the same problem any one has a solution pls reply
Priyesh512 said:
i m also facing the same problem any one has a solution pls reply
Click to expand...
Click to collapse
Try JTAG
Related
Hi there.
I tried downgrading my 2.3.4 xperia neo to 2.3.2 to root it. It worked, but I have the battery problem and I've heard it's a common issue.
I tried removing the battery for more than 10 min and reinserting it.
I tried upgrading to the latest official ICS with PC companion (strangely enough I could upgrade from 2.3.2 although it showed no new upgrades while in 2.3.4). Didn't solve the problem.
I tried flashing a the stock 2.3.4 rom. Didn't solve the problem.
I found following two threads:
http://forum.xda-developers.com/showthread.php?t=1312398
http://forum.xda-developers.com/showthread.php?t=1510703
Unfortunatly, both of these workarounds require an unlocked bootloader. The problem is, I don't seem to be able to connect my phone to the PC in this unlock bootloader mode, maybe because as soon as I remove the USB cable it thinks it has no battery left and turns all systems off?
I also found this thread for locked bootloaders, but only applicable for the arc: http://forum.xda-developers.com/showthread.php?t=1465702
Is there something like this for the neo? If not is it easy to make?
To summarize, I can flash new roms, but I'm not able to unlock my bootloader. Is there something I could do? Thanks in advance for your help
charge your phone to 100%
take out sim card and memory card .highly recommend to format your card
flash phone using suse or flashtools
and when done replace sim and memory card
then everything is clean
works a treat i have amazing battery life on ics 4.0.4
@OP: Have you try to unlock bootloader wit unofficial way? With s1tool? Check neo v development section for more info.
jasonvoor said:
charge your phone to 100%
take out sim card and memory card .highly recommend to format your card
flash phone using suse or flashtools
and when done replace sim and memory card
Click to expand...
Click to collapse
Have you even read his post?
He already tried flashing.
Which wont help him, because he have 0% problem, because he flashed 2.3.2.
If you don't know about that bug, google a bit.
Madfysh said:
@OP: Have you try to unlock bootloader wit unofficial way? With s1tool? Check neo v development section for more info.
Click to expand...
Click to collapse
Thanks, I'm not sure I like this method, but as it's my only choice at the moment I will try it out, as soon as I can get my hand on the needed materials.
In the meantime, is there any chance somebody could make an locked bootloader workaround like this for the xperia neo? http://forum.xda-developers.com/showthread.php?t=1465702
How much programming skills does it require?
It seems to be the easiest method. I just need my phone to realise it's charged for a few hours, until I can unlock the bootloader and install one of the custom roms workarounds
Thanks again for your quick replies
That kernel module would need to be compiled against whatever kernel you have installed. Chances are it may work 42.
But if you're going to unlock anyway, it's pointless. It's kernels that support the workaround not roms. S1tool works even with the battery out, therefore unlocking is the better option.
There's good tutorials here for unlocking, once done insert battery and leave connected to s1tool, some power will reach the battery, flash your custom kernel of choice.
Sent from my MT11i using XDA
Thanks a lot, I found and followed this guide http://androidflip.com/unlock-xperia-phones-bootloader-without-losing-drm-data-track-id-working/ (bad english, but pretty detailed) and now my bootloader is unlocked.
Unfortunatly, I have a pretty noobish question now: where should the boot.img be stored to upgrade the kernel with s1tool? I tried the s1tool file or the SDcard of the phone, but I just get this message:
Selecct firmware packages
You can select few packages with CTRL button
without any option to actually select anything? Am I doing something wrong? (I decided to take the patched stock kernel v9.6 from this thread http://forum.xda-developers.com/showthread.php?t=1468043)
Until now I've flashed the roms using flashtool and .ftf images. Is it possible to do something similar now? (I'd like to use the patched Cyanogen mod, but in my limited understanding you need to flash the kernel first)
Once your bootloader is unlocked, use flashtool to flash kernel.
Click the lightening symbol, select fastboot mode select kernel to flash.
One more thing, not all kernels match all roms, however most of them have the battery patch, for cm7/9 you need to use the fxp kernel. 9.6 nightelf is for gingerbread.
Sent from my MT11i using XDA
For kernel installation, read this: http://forum.xda-developers.com/showpost.php?p=20649481&postcount=3
EDIT: damn, I really need to start refreshing threads before replying
mpiekp was faster
I think I need a clarification: if you need to flash a new rom you hold the back-button while plugging the USB-cable and see a green LED, if you need to flash a new kernel or unlock the bootloader you hold the menu button and see a blue LED?
Because my problem is that I the green LED part works (for example when I flashed my stock 2.3.4 rom), but I when I hold the menu button and plug the USB cable nothing happens (after a while it shows the red LED for charging I think). ThatI was my problem when I wanted to unlock the bootloader the official way and now I see you have to do the same to flash a new kernel
EDIT: According to the thread you kindly provided
EDIT2: Never mind, I think this time it works. Wish me luck
Thanks a lot, you've both been very helpful
It seems to work just fine right now
Help
I have the same problem, pleas help me, tell me what steps did you followed to get the phone working back.
Thanks.
Hello,
I flashed the most recent MiniCM9-3.0.2 ROM with nAa ICS kernel and followed all steps carefully. Everything works except i get no service. I can find the service network (vodafone) but i cannot connect to it. I've tried to go back to stock kernel and miniCMPro 21 and i get no service as well. Any help?
Thanks
nvm... I figured it was a bootloader-issue, but i guess since you can still find the network your gsm is still working.
In any case, you're on stock rom, try relocking your bootloader and see if you can connect to the network then (Restore-button in S1-Tool)
Hi,
I'll try to restore and see if it works.
Thanks for the help.
Hi,
I restored and reinstalled CM9 and now everything is working! Thanks
i am in exactly the same boat, just flashed same rom and same kernal and now no service, i also was under the impression if i unlocked the bootloader it unlocked phone to all networks but my virgin sim would not work either, the phone was originally on orange and my orange sim worked before i done this, what do i need to do guys just flash back stock rom, if so where can i find this, thanks!
You need to use PC Companion or SEUS from Sony Ericsson to repair your phone, and then relock your bootloader with the Restore-button in S1Tool.
There is a big difference between sim-unlocking your phone, and boot-unlocking your phone.
The first one will allow you to go on other networks, the second one will allow you to flash a custom kernel.
If you want to unlock your bootloader, follow the tutorial and make sure your simlock-certificate is compatible, otherwise, obtain an EMMA/IMEI code from your provider to get your phone on other networks. In that case you can unlock your bootloader too.
There are plenty of warnings in the bootloader-unlock tutorial to prevent you from bricking your phone, if you don't understand the options that are there, don't mess with your phone.
iv tried using the repair function of pc companion but it just says no updates available for this phone, and i cant seem to find SEUS can anyone point me in the right direction please.
think i made a mistake last night though while messing, i locked the bootloader back up, had the capital R where needed, but i had a custom rom but i had flashed back the stock kernel by mistake, now the phone sits with sony ericsson on screen and doesnt do anything else, been that way for hours now, any help really appreciated!
Hi
I had the same problem. The easy way is to put the phone back to stck and start all over again. You can find SEUS here (search on google)
update_service_setup-2.11.4.11.exe
After install it just follow the instructions. When it says no update was found just click next anyway. it will restore the phone. And then start from that point:
unlock bootloader, flash kernel and install new Rom imediatly after flash kernel. DONT LET YOU PHONE START WIHT OTHER ROM OTHERWISE IT WILL GET THE SMA PROBLEM! Put the ROM file in the SD card and after install new kernel go imediatley to CWM and install the ROM.
It should work!
cheers mate iv just downloaded it and run it, this is all that happens once i restart in flashmode, any ideas
Go to the Development section for your phone in this forum and try to find a ROM that is based on the stock rom (I think you should still be able to nstall xRecovery on your phone and enter it), then flash it just like you would other custom roms.
how can i go about installing xrecovery mate as i cant access phone the way it is, i can get it into flashmode, using the power and home button then using back quickly after i restart, iv tried flashing a custom kernel back onto it too from flashtool but it gives an error and doesnt do anything, if only i could get that kernel back on at least just to get it out of the freezing!
Open flashtool and connect your turned-on phone through usb, if it says phone connected with usb-debugging, you can use flashtool to install xrecovery and reboot into that.
SmG67 said:
Open flashtool and connect your turned-on phone through usb, if it says phone connected with usb-debugging, you can use flashtool to install xrecovery and reboot into that.
Click to expand...
Click to collapse
its saying device connected with usb debugging off, lol, what now, is there anyway to flash back to stock via flashtool as i have stock e10i 2.1 uk stock rom, if so how mate, appreciate the help! iv really jumped in at the deep end and got all confused, used to flashing samsungs!
are you on the X10Mini (E10, robyn), or X10MiniPro (U20, mimmi)?
SmG67 said:
are you on the X10Mini (E10, robyn), or X10MiniPro (U20, mimmi)?
Click to expand...
Click to collapse
its the x10 mini mate, e10 model!
ok hang on
this is caused by your x10mini conditions just flash stock with flashtoll and if you want checke it with seus it will have a repair button
Theliakos said:
this is caused by your x10mini conditions just flash stock with flashtoll and if you want checke it with seus it will have a repair button
Click to expand...
Click to collapse
im unsure of how to do that mate,do i need to put the stock rom inthe firmware folder same as i did for the kernel as i tried but it didnt show up, any guidance is much appreciated!
big-hol said:
im unsure of how to do that mate,do i need to put the stock rom inthe firmware folder same as i did for the kernel as i tried but it didnt show up, any guidance is much appreciated!
Click to expand...
Click to collapse
Check your inbox
ok guys this is what im getting when trying to flash stock rom via flash tool
Is there a way to root my officialy updated to ICS, Xperia Mini(ST15i) without unlocking bootloader?(in order to downgrade etc...) I just want to root my xperia mini without messing up with the warranty....Any way to root it with locked bootloader? (4.1.B.0.431)
Thanks in advance
You have to downgrade to Gingerbread, root it and then upgrade to ICS using THIS tutorial.
There could be a different way: you should flash the 4.0.3 kernel (for example the Arc one), but I can't find the tutorial. Use the search button and see if you can find it
Feanor88 said:
You have to downgrade to Gingerbread, root it and then upgrade to ICS using THIS tutorial.
There could be a different way: you should flash the 4.0.3 kernel (for example the Arc one), but I can't find the tutorial. Use the search button and see if you can find it
Click to expand...
Click to collapse
downgrading needs unlocked bootloader... :/ i had bricked my mini some time ago because i tried to downgrade with locked... (( any other way?
Thanks
EDIT: flashing xperia arc's or Neo V's for example would brick my phone....wouldn't it? (and it also needs bootloader unlock...so i don't think i would do that... BUT thanks for your help mate
No, flashing a .ftf does NOT need an unlocked bootloader. You need to unlock it only if you want to flash a custom kernel, but for custom ROMs you can use flashtool.
Same for the 4.0.3 kernel. It's a stock kernel, so you can flash it via flashtool
It WILL end in bootloop, though. The tutorial says you can use DoomLord's root kit anyway, root the phone and then flash again the 4.0.4 kernel. But find it and read it carefully, cause I didn't try it and I can't assure you it will work.
I tried the first one I suggested, though, and my bootloader is locked!
Feanor88 said:
No, flashing a .ftf does NOT need an unlocked bootloader. You need to unlock it only if you want to flash a custom kernel, but for custom ROMs you can use flashtool.
Same for the 4.0.3 kernel. It's a stock kernel, so you can flash it via flashtool
It WILL end in bootloop, though. The tutorial says you can use DoomLord's root kit anyway, root the phone and then flash again the 4.0.4 kernel. But find it and read it carefully, cause I didn't try it and I can't assure you it will work.
I tried the first one I suggested, though, and my bootloader is locked!
Click to expand...
Click to collapse
man i have a problem...when i place my phone into flashmode (down key) it disconnects on its own...and that's why i bricked my phone long time ago....now i am afraid to do that i have installed the flashtool drivers from Flashtool/drivers.... but they mustn't work for my mini....any solution please give me the drivers you use for your Mini and work with it if you can i would really appreciate that!
What do you mean, it disconnects? How much time does it take for it to disconnect? Mine does the same. If I plug it and wait for a minute or so doing nothing, it disconnects. But if I start flashing a ROM it doesn't.
The drivers I installed are in \Flashtool\drivers.
Feanor88 said:
What do you mean, it disconnects? How much time does it take for it to disconnect? Mine does the same. If I plug it and wait for a minute or so doing nothing, it disconnects. But if I start flashing a ROM it doesn't.
The drivers I installed are in \Flashtool\drivers.
Click to expand...
Click to collapse
it takes about 1-2 minutes to disconnect.But, what if it disconnects while on downgrading?
It doesn't. At least, mine doesn't! And I flashed firmware twice a day in the last week
Anyway, both ways need the use of flashtool... so if you don't want to try it, you can't root ICS
Feanor88 said:
It doesn't. At least, mine doesn't! And I flashed firmware twice a day in the last week
Anyway, both ways need the use of flashtool... so if you don't want to try it, you can't root ICS
Click to expand...
Click to collapse
Pfff i'm a bit scared.....there is no hope that there will be somewhen another way to root...?
No, I'm sorry. Anyway, just follow this steps:
1) DON'T plug your phone.
2) Open flashtool
3) Click the lightning icon and select flashmode
4) Select the .ftf you want to flash: if you want to downgrade, select wipe data. If you want to flash the 4.0.3 kernel, unckeck wipe data and check "exclude" for everything apart from kernel. Which means you'll only flash the kernel
5) Start: you'll be asked to plug your phone. Plug it now in flashmode. This way you'll avoid it being unplugged.
Flashing will start, and your phone won't be unplugged. I suppose it's unplugged automatically when you're not doing anything, it's the same for me, but I repeat, whenever I flash something (kernel, whole ROM, whatever) everything just goes fine
Feanor88 said:
No, I'm sorry. Anyway, just follow this steps:
1) DON'T plug your phone.
2) Open flashtool
3) Click the lightning icon and select flashmode
4) Select the .ftf you want to flash: if you want to downgrade, select wipe data. If you want to flash the 4.0.3 kernel, unckeck wipe data and check "exclude" for everything apart from kernel. Which means you'll only flash the kernel
5) Start: you'll be asked to plug your phone. Plug it now in flashmode. This way you'll avoid it being unplugged.
Flashing will start, and your phone won't be unplugged. I suppose it's unplugged automatically when you're not doing anything, it's the same for me, but I repeat, whenever I flash something (kernel, whole ROM, whatever) everything just goes fine
Click to expand...
Click to collapse
i maybe try it later... thanks for your replies man DD i appreciate that
kwstas 13 said:
i maybe try it later... thanks for your replies man DD i appreciate that
Click to expand...
Click to collapse
Let me know if you need more help!
Feanor88 said:
Let me know if you need more help!
Click to expand...
Click to collapse
A friend of mine told me that if i try with locked bootloader is a simple suicide!!! :/ Now i am confused again :S
kwstas 13 said:
A friend of mine told me that if i try with locked bootloader is a simple suicide!!! :/ Now i am confused again :S
Click to expand...
Click to collapse
Who is that friend of you? He is trolling. Stay away from him. And learn this. Feanor here is a better friend for you than him, when it comes to rooting your phone.
Just do as in the tutorial Fenor had shared in his first post. Everything will be fine.
And you say you bricked your phone. May we know how your repaired it?
Thanks,
Rick
Sent from my SK17i using XDA
DragonClawsAreSharp said:
Feanor here is a better friend for you than him, when it comes to rooting your phone.
Click to expand...
Click to collapse
Blushing
But don't forget I'm a noob after all... I'll just keep pointing other people's tutorials, like for example yours, Rick
DragonClawsAreSharp said:
Who is that friend of you? He is trolling. Stay away from him. And learn this. Feanor here is a better friend for you than him, when it comes to rooting your phone.
Just do as in the tutorial Fenor had shared in his first post. Everything will be fine.
And you say you bricked your phone. May we know how your repaired it?
Thanks,
Rick
Sent from my SK17i using XDA
Click to expand...
Click to collapse
while i was downgrading with locked bootloader the procces stopped on its own at 43%....and my phone wouldn't turn on and didn't even worked with flashtool....i sent it to a service centre and they fixed it ( i think i hadn't installed the proper drivers....am i right?)
kwstas 13 said:
while i was downgrading with locked bootloader the procces stopped on its own at 43%....and my phone wouldn't turn on and didn't even worked with flashtool....i sent it to a service centre and they fixed it ( i think i hadn't installed the proper drivers....am i right?)
Click to expand...
Click to collapse
That's strange. Anyway, if you installed PC Companion you have adb drivers. Install flashmode drivers from Flashtool installazion folder, you find the executable in \Flashtool\drivers. If Windows prompts you that the drivers are dangerous, just install them anyway.
What I can say is that you DON'T need to unlock your bootloader to use flashmode in Flashtool. Otherwise, my phone would have exploded long ago
Now let me tell you this: if you are SURE you did everything the right way, and still your phone got bricked, then maybe you shouldn't try. you never know.
If you tried to to something you didn't know how to do, you probably made a mistake, and that's why the phone got bricked.In this case, I'd give it a try.
But we're not able to see your phone and test it, so whatever you do, unfortunately, you always do it on your own risk.
I couldn't be more sincere.
kwstas 13 said:
while i was downgrading with locked bootloader the procces stopped on its own at 43%....and my phone wouldn't turn on and didn't even worked with flashtool....i sent it to a service centre and they fixed it ( i think i hadn't installed the proper drivers....am i right?)
Click to expand...
Click to collapse
On all probability you are correct.
They (The service centre people) flashed a firmware using Flashtool. That's what they must have did. See. I will explain things a bit.
Your phone has some memory in it (this corresponds to what was known as phone memory in older phones). This memory is of Read Only type. That is ROM. Now, of all the types of ROMs, androids have EEPROM. That stands for Electronically Erasable Programmable ROM. So you can electronically erase the data stored in the ROM and write new data on it (even though it is called Read Only). This process of writing new data on the ROM is called flashing.
For flashing, the tool that is available to us as an open source, is Flashtool. Using it we can flash ROMs into our phones, erasing the earlier ones.
Now, Sony will not want us to flash Cyanogen Mod to our phones. So they have made up the concept of locking the bootloaders. With locked bootloaders custom ROMs can not be flashed to your phone. This is because most custom ROMs are designed for a specific Kernel (the intermediate between the OS and the hardware), and flashing a custom kernel requires unlocked bootloaders.
If you want, you can flash firmwares (ROMs + Kernels released by Sony) even if you are on locked bootloader, as long as the firmware files are signed by Sony.
This restriction however is against the OpenSource spirit of Android, and thus Sony gives us the scope to unlock bootloader at the cost of loosing the warranty, and the DRM keys (search google for that).
Now coming to your problem of unability to flash properly, make sure that you have installed all the drivers. For that open up /drivers folder in /flashtool and install the .exe there. Also install the adb drivers of your device. For that have PC Companion installed on your PC. Flashing will happen properly then.
Thanks,
Rick
Sent from my SK17i using XDA
DragonClawsAreSharp said:
On all probability you are correct.
They (The service centre people) flashed a firmware using Flashtool. That's what they must have did. See. I will explain things a bit.
Your phone has some memory in it (this corresponds to what was known as phone memory in older phones). This memory is of Read Only type. That is ROM. Now, of all the types of ROMs, androids have EEPROM. That stands for Electronically Erasable Programmable ROM. So you can electronically erase the data stored in the ROM and write new data on it (even though it is called Read Only). This process of writing new data on the ROM is called flashing.
For flashing, the tool that is available to us as an open source, is Flashtool. Using it we can flash ROMs into our phones, erasing the earlier ones.
Now, Sony will not want us to flash Cyanogen Mod to our phones. So they have made up the concept of locking the bootloaders. With locked bootloaders custom ROMs can not be flashed to your phone. This is because most custom ROMs are designed for a specific Kernel (the intermediate between the OS and the hardware), and flashing a custom kernel requires unlocked bootloaders.
If you want, you can flash firmwares (ROMs + Kernels released by Sony) even if you are on locked bootloader, as long as the firmware files are signed by Sony.
This restriction however is against the OpenSource spirit of Android, and thus Sony gives us the scope to unlock bootloader at the cost of loosing the warranty, and the DRM keys (search google for that).
Now coming to your problem of unability to flash properly, make sure that you have installed all the drivers. For that open up /drivers folder in /flashtool and install the .exe there. Also install the adb drivers of your device. For that have PC Companion installed on your PC. Flashing will happen properly then.
Thanks,
Rick
Sent from my SK17i using XDA
Click to expand...
Click to collapse
You, and all developers/people here, are simply awesome!.... But this sh*t with unlocking bootloader and loosing warranty is so....stupid....I think i will give it a try and i am gonna sure thank you.... Somethink else....my phone has also a problem on the screen while scrolling....do you know if that is a hardware or a firmware problem?
What do i mean when i say scroll problem:
1st example: While browsing the Internet and scroll with fast moves, links are pressed on its own and new tabs are opened,as links are pressed.
2nd example: While i scroll the app drawer,fast s make apps open without my will....
3nd exapmle and the most representative: While playing fruit ninja and do fast moves to cut the fruits, the touchscreen doesn't even fell that i touch the screen!!! I do fast moves to cut the fruits and nothing happens!! As a result i always lose! (just joking....)
My phone is fast and really smooth only when my moves are slow....any thoughts about that? :/
Thanks once again for your BRAVE help!
You have a Mini, right? That's a hardware problem. Very common, even if not everyone realizes it. Check THIS thread for a (possible?) solution.
Hey,
I have Xperia X10 mini, 2.1.1.A.0.6 build for stock.
I rooted him, install the nAa-14 kernel and MiniCM7-2.2.1 room, and it worked ok.
It's all beginning with trying to change the the room but then i got a problem, loop-boot.
I thought maybe the kernel doesn't fit for the room so i change for CE kernel, which then i got a black screen.
So, i reinstall nAa-14 and MiniCM7-2.2.1, but still got the loop-boot.
I tried several kernels but nothing worked.
Then i thought maybe the CE kernel doesn't work because the phone is rooted , so i un-root him, and it didn't work.
I tried also the Sopc and Update service without a succeed (i tried the update and repair options but i got no option to reinstall it, just notice me i got the last update)
One hour ago i saw the TUTORIAL]Up/Downgrading, ReFlash/ing, Rooting/xRecovery[For Noobs ONLY]
I'm a truly a Noob.
So i tried to root the phone again(SuperOneClick) but with no succeed, It's stuck on "waiting for device"
Then i noticed that the Sopc recognizing my phone as Xperia X8 (wtf?!)
Install the drivers for X8 doesn't help.
This is a dead end for my phone?
did22 said:
Hey,
I have Xperia X10 mini, 2.1.1.A.0.6 build for stock.
I rooted him, install the nAa-14 kernel and MiniCM7-2.2.1 room, and it worked ok.
It's all beginning with trying to change the the room but then i got a problem, loop-boot.
I thought maybe the kernel doesn't fit for the room so i change for CE kernel, which then i got a black screen.
So, i reinstall nAa-14 and MiniCM7-2.2.1, but still got the loop-boot.
I tried several kernels but nothing worked.
Then i thought maybe the CE kernel doesn't work because the phone is rooted , so i un-root him, and it didn't work.
I tried also the Sopc and Update service without a succeed (i tried the update and repair options but i got no option to reinstall it, just notice me i got the last update)
One hour ago i saw the TUTORIAL]Up/Downgrading, ReFlash/ing, Rooting/xRecovery[For Noobs ONLY]
I'm a truly a Noob.
So i tried to root the phone again(SuperOneClick) but with no succeed, It's stuck on "waiting for device"
Then i noticed that the Sopc recognizing my phone as Xperia X8 (wtf?!)
Install the drivers for X8 doesn't help.
This is a dead end for my phone?
Click to expand...
Click to collapse
As long as the phone does at least something there's a way to get out of it
Download this, it's original 2.1 firmware for the x10Mini for flashtool, put it in the flashtool firmwares folder and flash it. Afterwards you can do other stuff again, like installing naa-14 and minicm7, or, if you want another rom, make sure you've got the right kernel for it too.
it was E10a, and the link is for I
does is matter?
did22 said:
it was E10a, and the link is for I
does is matter?
Click to expand...
Click to collapse
I think the i supports more 3g frequencies than the a, but the ones the a supports are also supported by the i firmware. I think it should work. just try it, it won't break your phone. In any case, it won't get worse than it is now.
SmG67 said:
I think the i supports more 3g frequencies than the a, but the ones the a supports are also supported by the i firmware. I think it should work. just try it, it won't break your phone. In any case, it won't get worse than it is now.
Click to expand...
Click to collapse
I got that error
16/020/2012 20:20:14 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed"
16/020/2012 20:20:14 - ERROR - Error flashing. Aborted
did22 said:
I got that error
16/020/2012 20:20:14 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed"
16/020/2012 20:20:14 - ERROR - Error flashing. Aborted
Click to expand...
Click to collapse
Did you by any chance relock your bootloader in your efforts to unbrick your phone?
did22 said:
Then i thought maybe the CE kernel doesn't work because the phone is rooted , so i un-root him, and it didn't work.
Click to expand...
Click to collapse
did22 said:
Click to expand...
Click to collapse
(un)rooting and (un)locking the bootloader are NOT the same thing
try this instead.
What is the difference?
I did "Restore" on S1tool
maybe try SEUS
the locked version worked.
Thank you !!
so now, if i want install MIN-08 without break it down, what should i do? root the phone?
btw what it is "locked" mean?
did22 said:
the locked version worked.
Thank you !!
so now, if i want install MIN-08 without break it down, what should i do? root the phone?
btw what it is "locked" mean?
Click to expand...
Click to collapse
locked means it's got the original bootloader for your phone, the other one i sent you had the 'unlocked' loader. Min-08 works on the stock kernel, so you should just root your phone (use the padlock button in flashtool) install xrecovery (the +-button in flashtool).
Put this on your sd-card and flash it with xrecovery, it will install CWM and replace xrecovery.
Then put Min-08.zip onto your sd-card and flash it with the newly installed CWM.
Good Luck
did22 said:
Hey,
I have Xperia X10 mini, 2.1.1.A.0.6 build for stock.
I rooted him, install the nAa-14 kernel and MiniCM7-2.2.1 room, and it worked ok.
It's all beginning with trying to change the the room but then i got a problem, loop-boot.
I thought maybe the kernel doesn't fit for the room so i change for CE kernel, which then i got a black screen.
So, i reinstall nAa-14 and MiniCM7-2.2.1, but still got the loop-boot.
I tried several kernels but nothing worked.
Then i thought maybe the CE kernel doesn't work because the phone is rooted , so i un-root him, and it didn't work.
I tried also the Sopc and Update service without a succeed (i tried the update and repair options but i got no option to reinstall it, just notice me i got the last update)
One hour ago i saw the TUTORIAL]Up/Downgrading, ReFlash/ing, Rooting/xRecovery[For Noobs ONLY]
I'm a truly a Noob.
So i tried to root the phone again(SuperOneClick) but with no succeed, It's stuck on "waiting for device"
Then i noticed that the Sopc recognizing my phone as Xperia X8 (wtf?!)
Install the drivers for X8 doesn't help.
This is a dead end for my phone?
Click to expand...
Click to collapse
Use flashtool, download stock firmware and flash. i revive my x10mini too
Any ideas on how to fix my Xperia Ray? HELP..
Quick backstory - my Xperia Ray won't read my SIM card anymore. It doesn't even ask for my PIN number, it just boots as normal (after asking me to pick a language) but I have no connection to any network. I've tried using the SIM card in another phone and it works fine, therefore the problem is with the phone itself.
I'd recently had my phone network & bootloader unlocked by wotanserver using the test point method - because of this I thought the DRM keys would be fine (e.g. TrackId & Timescape still worked). However, when I was updating from GB .42 to .62 OTA (to flash a GB ROM) my phone bricked! (Does this mean the DRM keys weren't intact? Confused.)
So, I searched for a solution and ended up using s1tool to relock the bootloader. Then I used flashtool to flash a stock ICS ftf file. It seemed to work (the phone rebooted) but it was then I noticed that the SIM card wasn't being recognised. Also, in the Flashtool log I noticed that a blue line was there saying 'this file is ignored simlock.ta'.
Anyway, my real dilemma is - which of the Available Omnius Operations for the Xperia Ray (see link: http://www.omnius-server.com/phone?id=20… should I pick to fix this?
Backup TA
Flash
Identify
Live boot
Repair S1-boot
Restore TA
Revive phone after OTA flash
Unlock bootloader
Unlock network lock by certificate replacement
Repair S1boot? Restore TA? I really don't know. Would really. really appreciate someone's help - I need my phone back urgently!
Updating via OTA on an unlocked bootloader does lead to a bricked Phone, which just requires THIS to fix it.
XperienceD said:
Updating via OTA on an unlocked bootloader does lead to a bricked Phone, which just requires THIS to fix it.
Click to expand...
Click to collapse
Hi, thanks for your reply! I'm not sure what you mean though - the link provided in the first post on that thread took me to a dodgy website to download a file called 'downloadmanager
_setup' All that did was install crap like 'Zoomdownloader' and other non-android related rubbish on my computer. So I'm not best pleased about that...
Anyhoo, my phone isn't really bricked - it works fine apart from the SIM problem. I was asking what fix in the Omnius list of options applied to my situation. Do I need to Repair S1-boot? Do I need to 'Restore TA?' I really don't know to be honest.
All I really need to know is what option from Omnius's list applies to my situation...
seamo123 said:
Hi, thanks for your reply! I'm not sure what you mean though - the link provided in the first post on that thread took me to a dodgy website to download a file called 'downloadmanager
_setup' All that did was install crap like 'Zoomdownloader' and other non-android related rubbish on my computer. So I'm not best pleased about that...
Click to expand...
Click to collapse
Just checked the link myself, as it didn't skip the ad and asked you to download something else instead, that should have rang alarm bells. This is what you should have downloaded - FlashTool_0.2.9.1_FOTAUnbrick
seamo123 said:
Anyhoo, my phone isn't really bricked - it works fine apart from the SIM problem.
Click to expand...
Click to collapse
Your Phone was bricked in the first place due to an OTA update, and should actually state in what ever thread you used to unlock not to use the OTA feature after doing so, the attachment normally fixes that, given that you've re-locked using S1Tool then you may have done more harm than good. If I knew what option to suggest I would have done so, so unless anyone else does then it's trial and error I'm afraid.
Is it too late for me to give the link you gave me a shot then? Or might it do more harm than good at this stage? Thanks for your help btw, I appreciate it.
seamo123 said:
Is it too late for me to give the link you gave me a shot then? Or might it do more harm than good at this stage? Thanks for your help btw, I appreciate it.
Click to expand...
Click to collapse
You could try to unlock the boot loader again, flash stock ICS and kernel and try again to connect the sim card...
Or have you tried PC companion to fix your phone? Try this first!
But I can't promise anything, maybe you will end up in a bigger problem than now
Sent from my Nexus 7 running Android 4.2.1