Related
Last night I was on my nexus before I would go to bed. I opened the franco kernel app and then noticed that r6 was available for download. I downloaded and flashed it and was about to go to sleep when I noticed the notification light that my phone was charging. I thought it was neat then tried to get some sleep, but my promised sleep did not come quick. After a good chunk of time had passed, I thought that my lack of sleep was caused by the green light that was barely noticable. I searched and searched in the app to try and find an option to disable the LED, but could not. I then decided that the best way to get rid of the light, would be to flash the older r5 kernel so I wouldn't have to see the light anymore. I hit flash and my phone rebooted and then brought me to the bootloader. I attempted to reboot but I could not. I've tried using adb and nexus root toolkit to get my device to work again, but they can't seem to find it without the correct drivers. I installed Motorola device manager, nothing. I tried to follow the instructions in the toolkit to get the correct drivers installed but I can't continue with the need to enable debugging, which I cannot do from being stuck at the bootloader.
Under bootloader logs, I have the following messages:
Invalid boot image size!
failed to validate boot image
Fastboot Reason: Fall-through from normal boot mode
Any help would be greatly appreciated.
USB debugging is an android setting. It can only be used when android is running. If you had USB debugging on, it would make absolutely no difference in recovery or bootloader so don't let that step stop you.
From the logs, it sounds like your kernel download is corrupt or didn't flash properly. I had a similar message when I flashed a partially downloaded recovery image today.
Just fastboot flash a complete boot image
I tried that last night by launching adb and doing 'adb devices' but my device is unrecognized and I am unsure of how to go about fixing that.
thecupman said:
I tried that last night by launching adb and doing 'adb devices' but my device is unrecognized and I am unsure of how to go about fixing that.
Click to expand...
Click to collapse
Tried what exactly? Adb and fastboot are two different things. Adb works in android or recovery only. Fastboot works in boot loader only. Boot to boot loader and do "fastboot devices"
Ah that was my mistake. But the fastboot devices command just returns a new line for a new command to be entered in
thecupman said:
Ah that was my mistake. But the fastboot devices command just returns a new line for a new command to be entered in
Click to expand...
Click to collapse
That probably means there is a blank line between them - showing that no device is found. Unlike Adb it just gives a blank line instead of "no devices".
Probably means a driver issue or cable issue. Try different USB ports / cables if you can. Check to see if there are any yellow triangles in device manager too.
I'm new to this phone so I don't know where the drivers are if you need them. If I ever find them, I'll port my nexus 5 Adb and fastboot thread over here. Unfortunately i use Linux at home so I don't really have a driver issue.
Oh, so if I were to use Linux I wouldn't have to deal with missing drivers? I'm assuming that's the issue since no matter which port I use, 'Connect USB Data Cable' doesn't change
thecupman said:
Oh, so if I were to use Linux I wouldn't have to deal with missing drivers? I'm assuming that's the issue since no matter which port I use, 'Connect USB Data Cable' doesn't change
Click to expand...
Click to collapse
I can't say for sure. In Linux you may need to add UDEV rules. I didn't though. My bootloader is just recognised.
Please do check your device manager though.
I'm sorry i can't help more right now. I'm going to bed.
Okay, thank you! I'll reply if I encounter any other errors!
The Google driver works for all Nexus devices (except the GNex): http://developer.android.com/sdk/win-usb.html
I am not new to flashing phones, but I cannot figure this out. I can run Mofo and Mofoverify, but I cannot run a fastboot commands like "fastboot flash logo logo.bin". All I get is waiting for device. " Adb devices" and "fastboot devices" both return an empty list in there respective modes. Now I have tried several similar but not the same fixes from many Google and XDA searches. I have tried all sort of driver solutions, USB cables, toggleing of settings in my phone and such. I have used Mofo without issue and still can, but fastboot won't let me flash the setup files for Lollipop and I want me some sweetness! I have a newer Windows 8.1 machine and the XT1254. Lastly, this is my first Q&A thread post, so please be gentle. Thank you ahead of time, because this is XDA, and it can solve anything!
DragonRyderX said:
I am not new to flashing phones, but I cannot figure this out. I can run Mofo and Mofoverify, but I cannot run a fastboot commands like "fastboot flash logo logo.bin". All I get is waiting for device. " Adb devices" and "fastboot devices" both return an empty list in there respective modes. Now I have tried several similar but not the same fixes from many Google and XDA searches. I have tried all sort of driver solutions, USB cables, toggleing of settings in my phone and such. I have used Mofo without issue and still can, but fastboot won't let me flash the setup files for Lollipop and I want me some sweetness! I have a newer Windows 8.1 machine and the XT1254. Lastly, this is my first Q&A thread post, so please be gentle. Thank you ahead of time, because this is XDA, and it can solve anything!
Click to expand...
Click to collapse
Any way you could try it on a Windows 7 machine?
Where did you get your fastboot files? If mofo detects it then your fastboot files are jacked up
Go here: http://dl.google.com/android/android-sdk_r24.3.3-windows.zip
Once you extract it, run SDK Manager, Select to install Android SDK Tools, Platform-Tools.
Once that's done, go to \android-sdk-windows\platform-tools. Hold shift, right click and Open Command Prompt. Then fastboot will work
O
Here's an easy way to install Fastboot/ADB.
Once that is installed you'll have to change your commands to fit the file path of the fastboot files.
For example:
Code:
fastboot flash logo C:\Users\OP\Desktop\logo.bin
[/COLOR]
savagebunny said:
Where did you get your fastboot files? If mofo detects it then your fastboot files are jacked up
Go here: http://dl.google.com/android/android-sdk_r24.3.3-windows.zip
Once you extract it, run SDK Manager, Select to install Android SDK Tools, Platform-Tools.
Once that's done, go to \android-sdk-windows\platform-tools. Hold shift, right click and Open Command Prompt. Then fastboot will work
O
Click to expand...
Click to collapse
DragonRyderX said:
I am not new to flashing phones, but I cannot figure this out. I can run Mofo and Mofoverify, but I cannot run a fastboot commands like "fastboot flash logo logo.bin". All I get is waiting for device. " Adb devices" and "fastboot devices" both return an empty list in there respective modes. Now I have tried several similar but not the same fixes from many Google and XDA searches. I have tried all sort of driver solutions, USB cables, toggleing of settings in my phone and such. I have used Mofo without issue and still can, but fastboot won't let me flash the setup files for Lollipop and I want me some sweetness! I have a newer Windows 8.1 machine and the XT1254. Lastly, this is my first Q&A thread post, so please be gentle. Thank you ahead of time, because this is XDA, and it can solve anything!
Click to expand...
Click to collapse
This minimal version of fastboot is a lot smaller and worked for me.
I have used minimal Adb/fastboot. I don't know if it helps, but when in Android, even after revoking USB debugging authorizations, I never get asked on my phone to re-authorize my pc. As for a Windows 7 machine, I could downgrade my laptop, but I wanted that to be a last resort.
@savage- sorry for posting this on ComputerFreaks thread, but it was his image I am trying to install and figured someone doing the same as me may have had same issue, but I'm sorry.
DragonRyderX said:
I have used minimal Adb/fastboot. I don't know if it helps, but when in Android, even after revoking USB debugging authorizations, I never get asked on my phone to re-authorize my pc. As for a Windows 7 machine, I could downgrade my laptop, but I wanted that to be a last resort.
@savage- sorry for posting this on ComputerFreaks thread, but it was his image I am trying to install and figured someone doing the same as me may have had same issue, but I'm sorry.
Click to expand...
Click to collapse
A windows 7 machine is unnecessary. I used windows 8.1 pro x64 to perform the whole upgrade process without a hitch. If mofo functions correctly, that means the fastboot drivers are installed correctly. If you start up minimal adb/fastboot, plug in your phone while it's in fastboot mode and type "fastboot devices," what do you get?
EDIT: Duh. You already said that it says returns nothing. Well in that case there has to be some sort of problem with the USB connection or the minimal adb/fastboot installation. Maybe try running the minimal adb/fastboot shortcut as administrator. I don't remember having to do that on mine, but who knows?
St33ve- see OP, nothing listed for adb or fastboot devices commands in their respective modes.
Have you tried a different USB cable?
Yonnor said:
Have you tried a different USB cable?
Click to expand...
Click to collapse
Yes, about 7 different ones. 4 that I am sure have worked before, and no physical damage to them.
You said Mofo is able to see your device though, so that's kind of throwing me through a loop. You could try a fresh install of the Minimal ADB, and double check your drivers?
That's a sign of drivers not being installed!
Try opening up device manager n see if the driver is not installed.... If u see a device with an exclamatory mark n "quark" somewhere in it... The drivers aren't installed...
When the phone is in fastboot mode, the phone is listed as quark fastboot, but no exclamation mark. I reflashed computerfreaks image (KK) without an issue, but still isn't recognized in fastboot or Adb. I really want to flash me some Lollipop! I have crack flashed with every phone I own. I'm going thru withdrawals here LOL.
i am having the exact same issues. I've reinstalled drivers, switched usb cords and have had no success.
I'm not certain what actual fixed mine because I tried so many things but I got mine to recognize my phone. I think what did it was revoking the USB debugging authorizations and deleting the adb files on my computer under username/.Android. Then reauthorizing my phone. That and I believe I may have had duplicate drivers interfering with each other. Hope this helps
Hallelujah, I have lollipop!!!
I do not know exactly what the issue was but after factory resetting windows 8.1, and manually loading each driver for adb and fastboot, it works (again). I wish there was a Thank All Button. THANKS ALL!!!
Alright, I somewhat hate Android 6.0, and that's because of my hard time rooting my Nexus 6, which is, at this point, becoming immensely irritating. If I'm allowed to do so here, since this is a Q&A board, I need to ask how the hell to root this thing, because of Android's new thing where I have to install a custom kernal to get root.
All I really know, now, ids that I need to unlock the bootloader of the phone, which I've been trying to do (installed SDK's platform tools, made sure my Nexus 6 Windows drivers are installed, but when I open a command prompt to unlock the bootloader, I'm met with a, "no devices found," response, so I have no clue what to do, and need some help, because with how many tutorials I've looked up for how to do this, and none of them working, I'm about heady to break my monitor. If anyone can explain what the **** I'm doing wrong, or link to a tutorial for how to unlock the bootloader, that actually explains what's needed to do so, it'd be appreciated.
Da-JesuZ said:
Alright, I somewhat hate Android 6.0, and that's because of my hard time rooting my Nexus 6, which is, at this point, becoming immensely irritating. If I'm allowed to do so here, since this is a Q&A board, I need to ask how the hell to root this thing, because of Android's new thing where I have to install a custom kernal to get root.
All I really know, now, ids that I need to unlock the bootloader of the phone, which I've been trying to do (installed SDK's platform tools, made sure my Nexus 6 Windows drivers are installed, but when I open a command prompt to unlock the bootloader, I'm met with a, "no devices found," response, so I have no clue what to do, and need some help, because with how many tutorials I've looked up for how to do this, and none of them working, I'm about heady to break my monitor. If anyone can explain what the **** I'm doing wrong, or link to a tutorial for how to unlock the bootloader, that actually explains what's needed to do so, it'd be appreciated.
Click to expand...
Click to collapse
This is how i always root the phone:
- Enable usb debugging and ENABLE OEM UNLOCKING in developer options
- Reboot into the bootloader and type fastboot oem unlock and let the phone boot up
- Flash TWRP in fastboot
- Go to recovery and flash a modified boot.zip (all custom kernels will do)
- Flash the latest superSU.zip, also in recovery
- Done
Here is a tut for the adb setup (Windows) http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/.
- Reboot into the bootloader and type fastboot oem unlock and let the phone boot up
That's my problem. Opening up the command prompt and typing, "fastboot OEM unlock," does absolutely nothing. No prompts come up on the phone. It just sits there, and doesn't do anything.
Da-JesuZ said:
- Reboot into the bootloader and type fastboot oem unlock and let the phone boot up
That's my problem. Opening up the command prompt and typing, "fastboot OEM unlock," does absolutely nothing. No prompts come up on the phone. It just sits there, and doesn't do anything.
Click to expand...
Click to collapse
Do you see a serial number in fastboot if you type: fastboot devices? If not your drivers aren`t installed correctly or adb isn`t setup correctly.
gee2012 said:
Do you see a serial number in fastboot if you type: fastboot devices? If not your drivers aren`t installed correctly or adb isn`t setup correctly.
Click to expand...
Click to collapse
I'm using Windows Vista, so I had to add an underscore, and type, "fastboot oem_unlock," to get the bootloader unlocked. Everything is restoring, now, however, I'm wondering if I'll have to do something similar with flashing TWRP, and the kernal I'm attempting to install. I don't know programming or cmd commands.
Da-JesuZ said:
I'm using Windows Vista, so I had to add an underscore, and type, "fastboot oem_unlock," to get the bootloader unlocked. Everything is restoring, now, however, I'm wondering if I'll have to do something similar with flashing TWRP, and the kernal I'm attempting to install. I don't know programming or cmd commands.
Click to expand...
Click to collapse
You only have to flash the TWRP.img file in fastboot, the rest (boot/superSU) are zip files to be flashed in recovery. I have no experience with Vista so can`t help you there, maybe there is some info about it on Google/YouTube.
Hi,
I looked all over the place but could not find a way to unlock the bootloader of the latest version of my device. Currently running Android 6.0 H81120p and rooting this version as well!
hammy88 said:
Hi,
I looked all over the place but could not find a way to unlock the bootloader of the latest version of my device. Currently running Android 6.0 H81120p and rooting this version as well!
Click to expand...
Click to collapse
i recommend for you to KDZ 20p refurbished..
and heres the instruccions same as 20i
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
i tried but its not working as i get stuck on waiting for device after i type the command to reboot to bootloader, installed google usb drivers , lg drivers and all but nothing seemed to be fixing the issue
hammy88 said:
i tried but its not working as i get stuck on waiting for device after i type the command to reboot to bootloader, installed google usb drivers , lg drivers and all but nothing seemed to be fixing the issue
Click to expand...
Click to collapse
did you click on screen when you gave the command to go into fastboot it shows some sort of numbers and leters and asks you if you want to allow phone .??/ did you
Yes I did allow the computer to have access to the phone, when i typed the command to reboot to bootloader it did, but then when i type the command to fastboot oem unlock it gets stuck on waiting for any device. I tried doing it again just to check, after i get to bootloader, i typed adb devices it doesn't show any device thats connected
hammy88 said:
Yes I did allow the computer to have access to the phone, when i typed the command to reboot to bootloader it did, but then when i type the command to fastboot oem unlock it gets stuck on waiting for any device. I tried doing it again just to check, after i get to bootloader, i typed adb devices it doesn't show any device thats connected
Click to expand...
Click to collapse
adb reboot bootloader (phone reboots to bootloader)
fastboot oem unlock (this wipes ALL data!!)
debugging tick and unlock oen in dev options.?
raptorddd said:
adb reboot bootloader (phone reboots to bootloader)
fastboot oem unlock (this wipes ALL data!!)
debugging tick and unlock oen in dev options.?
Click to expand...
Click to collapse
I checked the oem unlock, and the USB debugging thing is checked as well. Developers Options is on but same issue. I installed the latest USB drivers, installed Google USB drivers. I went to device Manger and I can't see that my device is even connected!
hammy88 said:
I checked the oem unlock, and the USB debugging thing is checked as well. Developers Options is on but same issue. I installed the latest USB drivers, installed Google USB drivers. I went to device Manger and I can't see that my device is even connected!
Click to expand...
Click to collapse
can try another computer maybe. i use the drivers from LGUP..
am afraid i do not know how to proceed from here. am pretty sure you are not alonei gave read someting similar but.. i didnt pay attention
I tried 3 other computers , did not help resolve the issue
hammy88 said:
I tried 3 other computers , did not help resolve the issue
Click to expand...
Click to collapse
i came across this try it.
http://forum.xda-developers.com/showpost.php?p=69339003&postcount=2
Use Linux dude, also try different cables. My stock g4 came with a bad cable that only charged.
I've had exactly the same problem as hammy88. Is what is referred to as "fastboot mode" the same as download mode? I know it's relatively easy to get into download mode. But "adb reboot bootloader" doesn't work for me.
Fastboot mode ≠ Download mode
If you did tick "Enable OEM unlock" , and adb reboot bootloader doesn't work, then I guess is BL is locked now.
I tried the method , i found that Android Bootloader does not have a green light, so i went to device manager to try to update the driver but it wasn't even there, clicked on view to show the hidden items or whatever then found android device, when i clicked update the driver i could not find the Google fastboot thing to update it with, all i got was either LG usb or ADB interface even thoough i downloader google fastboot usb drivers few days ago
hammy88 said:
I tried the method , i found that Android Bootloader does not have a green light, so i went to device manager to try to update the driver but it wasn't even there, clicked on view to show the hidden items or whatever then found android device, when i clicked update the driver i could not find the Google fastboot thing to update it with, all i got was either LG usb or ADB interface even thoough i downloader google fastboot usb drivers few days ago
Click to expand...
Click to collapse
Brother, be calm. Find the fastboot drivers. And update.
You will figure it out. Just do it.
I received my new sony 1 ii and have checked and the bootloader can be unlocked and the phone can be rooted. I thought I was away to the races but I'm mystified. I can't get the phone to boot into fast boot.
I appears I have the drivers in place and the phone is recognized by the computer but no luck with fast boot.
I have searched and can't seem to find out why this is. I suspect some kind of driver issue with win10 but when I connect to the computer with the phone off and hold the up-volume nothing happens. I have also tried to boot into recovery mode and that does not work as well. Any help would be appreciated.
blkair445 said:
I received my new sony 1 ii and have checked and the bootloader can be unlocked and the phone can be rooted. I thought I was away to the races but I'm mystified. I can't get the phone to boot into fast boot.
I appears I have the drivers in place and the phone is recognized by the computer but no luck with fast boot.
I have searched and can't seem to find out why this is. I suspect some kind of driver issue with win10 but when I connect to the computer with the phone off and hold the up-volume nothing happens. I have also tried to boot into recovery mode and that does not work as well. Any help would be appreciated.
Click to expand...
Click to collapse
On Sony devices you need to power off and hold volume up and plug in the USB cable. That should leave the blue LED to indicate fastboot mode. I'm not 100% sure since it's been a while since I've messed around with Sony devices
Thanks for the input. I have done that and am still unable to action ADB - It is a little confusing since the phone only shows the blue light and nothing else.
If I normally boot the phone it will register as an ADB device. I also find it strange that it will not boot into recovery. The android icon flashes but when you release it boots to safe mode. I assume it is a driver issue but it is not revealing its self to me . Cheers
blkair446 said:
Thanks for the input. I have done that and am still unable to action ADB - It is a little confusing since the phone only shows the blue light and nothing else.
If I normally boot the phone it will register as an ADB device. I also find it strange that it will not boot into recovery. The android icon flashes but when you release it boots to safe mode. I assume it is a driver issue but it is not revealing its self to me . Cheers
Click to expand...
Click to collapse
The blue light is fastboot mode. There is no ui interface in fastboot for sony devices. Just a blue light and black screen.
R800x_user said:
On Sony devices you need to power off and hold volume up and plug in the USB cable. That should leave the blue LED to indicate fastboot mode. I'm not 100% sure since it's been a while since I've messed around with Sony devices
Click to expand...
Click to collapse
Same person but had to change user name -- more on the issue
I managed to unlock the boot loader and it seems that at every step for rooting I am running into curve balls. Windows was not working for me so I managed to unlock the bootloader with Linux and going on to the next step I had to go back to windows to find a current factory ROM.
The next issue: going back to the "how to" I am unable to located boot.xxxxx.sin in the factory ROM and the closest I could find is boot_x-Flash-ALL-2389.sin and that doesn't work.
In the boot directory all files are bootloader_X_44 and a combination of zip and sin files
Can anyone steer me through the muddy waters
The factory rom was downloaded through XperiaFirm application
blkair446 said:
Same person but had to change user name -- more on the issue
I managed to unlock the boot loader and it seems that at every step for rooting I am running into curve balls. Windows was not working for me so I managed to unlock the bootloader with Linux and going on to the next step I had to go back to windows to find a current factory ROM.
The next issue: going back to the "how to" I am unable to located boot.xxxxx.sin in the factory ROM and the closest I could find is boot_x-Flash-ALL-2389.sin and that doesn't work.
In the boot directory all files are bootloader_X_44 and a combination of zip and sin files
Can anyone steer me through the muddy waters
The factory rom was downloaded through XperiaFirm application
Click to expand...
Click to collapse
May I know how did you unlock the bootloader? Did you use xperia 1 as your device in https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/#unlock-code?
I have already installed usb drivers and have the platform tools. But everytime I boot my device to fastboot, whether using "adb reboot bootloader" or power button + volume up, screen only shows black (led is solid blue). I did left it for a couple of minutes, nothing happened.
jepher said:
May I know how did you unlock the bootloader? Did you use xperia 1 as your device in ?
I have already installed usb drivers and have the platform tools. But everytime I boot my device to fastboot, whether using "adb reboot bootloader" or power button + volume up, screen only shows black (led is solid blue). I did left it for a couple of minutes, nothing happened.
Click to expand...
Click to collapse
I unlocked my bootloader after obtaining the unlock code from sony developers I used adb/fastboot commands in linux mint. Pretty straight forward but the next step for rooting is giving me issues. Just select xperia 1 and the imei number will identify your phone -- cheers
blkair446 said:
I unlocked my bootloader after obtaining the unlock code from sony developers I used adb/fastboot commands in linux mint. Pretty straight forward but the next step for rooting is giving me issues. Just select xperia 1 and the imei number will identify your phone -- cheers
Click to expand...
Click to collapse
Yes I followed those. But may I know how long it took you to finish the unlocking?
Install ADB/SDK drivers
Download platform tools
Plug the device
Make sure adb can see my device
Use adb reboot bootloader command
Device booted to fastboot mode
Execute the command with the unlock code
...stucked here
If I miss something. Please do let me know
jepher said:
Yes I followed those. But may I know how long it took you to finish the unlocking?
Install ADB/SDK drivers
Download platform tools
Plug the device
Make sure adb can see my device
Use adb reboot bootloader command
Device booted to fastboot mode
Execute the command with the unlock code
...stucked here
If I miss something. Please do let me know
Click to expand...
Click to collapse
I assume you are using windows and I must say I gave up trying to get win10 to work and I was stuck at the same place you are. I then switched to linux and it went a lot smoother and I didn't need all those tools as laid out in the description.
In linux you must use the phone to go into fastboot mode if you boot from computer it actually boots to a visible screen on the phone and I didn't have connection that would take the command line commands. Linux is very good because if you are missing something it will give you a link or a command line input when you execute the ADB or Fastboot command.
I have run a windows/linux dual boot desktop for a while now and I'm no expert but coming from the era of command line I can muddle through. Sorry if I can't give you more info on windows but win10 is such a pain and I find that with a lot of things linux works better. If I didn't need adobe acrobat I would not even bother with windows.
cheers
blkair446 said:
I assume you are using windows and I must say I gave up trying to get win10 to work and I was stuck at the same place you are. I then switched to linux and it went a lot smoother and I didn't need all those tools as laid out in the description.
In linux you must use the phone to go into fastboot mode if you boot from computer it actually boots to a visible screen on the phone and I didn't have connection that would take the command line commands. Linux is very good because if you are missing something it will give you a link or a command line input when you execute the ADB or Fastboot command.
I have run a windows/linux dual boot desktop for a while now and I'm no expert but coming from the era of command line I can muddle through. Sorry if I can't give you more info on windows but win10 is such a pain and I find that with a lot of things linux works better. If I didn't need adobe acrobat I would not even bother with windows.
cheers
Click to expand...
Click to collapse
Yes I am using w10. Will try linux later. I have searched everywhere and stucked at the same step. Thank you.
I have managed to unlock the bootloader and root the phone. But problem is. I can't write on the root folder.
More to this I think I might have located the boot file boot_X-flash-all-2396.sin but using magisk it returns no boot image found. I see the guide says use the canary built but that seems to have been shut down, so at an impasse here and am still reaching out for help - damn op phone were never this funky
I might as well put this one out there then -- Is there anyway to flash a op 8 pro in2025 to dual sim - it's the cause of this painful trip
I was reverting my phone to unroot and locked bootloader. And it is saying that "Your Device is corrupt. It can't be trusted and will not boot" loop.
I tried flashing it using the new flasher. But after flashing, it will do SONY boot loop. If I connect it to a charger it goes back to "Your Device is corrupt. It can't be trusted and will not boot" loop.
I can't use Sony Companion since it is saying that my battery is low, and I can't charge the phone since it will just continue looping.
Do you know/have any recovery.img?
Edt: Fixed my phone. Relocked the bootloader
jepher said:
I was reverting my phone to unroot and locked bootloader. And it is saying that "Your Device is corrupt. It can't be trusted and will not boot" loop.
I tried flashing it using the new flasher. But after flashing, it will do SONY boot loop. If I connect it to a charger it goes back to "Your Device is corrupt. It can't be trusted and will not boot" loop.
I can't use Sony Companion since it is saying that my battery is low, and I can't charge the phone since it will just continue looping.
Do you know/have any recovery.img?
Edt: Fixed my phone. Relocked the bootloader
Click to expand...
Click to collapse
Any chance you could post the steps to relock successfully? I presume using the fastboot commands etc though did you then just re run the command to relock the bootloader? Many thanks
cd993 said:
Any chance you could post the steps to relock successfully? I presume using the fastboot commands etc though did you then just re run the command to relock the bootloader? Many thanks
Click to expand...
Click to collapse
Yes. Relock it using fastboot command.
I use ubuntu to do it. If you can run fastboot commands in windows10 lucky you.