Hello there!
I've been trying to install a custom rom to my sk17i running 4.1.B.0.587, I'm also using Windows 8 64 bit.
I first follow this http://forum.xda-developers.com/showthread.php?p=31376248#post31376248 initially as it seems that it's a complete guide. But in that thread, I was unable to unlock the bootloader as the command is not letting me run the fastboot.exe -i 0x0fce getvar version / fastboot device etc.
So I end up trying this thread http://www.androidgadgematic.com/2012/11/how-to-unlock-any-sony-xperia-bootloader-easily.html
Which I able to run those commands ( fastboot.exe.... etc ) but when I run this command to unlock the bootloader ( fastboot.exe -i 0x0fce oem unlock.. ) I got an error " failed remote oem unlock " so I double checked the IMEI and got new bootloader key. Then I tried again, I got an error this time " too many links ". As per other thread, they advised to clear cache ( fastboot clear cache ) but it doesn't made any difference.
After too many trials, I decided to use this http://forum.xda-developers.com/showthread.php?t=1879982 (using flashtool and flashmode) I was able to get 14% when the LED light on my xperia gone. Then what I did was I reconnected the cable then proceeded with flashtool method.
At this point, when I rerun flashtool, it's stock at 2% with checking headlines. Goes about more than 10mins on that phase so I decided to reconnect it. Then my computer crashed, so I have to restart. When I turned my computer on, It loaded for 5 mins then I got a pop up message, "upgrading android" afterwards, other programs loaded but then at the end, I got another error saying " Unfortunately, startup programs stopped..." then it restarts itself continuously that I have to remove the battery to completely turn it off.
I assumed that my phone is now "bricked" that is why i follow this "6. Turning the "brick" into a smartphone" http://forum.xda-developers.com/showthread.php?p=27376017 but it didn't worked. same as the last time I used the flashtools.
Can I still revive my phone? I just want to downgrade it back to GB 2.3 or upgrade it to CM10 JB if possible.
I'm definitely stupid and noob in this field. Can someone help me out for this one? It'll be highly appreciated! Many thanks!
*Drivers are successfully installed.
*downloaded kernels.
*Windows 8 64 bit
I'm on the point of losing hope that I could still use it. =((((
Give this a read - http://www.androidgadgematic.com/2012/06/how-to-fix-bricked-sony-xperia-android.html
Many thanks! I'll give it a try. hope it works. =)):fingers-crossed:
**by the way, I can't see the xperia mini pro component when I try to install the flashtool driver. what component shall I choose?Please advise.Thanks!
Cant find any threads about this. So confusing.
nejakkin said:
Cant find any threads about this.
Click to expand...
Click to collapse
See the general section, everything has been covered before so finding it should be easy.
Related
A friend of mine gave me his x10i phone to play, so i decided to follow all the proper steps to get the device rooted and install 2.3.4 on it.
I have downloaded the flashtool v 0.5.3.0, but it does not detect the device. I have also installed the drivers on the system from flashtool\drivers folder
When I click Check Drivers, i get the following output:
12/041/2011 16:41:47 - INFO - List of connected devices (Device Id) :
12/041/2011 16:41:47 - INFO - - USB\VID_0FCE&PID_612E\CB511ND245: OK
12/041/2011 16:41:47 - INFO - List of ADB devices :
12/041/2011 16:41:47 - INFO - List of fastboot devices :
Another problem I have is that Debug mode is on, but the flashtool always says it is off. I tried all i could including upgrading the stock rom from sonyericsson site, but at this stage, I am ready to give up. I do not see anyone else is experiencing this problem.
Any advice is appreciated.
screw the drivers in that folder
install the legit ones from the SE webstie
install the PC Companion and it will do everything for you
then try. If does not work message me or reply here
tried it all from scratch at home on windows 7 (first attempt was at work on XP).
At home everything worked fine Thanks!
do you want Unlocking you bootloader?
try my way, its stands in my signature.
I think i was able to unlock it. In fact, sorry, I do not know what "unlocking bootloader" is, but what makes me think that I've done it is that i was able to flash Doom kernel with wifi and one of the custom ROMs on it. Also I got root access on the phone. Recovery console (CWM ?) is working too.
Correct me if i am wrong, but this is as far as i can go with this device and nothing else needed to crack/install etc.
One issue i noticed is that GPS does not work and settings are just not there, but i guess it is a ROM/kernel related question which i will explore further.
unlock bootloader
makes it a lot easier and nicer when you install a custom rom
um
use flashtool
under plugins category
Hello all!
I'm trying to root my HTC Legend using Chirag's manual.
I somehow managed to complete all steps until step 4 (that is, flashing the rooted rom), but now i'm stuck.
I but the phone in fastboot mode, plug it to my computer, and the phone says "fastboot USB". When i run 'step1-windows.bat', nothing happens, i get the message:
"Legend Root Step 1
Erasing cache and rebooting in RUU mode...
<waiting for device>"
And that is all. Any ideas? It would be pretty lousy to go through all those steps, including downloading and losing all apps not to be able to finish the very last step...
--edit--
I do have superuser "app" in the drawer of my legend. Don't know if it's important...
Ok, so my PC doesn't see the legend when in FASTBOOT mode, "adb devices" returns an empty list. When the phone is on, and normal, i see it with adb services.
Okay, made it past step one. I turned off HTCSync, and the PdaNet, which i installed earlier (i was that desperate). Nothing seemed to work. I then entered FASTBOOT mode, plugged it into the PC, and then in control panel went to 'devices', found 'Android 1.0 devices' and installed the drivers automatically. The moment i did that, step one started to work, and finished in about couple of minutes.
Just in case someone else gets this problem, this is the solution.
Now starting step 2, i hope it will succeed.
--edit--
Yesss!!! It worked like a charm, i now (finally) have rooted 2.1 with sense
Sorry for talking to myself, but i wanted to share the solution, i usually get pissed when someone solves his problems and doesn't share
Nah Your all right with me, its good to see you managed to get it fixed on your own. I think all the guides need to be updated with that information regarding the need for android 1.0 drivers as it seams to be THE most common issue when not being able to get through the rooting steps.
Enjoy and have fun!
Sent from my HTC Legend using XDA App
Guys, hi.
I'm beat, I admit it, the jig is up and I'm all out. I've done every possible thing to my phone and nothing helps.
I want to flash CWM7, right? I have the stock 2.1 and working root (that I know for sure). I also have Flashtool and Android SDK on my computer.
What I DON'T have, however, is a way to get into recovery and from there flash ROMs. CWM Recovery doesn't exist for my phone (Xperia X10 Mini Pro), so I got this thing (http://forum.xda-developers.com/showthread.php?t=1106146), copied the chargemon and recovery.tar into my system folder, set the permissions to all enabled, turned off my phone, turned it back on and spammed the back key -> nothing. On another try I long-pressed the back-key -> nothing. On another I installed Rom Manager and selected Boot into Recovery. The phone just restarted.
I THINK, but I'm not sure, that to use recovery, I have to have my bootloader unlocked, is that correct? For that I used this guide (http://forum.xda-developers.com/showthread.php?t=1254225) which I must say is extremely confusing - essentially, what I did was that I got msm7227_semc.cmd from here (http://forum.xda-developers.com/showpost.php?p=17384177&postcount=3) and run that -that seemed to work fine and returned no errors, on my pc.
I can't ascertain whether I ACTUALLY have bootloader unlocked, because that (from what I read in the guide) requires Gordon's Gate and S1tool - S1tool alone doesn't work for me (does nothing) and my Flashtool installation doesn't have Gordon's Gate in it.
So, I don't even know anymore. What the heck am I doing wrong, how can I boot into recovery? It used to be so easy when I had the HTC Desire
Thanks, all. It would be really appreciated if you could give me any help, because I spent hours on this and have had no success despite following all the neat guides and stuff
Angelic out
When i was in Stock Android, I had taken xRecovery to flash my first ROM (MiniCm7pro V21)
After the ROM was flashed I had CWM already preinstalled
Hopefully this (http://forum.xda-developers.com/showthread.php?t=950324) may help you
liveangelic said:
Guys, hi.
I'm beat, I admit it, the jig is up and I'm all out. I've done every possible thing to my phone and nothing helps.
I want to flash CWM7, right? I have the stock 2.1 and working root (that I know for sure). I also have Flashtool and Android SDK on my computer.
What I DON'T have, however, is a way to get into recovery and from there flash ROMs. CWM Recovery doesn't exist for my phone (Xperia X10 Mini Pro), so I got this thing (http://forum.xda-developers.com/showthread.php?t=1106146), copied the chargemon and recovery.tar into my system folder, set the permissions to all enabled, turned off my phone, turned it back on and spammed the back key -> nothing. On another try I long-pressed the back-key -> nothing. On another I installed Rom Manager and selected Boot into Recovery. The phone just restarted.
I THINK, but I'm not sure, that to use recovery, I have to have my bootloader unlocked, is that correct? For that I used this guide (http://forum.xda-developers.com/showthread.php?t=1254225) which I must say is extremely confusing - essentially, what I did was that I got msm7227_semc.cmd from here (http://forum.xda-developers.com/showpost.php?p=17384177&postcount=3) and run that -that seemed to work fine and returned no errors, on my pc.
I can't ascertain whether I ACTUALLY have bootloader unlocked, because that (from what I read in the guide) requires Gordon's Gate and S1tool - S1tool alone doesn't work for me (does nothing) and my Flashtool installation doesn't have Gordon's Gate in it.
So, I don't even know anymore. What the heck am I doing wrong, how can I boot into recovery? It used to be so easy when I had the HTC Desire
Thanks, all. It would be really appreciated if you could give me any help, because I spent hours on this and have had no success despite following all the neat guides and stuff
Angelic out
Click to expand...
Click to collapse
hey angelic have you tried superoneclick? its a rooting software with a builtin recovery intaller
Hi, i'm starting this thread by excusing myself for this approximativly english, i'm not really an english man :angel:
I don't really like calling help on forum, but at 00:30, with studies tomorrow, i'm really bored.
So, today at 17:30, i have reboot my OPX, simply reboot, and i'm now on a bootloop... I read a looooooot of thing on internet and i deduce that : My bootloader has relocked himself.
Before this reboot, i was on OxygenOS 3.* with TWRPblu****** and an unlocked bootloader. I can't access to recovery, only to a bootloop or fastboot mode.
I've tried :
- Use fastboot commands to flash recoveries, but nothing happen because i can't unlock the bootloader
- Use the MSMdowloadtool like all guide said, but the problem is there i think. My device aren't recognize as a "Qualcomm ***********" is recognize as "Android" or "One plus bootloader device" (i haven't exact name here). I thinked Windows 10 have the faculty to identify android devices, so i've installed on dual boot windows 7, no more results. (Signed Drivers are disabled)
I have no idea, i need u :crying:
If anyone have ever see the same issue, give me ur solution please
I certainly will contact the OnePlusSupport too but i know it's not really a good idea.
I will go to sleep now, i need to go to school tomor... today.
Have a good night !
Nekkoelb said:
Hi, i'm starting this thread by excusing myself for this approximativly english, i'm not really an english man :angel:
I don't really like calling help on forum, but at 00:30, with studies tomorrow, i'm really bored.
So, today at 17:30, i have reboot my OPX, simply reboot, and i'm now on a bootloop... I read a looooooot of thing on internet and i deduce that : My bootloader has relocked himself.
Before this reboot, i was on OxygenOS 3.* with TWRPblu****** and an unlocked bootloader. I can't access to recovery, only to a bootloop or fastboot mode.
I've tried :
- Use fastboot commands to flash recoveries, but nothing happen because i can't unlock the bootloader
- Use the MSMdowloadtool like all guide said, but the problem is there i think. My device aren't recognize as a "Qualcomm ***********" is recognize as "Android" or "One plus bootloader device" (i haven't exact name here). I thinked Windows 10 have the faculty to identify android devices, so i've installed on dual boot windows 7, no more results. (Signed Drivers are disabled)
I have no idea, i need u :crying:
If anyone have ever see the same issue, give me ur solution please
I certainly will contact the OnePlusSupport too but i know it's not really a good idea.
I will go to sleep now, i need to go to school tomor... today.
Have a good night !
Click to expand...
Click to collapse
Fastboot commands : is the phone recognised?
"fastboot oem device-info" output?
Did you tried the Mega unbricked guide?
Which step precisely is a problem?
Kéno40 said:
Fastboot commands : is the phone recognised?
"fastboot oem device-info" output?
Did you tried the Mega unbricked guide?
Which step precisely is a problem?
Click to expand...
Click to collapse
Yes he used..read full op.
Nekkoelb said:
Hi, i'm starting this thread by excusing myself for this approximativly english, i'm not really an english man :angel:
I don't really like calling help on forum, but at 00:30, with studies tomorrow, i'm really bored.
So, today at 17:30, i have reboot my OPX, simply reboot, and i'm now on a bootloop... I read a looooooot of thing on internet and i deduce that : My bootloader has relocked himself.
Before this reboot, i was on OxygenOS 3.* with TWRPblu****** and an unlocked bootloader. I can't access to recovery, only to a bootloop or fastboot mode.
I've tried :
- Use fastboot commands to flash recoveries, but nothing happen because i can't unlock the bootloader
- Use the MSMdowloadtool like all guide said, but the problem is there i think. My device aren't recognize as a "Qualcomm ***********" is recognize as "Android" or "One plus bootloader device" (i haven't exact name here). I thinked Windows 10 have the faculty to identify android devices, so i've installed on dual boot windows 7, no more results. (Signed Drivers are disabled)
I have no idea, i need u :crying:
If anyone have ever see the same issue, give me ur solution please
I certainly will contact the OnePlusSupport too but i know it's not really a good idea.
I will go to sleep now, i need to go to school tomor... today.
Have a good night !
Click to expand...
Click to collapse
Power off your phone, connect to PC with power off holding volume up button. It should detect phone as Qualcomm.
Nekkoelb said:
Hi, i'm starting this thread by excusing myself for this approximativly english, i'm not really an english man :angel:
I don't really like calling help on forum, but at 00:30, with studies tomorrow, i'm really bored.
So, today at 17:30, i have reboot my OPX, simply reboot, and i'm now on a bootloop... I read a looooooot of thing on internet and i deduce that : My bootloader has relocked himself.
Before this reboot, i was on OxygenOS 3.* with TWRPblu****** and an unlocked bootloader. I can't access to recovery, only to a bootloop or fastboot mode.
I've tried :
- Use fastboot commands to flash recoveries, but nothing happen because i can't unlock the bootloader
- Use the MSMdowloadtool like all guide said, but the problem is there i think. My device aren't recognize as a "Qualcomm ***********" is recognize as "Android" or "One plus bootloader device" (i haven't exact name here). I thinked Windows 10 have the faculty to identify android devices, so i've installed on dual boot windows 7, no more results. (Signed Drivers are disabled)
I have no idea, i need u :crying:
If anyone have ever see the same issue, give me ur solution please
I certainly will contact the OnePlusSupport too but i know it's not really a good idea.
I will go to sleep now, i need to go to school tomor... today.
Have a good night !
Click to expand...
Click to collapse
You have noting to do but to flash stock oos 2.1.4 using Qualcomm flasher and driver.I faced the same issue.but I managed to flash using Qualcomm in windows 10.and got my onyx back.
My suggesting is remove the adv or oneplus drivers.just install the Qualcomm driver and connect the device.follow the device manager if the deivce detected or not.it will detect and flash using Qualcomm flasher.
Hey guys,
I've been trying to unlock my Nubia Z18 mini (NX611J) for a while now and its not happening.
None of the guides or info I can find is helpful here.
The thing is that I ordered the phone with google play.
So it already was unlocked at one point.
The thing now is that the bootloader is locked and wont unlock.
(Of course developer options are on with usb debugging and oem unlock activated)
With fastboot oem nubia_unlock NUBIA_NX611J it should work... And on ubuntu it at least starts to work...
So in ubuntu it does unlock and the devices even says its unlocked und adds 1 to its lock count....BUT THEN...
it just freezes on the pc side with the following:
...
(bootloader) START update nubia fastboot unlock flag!!!
...If i then just unplug/plugin the phone again and try to flash twrp, it acts as though it would still be locked.
And running this command the cursor blinks on pc. The device unlocks like mentioned above and then the cursor on the pc stops blinking and then that was it... Nothing more ever happens it just stops and freezes. And on the phone I can't acknowledge the unlock or anything. The bootloader menu on the phone still works, but if I choose any of the options there to reboot or anything its locked again after that.
On my Windows machine the Device either won't even be recognized by the system, depending on the drivers I use or it will give errors like: ...
FAILED (remote: password wrong)
finished. total time: 0.008s
Or it will also freeze.
The nubia emergency tool (v. 1.1.6) unfortunately does not support the phone yet.
The only thing I can think of trying now would be KingRoot, which I HATE. Cause that will install me Bloatware I might not be able to get rid of. And also I'm pretty sure I won't be able to use Magisk which is the main reason I'm doing this.
I also found and tried this one: https://forum.xda-developers.com/general/general/nubia-z18-mini-nx611j-root-recovery-t3835718
But thats just a script trying to use the same commands... So it just gets the same errors.
So if anyone can think of anything I can do here please help.
Thank you so much.
Found my problem
Bungee-Spider said:
Hey guys,
I've been trying to unlock my Nubia Z18 mini (NX611J) for a while now and its not happening.
None of the guides or info I can find is helpful here.
The thing is that I ordered the phone with google play.
So it already was unlocked at one point.
The thing now is that the bootloader is locked and wont unlock.
(Of course developer options are on with usb debugging and oem unlock activated)
With fastboot oem nubia_unlock NUBIA_NX611J it should work... And on ubuntu it at least starts to work...
So in ubuntu it does unlock and the devices even says its unlocked und adds 1 to its lock count....BUT THEN...
it just freezes on the pc side with the following:
...
(bootloader) START update nubia fastboot unlock flag!!!
...If i then just unplug/plugin the phone again and try to flash twrp, it acts as though it would still be locked.
And running this command the cursor blinks on pc. The device unlocks like mentioned above and then the cursor on the pc stops blinking and then that was it... Nothing more ever happens it just stops and freezes. And on the phone I can't acknowledge the unlock or anything. The bootloader menu on the phone still works, but if I choose any of the options there to reboot or anything its locked again after that.
On my Windows machine the Device either won't even be recognized by the system, depending on the drivers I use or it will give errors like: ...
FAILED (remote: password wrong)
finished. total time: 0.008s
Or it will also freeze.
The nubia emergency tool (v. 1.1.6) unfortunately does not support the phone yet.
The only thing I can think of trying now would be KingRoot, which I HATE. Cause that will install me Bloatware I might not be able to get rid of. And also I'm pretty sure I won't be able to use Magisk which is the main reason I'm doing this.
I also found and tried this one: https://forum.xda-developers.com/general/general/nubia-z18-mini-nx611j-root-recovery-t3835718
But thats just a script trying to use the same commands... So it just gets the same errors.
So if anyone can think of anything I can do here please help.
Thank you so much.
Click to expand...
Click to collapse
Ok so I found the Problem... I just had to uninstall all the drivers and then reinstall them (included in the download as autorun.exe) from scratch one more time (in windows) and then use the ./fastboot.exe from your download or this: https://www.androidbrick.com/download/nubia-z18-mini-nx611j-twrp-root/ and it finally worked
Thank you for this amazing link
Bungee-Spider said:
Ok so I found the Problem... I just had to uninstall all the drivers and then reinstall them (included in the download as autorun.exe) from scratch one more time (in windows) and then use the ./fastboot.exe from your download or this: "I cannot display the link" and it finally worked
Click to expand...
Click to collapse
I did not no what to do and had been busy for two days. Then I found this amazing link ). Thank you very much