I just purchased a G8343 on eBay and have attempted to unlock the bootloader, but the OEM unlock command seems to merely hang every time I run it.
By sheer luck, the bootloader ended up unlocked, but when I try to flash recovery, the command also hangs—this time without leaving the recovery actually flashed.
I can't restore with Xperia Companion as the bootloader is unlocked and Flashtool doesn't work to flash the device. Sony's official Emma also appears to not want to work with the device, stating "No available services for this model"—presumably because the G8343 is not listed on the officially supported devices for Sony's "Open Devices". I've even tried newflasher but that times out in fastboot as well.
What do?
To flash the recovery, make sure it is powered off and UNPLUGGED. Then plug in the phone while holding the Volume UP button. You should see a blue LED light.
Then check windows device manager and make sure to install the Android Bootloader drivers are installed. Then you can freely use "fastboot flash recovery twrp-xxxxx.img" easily.
You can not flash recoveries the same way you use Newflasher, since that uses the flashmode and not fastboot.
Related
Hey,
I'm currently trying to root my Sony Xperia Z2 but I can't get past the unlockbootloader stage.
I use the instructions given at Sony Developer World after entering my IMEI and all that, but one step don't work for me:
"3. On your Xperia™ Z2, press the Volume up button at the same time as you connect the other end of the USB-cable. For Windows users, when asked for a driver, point to the usb_driver folder where you placed the android_winusb.inf-file, and select the Android Boot loader Interface-file."
I connect the phone and it lights up blue as it should but computer is not asking me for any drivers. And seem I have to do this step as the next step is:
"4. When your device is connected, open a command window on your computer and go to the platform-tools folder within the Android SDK folder and type in ">fastboot devices" "
And if I type "fastboot devices" after the ">" nothing happens. If I try it with ">fastboot devices" the cmd.exe goes "The system cannot find message text for message number in the message file for Application."
Thanks for any help!
Andreas
I recomend using flashtool instead, also backup your TA partition because your warrent is voided by your bootloader being unlocked
Flashtool.net < it has a drivers.exe run in the drivers folder, run that first
I was never able to unlock my bootloader via sonys instructions across few devices, flashtool alwaus has worked for me
Thanks!
Gonna try it out but wondering if I should backup the TA Partition before or after the fastboot?
For example at this thread it states first step as "root" which feels more like the last step.
http://forum.xda-developers.com/xpe.../tutorial-backup-ta-partition-to-drm-t2234627
AndreasWY said:
Thanks!
Gonna try it out but wondering if I should backup the TA Partition before or after the fastboot?
For example at this thread it states first step as "root" which feels more like the last step.
http://forum.xda-developers.com/xpe.../tutorial-backup-ta-partition-to-drm-t2234627
Click to expand...
Click to collapse
Before!
Unlocking the bootloader deletes your DRM keys so backing up your TA after you have unlocked the bootloader would be pointless.
The order you need to do things is...
Root (this allows you to backup your TA)
Backup your TA
Unlock your bootloader
Flash a flash a custom recovery
Flash ROMs to your heart's content
If you want to go back to stock (including restoring your DRM keys)...
Flash a stock FTF using flashtool
Lock the bootloader
Root
Restore your backed up TA
Flash the same FTF using flashtool (to remove root)
Hey!
I have the same problem here, nothing happens when i write fastboot devices while trying to unlock my device (but adb is working, in fact, i got into bootloader mode using adb).
I tried also using flashtool, but it says my device isn't able to be unlocked (but checking it in my z2 following Sony 's website steps it says: UNLOCK BOOTLOADER:YES).
Thanks!
Daniel30 said:
Hey!
I have the same problem here, nothing happens when i write fastboot devices while trying to unlock my device (but adb is working, in fact, i got into bootloader mode using adb).
I tried also using flashtool, but it says my device isn't able to be unlocked (but checking it in my z2 following Sony 's website steps it says: UNLOCK BOOTLOADER:YES).
Thanks!
Click to expand...
Click to collapse
If you aren't getting device ID on fastboot devices then either your device isn't in fastboot mode or your pc isn't detecting it, check that you have the correct drivers installed, flashtool can do it for you, and try again.
ghostofcain said:
If you aren't getting device ID on fastboot devices then either your device isn't in fastboot mode or your pc isn't detecting it, check that you have the correct drivers installed, flashtool can do it for you, and try again.
Click to expand...
Click to collapse
Thanks for helping!
That was the first i though, but if i can use adb, drivers should be okay, or at least that's what it should be.
And about not being in fastboot mode, i got into it through adb, and my notification led was blue, as it should be when the device is in fastboot mode.
Thanks again!
If I'm not mistaken fastboot and adb drivers are different, at least they are on htc devices. If fastboot devices returns no results it's because the pc can't communicate with any fastboot devices connected to it, end of.
i couldn't get twrp to work on my xperia zr so i tried this open cmd put the phone in recovery mode i think (blue led) then "fastboot flash boot TWRP+RAINBOW2.8.2A.img" then "fastboot reboot" the phone is dead just a red led and a small vibration when powered up but nothing light up any help ?
edit : i boot it again the Q now is there any way to install this recovery TWRP
Depends on if your bootloader is unlocked. I don't know about the ZR specifically, but the majority of newer Sony devices need either bootloader unlocked or to use a special kernel+recovery combo that must be installed through the flash tool for devices with locked bootloaders.
I ported TWRP using Android kitchen to flash to my device (Coolpad 801es) since there isn't an official version. For some reason, I can't seem to get fastboot to play nice with my phone (see my earlier post) so I used flashify. On reboot i'm stuck in a bootloop. I did have the foresight to back up my stock recovery with flashify and transfer it to my PC first, in case something went wrong. Now, I can't boot into recovery at all and ADB isn't working since the phone isn't being recognized by my PC when I plug it in. I just want to flash the stock recovery back and fix this. I can get into fastboot, and the PC does recognize the phone in fastboot, but when I try any commands it just hangs at waiting for device. I've googled but every solution i've seen for fixing a bootloop tells you to boot into recovery to do so.
Can someone please help me out?
UPDATE:
Upon further research, I discovered the reason fastboot commands weren't working is because my phone apparently isn't whitelisted in the fastboot exe. However, if I type Fastboot followed by -i 0x1ebf the commands seem to work. Using this method, fastboot devices lists my phone and fastboot reboot reboots the phone.
I think i'm on the right track, but when I try "Fastboot -i 0x1ebf flash recovery (path to recovery.img)" the terminal shows "sending 'recovery' (10240kb)..." and nothing else. No progress indicator, and i've waited 10 minutes for it to complete which should be more than enough time to flash a 10 meg file, but there's no change it just sits there. Like I said, I think i'm on the right track but I could REALLY use some help. I can't be the first person on here with this problem. Can someone, anyone, PLEASE help me.
So, more Googling would indicate that either i'm not using the correct USB port, or that my bootloader is locked. I have tried all the USB ports on my PC (front and back) as well as two different cables, no joy. As far as the bootloader being locked, the phone is rooted which I thought meant that the bootloader is unlocked as that is part of the rooting process. I try "Fastboot oem unlock" to check but I just get "failed remote no such command unlock" and there is no OEM option under developer options on this phone. I'm trying to piece this together but I could really use some help.
My Z5 compact was updated to Nougat using the OTA service.
The bluetooth integration to my car stopped working and I read that this was a noted problem I decided to flash my phone back to Marshmallow.
I'd installed custom ROMs on previous HTC phones following info from XDA so was pretty confident.
After following the Sony guidelines and obtaining my unlock key I am unable to get it to work in fastboot mode.
I suspect that it is a USB problem at one end or another.
If I connect up the phone to the PC using the original lead I can find it using adb devices and the device is showing up as error free "Sony sa0113 ADB Interface Driver" in Windows 10 device manager.
However the phone isn't charging and I can't get it into Fastboot by holding the up vol key and plugging in the USB lead.
I can get a black screen with the blue led by running adb reboot bootloader and the phone is recognised from fastboot devices but when I try to unlock the bootloader I get an error:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0fce oem unlock 0xB4D9AxxxxC359F2C
...
FAILED (remote: Command did not succeed)
finished. total time: 0.042s
Any help appreciated.
PhilG57 said:
My Z5 compact was updated to Nougat using the OTA service.
The bluetooth integration to my car stopped working and I read that this was a noted problem I decided to flash my phone back to Marshmallow.
I'd installed custom ROMs on previous HTC phones following info from XDA so was pretty confident.
After following the Sony guidelines and obtaining my unlock key I am unable to get it to work in fastboot mode.
I suspect that it is a USB problem at one end or another.
If I connect up the phone to the PC using the original lead I can find it using adb devices and the device is showing up as error free "Sony sa0113 ADB Interface Driver" in Windows 10 device manager.
However the phone isn't charging and I can't get it into Fastboot by holding the up vol key and plugging in the USB lead or by running adb reboot fastboot
If feels like I haven't go the fastboot USB drivers but I can't see how or where I can add them.
Any help appreciated.
Click to expand...
Click to collapse
Disable driver signature enforcement then reinstall sony drivers
tapiwasam said:
Disable driver signature enforcement then reinstall sony drivers
Click to expand...
Click to collapse
Thanks. I think I am OK there because I accepted the drivers from an unverified source during installation.
Also I can see the phone with both adb devices and fastboot devices
However when I run adb reboot bootloader the phone reboots but comes up with a blank screen with the blue led.
adb reboot bootloader just goes into bootloader mode and not fastboot mode which is needed to unlock it. Go directly into fastboot by typing adb reboot fastboot
Then when your phone led is flashing blue, run your fastboot "oem unlock" command.
Saw now that you already tried that sorry about that.
Tried running cmd with admin privileges to see if that shows any difference?
Also from sony:
Please note! It will only be possible to unlock the boot loader for certain releases. You can check if it is possible to unlock the boot loader of your device in the service menu by following the steps below:
In your device, open the dialler and enter *#*#7378423#*#* to access the service menu.
Tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.
Click to expand...
Click to collapse
PhilG57 said:
My Z5 compact was updated to Nougat using the OTA service.
The bluetooth integration to my car stopped working and I read that this was a noted problem I decided to flash my phone back to Marshmallow.
I'd installed custom ROMs on previous HTC phones following info from XDA so was pretty confident.
After following the Sony guidelines and obtaining my unlock key I am unable to get it to work in fastboot mode.
.... snip....
Click to expand...
Click to collapse
You don't need to unlock your bootloader to simply downgrade to official MM! Just use flashtool to flash the appropriate MM ftf. There are plenty guides available on XDA and elsewhere.
I'm lost in your explanation.
You wanted to unlock your bootloader to be able to downgrade your phone? That's right? And it's fine to me, but you don't need to do that if you don't feel like. Unlocking your bootloader is nog necessary to downgrade to MM via flashtool.
So you tried to unlock your bootloader. But what you write what happened afterwards is completely unclear to me, because it contradicts itself.
-->> "Also I can see the phone with both adb devices and fastboot devices"
Fine. This means your connected with your phone and fastbook recognizes your phone. So bootloader is unlocked and software to control that works fine.
-->> "However when I run adb reboot bootloader the phone reboots but comes up with a blank screen with the blue led."
Fine, so you unlocked your bootloader, and rebooted in fastboot.
-->> Obviously. It's an unlocked bootloader, you can double unlock it or something like that. You can relock it if you want (which doesn't make any difference for what you want to do) but that's a different method.
Is there any reason that you absolutely need to a second method to enter fastboot mode? Or any fastboot mode? It could be possible with another kernel, but I don't see the point to flash another kernel. I would just leave it like it is.
PhilG57 said:
Thanks. I think I am OK there because I accepted the drivers from an unverified source during installation.
Also I can see the phone with both adb devices and fastboot devices
However when I run adb reboot bootloader the phone reboots but comes up with a blank screen with the blue led.
Click to expand...
Click to collapse
that is notmal behaviour, that is fastboot mode, indicated by that blue LED
Thanks for the clarification that I don't need to unlock the bootloader to downgrade using flashtool. What I didn't say was that I couldn't reinstall Nougat using the Sony tool software restore option or get anywhere with flashtool because the phone won't go into the blue led mode by inserting the USB and holding the up vol button. I did try running flashtool in one window and the command line tools in another with the idea of running flashtool first and then unplugging the phone and replugging it to use command line to get the blue LED state, but that doesn't work because the command line tools can't see the phone once flashtool is running and has addressed the phone.
From what i read, i assume you are on nougat and want to go back to MM, right?
So you would need flashmode instead of fastboot mode.
You get there with holding Vol down button and plugging in USB cable on turned off phone.
Flashmode also shows a green notification light instead of the blue one.
If you having Problems to get there, please check following:
make sure to have latest version of flashtool installed http://www.flashtool.net/downloads.php
install drivers from your flashtool\drivers folder
don't use an USB 3.0 port or cable(have heard of some people having trouble with)
PhilG57 said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0fce oem unlock 0xB4D9AxxxxC359F2C
...
FAILED (remote: Command did not succeed) <- this
finished. total time: 0.042s
Any help appreciated.
Click to expand...
Click to collapse
OP, I had the exact same problem as you. At the time I tried absolutely everything but never found the culprit. So after several months I actually succeeded today
This is the guide I followed - https://forum.xda-developers.com/z5-compact/general/guide-how-to-root-z5c-painful-using-t3549388 and it worked perfectly.
A few pointers:
- Go to the service menu (*#*#SERVICE#*#*) before you begin, before you turn OEM Unlocking ON from Dev Options .
- Take note of what it says in Configuration and Firmware.
- Now enable OEM Unlocking and take note again, it should say stuff like Model Number: Unknown and other unknown stuff.
- Reboot - IMPORTANT.
- Use the guide I gave you and you will be fine, it took me ages to find a solution but now I'm on MM and rooted
Hope I helped :fingers-crossed::fingers-crossed::fingers-crossed:
Hi to all,
I have a question about my device.
I hope that I have posted this correctly; if not please accept my apologies.
I have a Letv Le 2 Pro X620. This has the MTK CPU (not snapdragon).
The phone had the stock ROM on it with EUI and it got the updates.
In the last update about a month ago, Google Service stopped working; and I therefore wanted to flash a different ROM on to fix that; as well as to finally get rid of the chinese apps which annoyed me.
SO I downloaded a ROM from XDA https://forum.xda-developers.com/le-2/development/rom-lligera-t3538654 (thanks).
The device was unrooted and had the stock recovery.
I used the basic adb and fastboot command prompt applications. I already enabled developer mode in the phone and had also enabled debugging and unlocking boot loader.
In the adb/fastboot I entered the command to unlock "fastboot oem unlock" and "fastboot oem unlock go". IT would confirm and complete and then I went onto flash the recovery.
HERE IS WHERE THINGS DIDNT GO AS EXPECTED.
And I ended up doing this multiple times (i.e oem unlocking, and flashing recovery)
I tried using TWRP twrp-3.2.1-0-s2; and also downloaded a pack "Le2RootMegaPack" which had Letv-X620-Twrp-3.0.2-0 .
IT would complete successfully; but on reboot I would get an error message like "Orange State. Your phone can not be trusted" (this is not the exact message but close to it).
The message only seemed to come once as if I restarted it would disappear.
When I went back to fastboot it would say locked until i did over the fastboot oem unlock command (in other words I had to unlock everytime).
Also when I go to reboot; something about "Lock" would come in the command prompt statuses just before it rebooted.
It seems like the bootloader kept getting locked again.
So I could not boot into TWRP.
I then tried using the "fastboot boot xx.img" command which after several attempts and variations worked.
I flashed the Letv-X620-Twrp-3.0.2-0 and then "fastbook boot" booted from ANOTHER version of TWRP (as it would not boot using that same TWRP).
Then when the phone was about to restart I held up the volume up button and it booted to TWRP.
(That recovery (which I booted from) was from the ROM LeEco+x620+CM13+Rom+v145+by+Kangburra which I also downloaded from XDA.)
However the touch screen wouldnt work and I had to use a USB mouse (using the adaptors/OTG cable) and was able to control the phone in the TWRP.
I wiped the dalvik and cache and loaded the rom and it completed. then it asked to reboot which i did; and then it just wouldnt start.
The present status is that there is nothing on the Phone. I cannot boot to recovery nor to fastboot.
The only reaction I get from the phone is if I plug in a USB cable (charger). I have it plugged into the PC and the PC sound for when a device is plugged in and the sound for when a device is plugged out plays rapidly within 2-3 seconds (ie it connects/disconnects quickly).
The adb/fastboot commands do NOT work. The computer does not include it in devices etc.
I would therefore be grateful if I can have some assistance. I would like the phone to work again (obviously).
Thank you for your time.