I tried to unlock bootloader following the guide on the developer section (actually, only the "guide" in the header, 1 step). I tried multiple times, and this always happen (attachment)
edited:
This seems to be the situation for the fxp 123 too.
--
As I'm a noob. I have no idea whether to flash the fxp 123 with our without bootloader. Anyhow.. as my question says.. I can't do ether.
odd,
i actually did the exact same thing and its fine here.
this is what your trying to do yes ?(below)
•flash the azuzu kernel downgrade ftf with flashtool
•disconnect usb cable, press power button until phone vibrates shortly and immidiatly connect the usb cable again (it is supposed to be stuck at SE logo)
•start the batch file for unlocking bootloader, cause it says press any button before it starts, it won't start unlocking until you press any button
•now wait until flashtool recognizes your x10 (if flashtool doesn't do anything, check third post please! thx)
•close flashtool and then press any button in the cmd window that the unlocking process starts (please close flashtool, instead the bl unlock cmd and flashtool are constantly killing and restarting adb!!)
•after unlocking is finish you have to flash azuzu kernel upgrade
•now power on phone to check if the phone is starting after the unlock (if you are using a custom kernel yet with the bypass method and get stuck in a bootloop enter xrecovery and clear dalvik-cache, then your phone should boot up again fine)
•power off phone and flash dooms ck v05-fs with flashtool
•now flash the wifi modules for dooms ck with recovery. (atm the update.zips are for xrec, but for sure please always check dooms kernel-thread if there is anything changed)
•power on phone again and if everything is right, read the line under that one
•WOOOHOOO!!! Here you are with unlocked bootloader, custom kernel directly loaded AND without reflashing any rom, means you have kept your current installation
a.have you tried checking the S1Tool to see if you can unlock ive seen people saying its just not an option.
b. what are you choosing to flash ? i actually selected kernel straight away on the downgrade part
maybe use the s1tool and post that so people can respond to that
No. It says I only have to flash the X10_V1_BLRelock.ftf, if I'm going to a custom ROM afterwards.
Have I misunderstood?
i guess its me misunderstanding
could you like me the thread where you got the file from or your guide
if your unlocking your bootloader i find it odd that the file says BL''RELOCK''
anyways this is the guide i followed and worked like a charm.
http://forum.xda-developers.com/showthread.php?t=1254087&highlight=blrelock
the first post has the guide and my files were called the following
qsd8250 (zip file wich held the qsd8250_semc.bat)
wich allowed me to unlock the bootloader (this file had nothing to do with flashtool)
only used flastool for 2 things.
1) downgrade kernel
2) after qsd8250 was done unlocking bootloader to upgrade kernel to doomkernels V6 for UL bootloaders (was my choice of kernel)
That was the guide I used too.
"If you aren't keeping your current device configuration (because of flashing another rom after unlocking bootloader or anything else) the simplest way to unlock is to flash stock 2.3.3 rom, root it and use the bl unlock plugin from latest flashtool"
So i took the flash thing named bl_something..
---
As it seems that was wrong, can you give me a quick tutorial, as I didn't quit understand your way. and this one mention and easy way to do it if you'r going to change ROM at once.
tutorial read beyond the big text http://forum.xda-developers.com/showthread.php?t=1254087
basicly it says this.
1) get the files you need
semc bat is for x10i and x10a. But only if you haven't tried any simunlocking
the bl unlock file from this thread: http://forum.xda-developers.com/show....php?t=1253277 - thanks to the_laser
Kernel up/downgrade for flashtool from here: - thanks to azuzu im using FlashTool_0.2.9.1-GBready_root_xRec
and a custom kernel for Unlocked bootloaders (since your unlocking it )
i used doomkernels v6 for UL BL
Wifi modules for kernel if needed mine had it built in
and then the guide tells you to do this
Please make sure you have enabled usb-debugging in your current rom before starting with this!!
•flash the azuzu kernel downgrade ftf with flashtool
(i opened flashtool selected flash and then selected 'kernel downgrade' and in the other tab i skipped the 'loader' and selected 'kernel')
•disconnect usb cable, press power button until phone vibrates shortly and immidiatly connect the usb cable again (it is supposed to be stuck at SE logo)
(it asks you to do this and so i did)
1) turn off phone
2)unplug phone
3)hold back button
4)stil while holding back button plug phone in
5) flashtool takes over and you can let go
•start the batch file for unlocking bootloader, cause it says press any button before it starts, it won't start unlocking until you press any button
(when its done open the qsd8250 file wich you unzip(ped) and start the qsd8250_semc.cmd)
•now wait until flashtool recognizes your x10 (if flashtool doesn't do anything, check third post please! thx)
•close flashtool and then press any button in the cmd window that the unlocking process starts (please close flashtool, instead the bl unlock cmd and flashtool are constantly killing and restarting adb!!)
•after unlocking is finished you have to flash azuzu kernel upgrade
(same deal as the downgrade)
•now power on phone to check if the phone is starting after the unlock (if you are using a custom kernel yet with the bypass method and get stuck in a bootloop enter xrecovery and clear dalvik-cache, then your phone should boot up again fine)
•power off phone and flash the kernel you downloaded with flashtool
(the one you picked as said i used doomkernels v6 for UL BL)
•now flash the wifi modules if its needed with xrecovery. NOT FLASHTOOL!!!!
•power on phone again and if everything is right, read the line under that one
If you aren't seeing the se logo at turning on phone, but directly the custom kernel logo, you were succesfully. If you want to enter xrecovery you have to spam the back button now if the xperia logo appears instead of the se logo.
and thats it
all thnx should go to 9Lukas5 since i just copy / pasted evrything that he wrote
It's stuck here at the upgrade...
04/010/2012 20:10:39 - INFO - <- This level is successfully initialized
04/010/2012 20:10:39 - INFO - Flashtool Version 0.8.4.0 built on 2012-06-02 11:54:12
04/010/2012 20:10:39 - INFO - You can drag and drop ftf files here to start flashing them
04/010/2012 20:10:45 - INFO - Device connected in flash mode
04/010/2012 20:10:47 - INFO - Selected X10_aZuZu_Kernel_UpGrade_Generic.ftf
04/010/2012 20:10:47 - INFO - Preparing files for flashing
04/010/2012 20:10:47 - INFO - Please connect your device into flashmode.
04/010/2012 20:10:47 - INFO - Opening device for R/W
04/010/2012 20:10:47 - INFO - Reading device information
And when are the bat file finished, it didn't give a clear message, so after a while i exited it.
the bat file auto exits when completed cant remember but it asks you to press any key again and when you do it auto closes
make sure thats done and make sure you do this while flashtool is closed
so close flashtool before pressing any key in de bat file
and i dont see an error in the flash tool info you posted ? how is it stuck ?
i dont know if it matters but i actually upgraded straight away to the kernel i wanted to use
so instead of doing the kernel upgrade delivered with flashtool i upgraded to doomkernels v6 ULBL
seems like your almost there
The upgrade didn't continue..
I'll try your method instead, as for the bat tool.. it's "stuck" at the *daemon started successfully*
ah yeah ok
its bat file first while flashtools turned of
then when it auto closed turn flashtool back on and upgrade
I don't think you understood my explanation
First I downgraded
then I started the bat
then I closed the flashtool
then I pressed "any key" in the bat
then it got stuck on *daemon started successfully*, and it still get stucks there.
xVenator said:
I don't think you understood my exploitation
First I downgraded
then I started the bat
then I closed the flashtool
then I pressed "any key" in the bat
then it got stuck on *daemon started successfully*, and it still get stucks there.
Click to expand...
Click to collapse
I think u may be missing adb drivers on ur pc
Sent from my Xperia X10 using XDA
I think you might be right.
First, after a while just having the bat file opened this pops up: "error: protocol fault (no status)". Whatever that means, and it get stuck at the deamon thing again.
however when I start flashtool while having the bat file open it starts killing the apb server because it is out of date.
now.. what is adb server and how do I update/Install it?
Also, when I get this apb server thing installed ( can anyone link? ), can I use FXP 123 to upgrade with?
edit:
I used another computer, as I was away from my main computer. I got no problem with the adb server there, other than windows defender, but I manage to allow it
now, back to the question above: Can I install FXP 123 as custom kernal? instead of upgrade?
Thats what i did but with doomkernels v6 and no pro lems here ... maybe just to be safe flash the upgrade first then your fx123 its how the guide told us to do it
Sent from my X10 using xda premium
and so I did
Then I installed CM7 FXP123 .... stuck at CM7 loading logo
any idea what happend?
---
btw, thank you so much for the help so far! I really appreciate it and ofc used the thanks button! ^^
Redo de wipes ... enter recovery if you can? Its the rom loadin not kernel is it?
Then full wipe
Wipe cache partition
And wipe dalvik cache or whatever its called
In xrecovery its in adv option i believe
Ive googled some more and dalviks cache alone might even be sufficient
Sent from my CM7 Zmod / doomkernels v6 UL BL X10!
(And all that without bricking it) so far atleast.
xVenator said:
I think you might be right.
First, after a while just having the bat file opened this pops up: "error: protocol fault (no status)". Whatever that means, and it get stuck at the deamon thing again.
however when I start flashtool while having the bat file open it starts killing the apb server because it is out of date.
now.. what is adb server and how do I update/Install it?
Click to expand...
Click to collapse
To fully run adb u need to download java runtime environment and android SDK. The reason I think its adb is because it stops after saying starting daemon. This I think is adb starting
Sent from my Xperia X10 using XDA
Got everything working now.. except, I don't have a market app
As I said I just used another computer and the bat file worked, and after wiping all data as Bjornlindekens suggested I got it running.
Thanks all!
this is what i found so far.
(Amaurilol)
''Try finding an apk file for the market. Uninstall the one of your phone and install the downloaded one.''
http://www.filecrop.com/google-market.apk.html
flash google apps.zip if there is one ?(for your rom)
can you locate the market app in your settings/applications ?
only found 1 simular problem and doesnt say if its solved or not
and
(Ynkamat)
''Or else do a manual install of market app. We have a lots of them in apps section. Fix permissions. Use android commander from pc and install that app as a system app. But you need google account and its services to detect''
Hey!
Now my device is installed as Xperia Mini, when device is on, is this the right driver?
When not installed (before I press Install PC Companion software on this computer)
it shows up as Sony Ericsson sa0102 ADB Interface Driver, and I have the option to choose between similar named drivers, non of which works. This doesnt seem right?
What driver should the device use before PC-Companion installs the Xperia Mini driver?
In flashmode, the device is installed as Android ADB device. This seems right if you follow other tutorials/guides!
But I still cant flash/root nor unlock bootloader.
I know I need to downgrade the stock software version .62 to either .42 or .58 (The latter I couldnt find, so I will try .42 fw)
Bootloader unlock allowed: yes
USB debugging: ON
Unknown sources: ON
USB connection mode: MSC
Driver signature enforcement: OFF
Flashtool -> Throws error both on BLU and Flash, says my bootloader cant be officially unlocked
Doomlords v.4 -> Cant chmod/copy/install, but it seems it can push zergRush, if that means it "transferring" the app to the device
SE Bootloader_Unlocking_Relocking -> Throws exception when trying to flash, and hangs when I try to unlock the bootloader
SuperOneClick -> Shows half the process of zergRush then hangs, doesnt matter the method (zergRush, psnauter, GingerBreak)
fastboot.exe -i 0x0fce getvar version-> stuck at < waiting for device >
But "adb devices" shows the device! Is there a way to flash, root or unlock the bootloader with ADB?
This part might be the source of the whole mess!
Another problem im facing, probably highly crusial, when I try to upgrade the stock firmware neither PC-Companion nor SE update service can finish the upgrade!! It doesnt recognise my device when I being prompted to connect my phone in flashmode. I'm stuck here...
This might be a problem someone has encontered, and might share som insight in!?
When solved, I'll edit this thread to be "for those who facing the same issues as I'm doing!" And explain the exact details how and which drivers to install, and when!
And if I dont solve it, I'll think I'm gonna give Sony Ericsson a call after I posted on there official forums!
Hi all
Let me expose my problem :
I got an unlocking key from sony ; when I use it with
Code:
fastboot oem unlock 0xDEVICESKEY
, the boot process loops : I can see the sony logo, then the Xperia logo, then a few colorwaves, which in turn stalls for a second or two, and then the device reboots.
I tried to flash the device with kernels adapted to SGP312. Flashing succeeds if I unlocked just before (if I want to re-flash I have to re-unlock), but the device then doesn't boot at all.
I could never access recovery, but I read this thread saying that's normal with stock kernel. Though I couldn't access it having flashed any other kernel.
Thus I'm locked into android.
Can anyone help ? I discussed this with Mamenyaka, he suggested I posted my issue here. I tried to find a similar case in the forums but couldn't figure anything close to this.
I finally found a solution to my problem : I unlocked the device using flashtool-0.9.11's gui procedure, instead of flashtool's fastboot. It succeeded and I can successfully flash anything I want on the device.
My first thread and my only device, please help.
My device was rooted 3 years ago downgrading to 23.0.A.2.93 then flashing a prerooted stock ROM.
Right now I was using 23.5.A.1.291 SLiMM 3.8 with SuperSU 2.82 and Xposed 89, but I think at some point I tried to update BusyBox and lost access to the recovery.
So my idea was to instal XZDualRecovery (2.8.26) then unlock bootloader and jump into some newer version of Resurrection Remix (my fav ROM) cause I felt I was quite behind and I don't really like any new device.
How I broke it:
I connected it to my computer (Win10), enabled USB debugging, clicked on the install.bat from XZDR and allowed debugging and root access, the script went as I thought it should, threw some "couldn't write" errors but I think the script figured out as I saw some mounting system partition and whatnot underneath, when it finished it tried to reboot and there I am, I cannot go past the Sony logo and it constantly reboots.
What I tried:
Using Xperia Companion's "Software repair", I shut the device down, I press volume - and connect USB, my computer finds a USB device but the software doesn't recognize it as my device, so it doesn't continue.
I also tried doing the same but this time with volume +, it recognizes my device but it says that is locked and to please unlock it (as in drawing the unlock pattern) but the screen is black and doesn't react.
Flashtool also cannot find the device.
My last attempt was to unlock the bootloader to see if that changed anything, fastboot doesn't do anything and shows < waiting for any device >.
The best of this all is that I didn't even have a backup of almost anything, as this process doesn't wipe anything I thought I was in the clear, the more you know...
Come on guys, I need some help, somewhere from where to start, either to recover my files or to revive my Z3.
ok hear me out, I'm a newbie, and I missed up, plz help
I was trying to root my device following this tutorial, I flashed twrp and vbmeta and every thing went alright without errors, I booted the phone into recovery to continue as how the tutorial said, but it gave me the orange state error and it restarted into system but now the device is factory reset, I enabled usb debugging and went on to follow this tutorial, every thing went same as before and I couldn't boot into recovery, so I decided to flash the "orange_state_disabler_MTK Only.zip" with adb and every thing went downhill from there, It won't boot to recovery, bootloader nor system, It just stays at a blank screen after the logo and the orange state message, It is recognized by adb as "recovery" and I can do adb commands but I can't boot to bootloader to flash the stock firmware, I found this thread and tried using the tool mentioned there, Faced an error, solved it and the phone still won't boot to any thing.
so, is there any way I can get out of this situation ?
TLDR / what you should know/ idk ¯\_(ツ)_/¯
- did something wasn't supposed to do
- can't boot to recovery
- can't boot to bootloader
- device recognized by adb but can't do fastboot commands
- device is recognized by MTKAuthBypassToolV25
- can't shutdown nor restart using phone physical buttons
- don't know if the below screenshots would help with any thing, but here goes nothing
You have misunderstanding, Orange State does not cause anything. That is just notification that bootloader is unlocked, nothing more. Therefore the Orange State Disabler cannot fix anything. You don't need this at all.
But it seems it destroyed fastboot. flash lk from SP Flash Tool
aIecxs said:
You have misunderstanding, Orange State does not cause anything. That is just notification that bootloader is unlocked, nothing more. Therefore the Orange State Disabler cannot fix anything. You don't need this at all.
But it seems it destroyed fastboot. flash lk from SP Flash Tool
Click to expand...
Click to collapse
please explain, I don't know what IK is, and if I could flash things with SP flash tools, wouldn't I be able to flash stock firmware?
lk - little kernel. that is the partition where fastboot lives (and was modified by Orange State Disabler).
you need partition image from stock ROM and any flash tool to restore its original state.
i can't do that because i can't boot to bootloader
you don't need bootloader, only preloader or bootrom
ok turns out ima an idiot and misunderstood the entire situation , this is my first dealing with an mtk device so i thought sp flash tool is like odin and you need to be in download mode to flash things so i panicked, and didn't read well how to use the tool.
flashed stock firmware and the phone is up and running again
thanks for your help man really appreciate it and sorry for wasting your time