I’m also having an issue regarding my XZ1 Compact and Xperifix. I purchased Xperifix and I tried to use it with my XZ1 Compact (G8441, 47.1.A.12.179) yesterday. Unfortunately, it did not work.
Unlike the online video which demonstrates the process, when my phone boots during the process, the white Sony intro screen remains visible for a long time. Then I get a message saying: “It appears that TWRP is not booting. Please do it manually…” followed by instructions on how to do so. I follow these, eventually pressing volume down until TWRP appears, and then reconnecting the USB and pressing OK.
Although Xperifix indicates that it is continuing the process, TWRP remains on screen and nothing further happens. Eventually, I get the same “It appears that TWRP is not booting. Please do it manually…” message for a second time. Again, I follow there instructions. As before, Xperifix seems to indicate that it is performing normally. I then get a message telling me to check my phone to check that all has worked correctly. Unfortunately, it has not.
I have now completed this process perhaps six or seven times and the same thing happens every time. Can anybody please advise as to what I may be doing wrong or what I need to do in order for the software to run as intended?
Prior to running Xperifix, I unlocked my bootlaoder, resulting in green pictures from the camera. I was aware that this would happen, but I did so with a reasonable level of confidence that Xperifix would then resolve this issue for me. Obviously, it has not. So, even if there is no advice out there on how to get Xperifix to run successfully on my device, any advice on other methods of getting around this DRM issue would also be much appreciated.
Thank you in advance
Free25 said:
I’m also having an issue regarding my XZ1 Compact and Xperifix. I purchased Xperifix and I tried to use it with my XZ1 Compact (G8441, 47.1.A.12.179) yesterday. Unfortunately, it did not work.
Unlike the online video which demonstrates the process, when my phone boots during the process, the white Sony intro screen remains visible for a long time. Then I get a message saying: “It appears that TWRP is not booting. Please do it manually…” followed by instructions on how to do so. I follow these, eventually pressing volume down until TWRP appears, and then reconnecting the USB and pressing OK.
Although Xperifix indicates that it is continuing the process, TWRP remains on screen and nothing further happens. Eventually, I get the same “It appears that TWRP is not booting. Please do it manually…” message for a second time. Again, I follow there instructions. As before, Xperifix seems to indicate that it is performing normally. I then get a message telling me to check my phone to check that all has worked correctly. Unfortunately, it has not.
I have now completed this process perhaps six or seven times and the same thing happens every time. Can anybody please advise as to what I may be doing wrong or what I need to do in order for the software to run as intended?
Prior to running Xperifix, I unlocked my bootlaoder, resulting in green pictures from the camera. I was aware that this would happen, but I did so with a reasonable level of confidence that Xperifix would then resolve this issue for me. Obviously, it has not. So, even if there is no advice out there on how to get Xperifix to run successfully on my device, any advice on other methods of getting around this DRM issue would also be much appreciated.
Thank you in advance
Click to expand...
Click to collapse
Just a wild guess, as I have zero experience with Xperifix: make sure you are on the latest TWRP version (posted yesterday) to get data partition decryption to work for sure (independent on which security patch level you are on).
I advice you to use the official support you purchased with Xperifix.
4rz0 said:
I advice you to use the official support you purchased with Xperifix.
Click to expand...
Click to collapse
Good point I didn't realize it was paid-for software.
Free25 said:
what I need to do in order for the software to run as intended?
Click to expand...
Click to collapse
It sounds like you don't have the right drivers installed. You need Google USB drivers to be registered when you plug the phone in while running TWRP. This is tricky because by default Windows chooses the wrong drivers and you have to manually add/change them while TWRP is running. If you start the Xperia fix, manually start TWRP, set system as writable then plug it back in, you will see Xperiafix take control of the phone and reboot it. The fact it doesn't makes me think it's drivers.
Don't forget that Windows10 lies to you when it says it's installed the ADB drivers and you have to go into safe mode and 'disable signature checking' on the driver install
Xperiafix works, I used it, but getting the drivers right took me a couple of days..
You could read through the original app thread to find out a little bit more about how it works and there are even links to the drivers
you have to install at first the USB drivers for XZ1c.
if use use Windows 8+ you have to boot into the deactivated driver signature mode and install the driver.
On xperifix I can tell you, it downloads every time an old TWRP for XZ1C, which won't work with new firmware versions.
download the new TWRP version from our TWRP thread. then download portable minimal adb and fastboot, extract it on a place.
next step, start cmd.exe from start menu, enter the following command to switch in cmd into the path:
cd <path you have extracted minimal adb and fastboot >
enter the following command and don't execute it:
fastboot flash recovery <path were your downloaded TWRP is>
don't execute it!
reboot your phone into fastboot.
now start xperifix, click on fix device, and when you have a white Sony logo, plug out phone and reboot again into fastboot.
now switch to cmd.exe and execute the command.
press the key "up" to get the command again and replace the words "flash recovery" with "boot" and execute it again.
now your phone will boot into correct TWRP and let xperifix finish it's progress.
after restart, all should work.
you have at least to install the magisk manager and you will have working cam and magisk.
Thanks for all the advice thus far. I had already contacted the guys at Xperifix but am awaiting a response from them.
Within TWRP, the box marking the system read-only was already unchecked.
I had already visited https://developer.sony.com/develop/drivers/ and downloaded the ZX1 Compact drivers.
When in fastboot mode, my phone is recognised in device manager as Android Device – Sony ADB Interface. And, if I open a command prompt window from the Minimal ADB and Fastboot folder and enter “fastboot devices”, my phone is recognised.
Would this – the fact that my device is being recognised in fastboot mode - indicate that I have the correct drivers installed?
Sorry for all the newbie questions – I’d rooted a phone previously but it was years back, I’ve forgotten more than I remember, and I’m in a bit over my head. My own fault but, again, any further help in resolving this gratefully received. As you said Didgesteve, it works, I just need to figure out where I’m going wrong
if you test fastboot devices and you get a serial number, the driver is correct working.
test it with my method to replace TWRP after xperifix is started.
Raz0Rfail, just saw your post after my last response. Will take a look over that now. Thank you.
Free25 said:
I just need to figure out where I’m going wrong
Click to expand...
Click to collapse
Check out the link to the drivers I posted above, there's a how to video that's helpful
On the TWRP download list, I don’t see an option for the XZ1 Compact; only for the XZ or XZ premium. For both of these options, the most recent TWRP version listed is 3.2.1-0, and this is the version that Xperifix installed on my device. Would this indicate that Xperifix is giving me the most recent version?
Free25 said:
On the TWRP download list, I don’t see an option for the XZ1 Compact; only for the XZ or XZ premium. For both of these options, the most recent TWRP version listed is 3.2.1-0, and this is the version that Xperifix installed on my device. Would this indicate that Xperifix is giving me the most recent version?
Click to expand...
Click to collapse
Here you get the correct twrp for XZ1C:
https://forum.xda-developers.com/xp...t/recovery-twrp-3-1-1-stock-security-t3706704
Didgesteve said:
Check out the link to the drivers I posted above, there's a how to video that's helpful
Click to expand...
Click to collapse
Thanks, I did have a look at that, but from what I'm seeing and reading (unless I'm missing something), it seems like this mightn't be a driver issue.
Free25 said:
Thanks, I did have a look at that, but from what I'm seeing and reading (unless I'm missing something), it seems like this mightn't be a driver issue.
Click to expand...
Click to collapse
The driver you use works.
What else is your problem?
I suspect that it’s TWRP, as you suggested. I downloaded ‘twrp-3.2.1-0-lilac-14’ and ‘twrp-3.2.1-0-lilac-14.img.asc’ (thank you for the link). I already had Minimal ADB and Fastboot installed.
I changed cmd directory to C:\Program Files (x86)\Minimal ADB and Fastboot, then entered ‘fastboot flash recovery C:\Users\25D\Downloads\TWRP\twrp-3.2.1-0-lilac-14’ (to where I had extracted the .img file)
I rebooted the phone into fastboot, activated Xperifix, waited for the white Sony screen, plugged out the phone, turned it off, plugged it back in in fastboot and executed the command. I erred somewhere however, as I received the response that the command is not recognised.
Probably a very elementary mistake on my part. Can you see where I went wrong?
the twrp filename has to be twrp-3.2.1-0-lilac-14.img with tab key you can do autocomplete
Tried it a few times now, got the
fastboot flash recovery C:\Users\25D\Downloads\TWRP\twrp-3.2.1-0-lilac-14.img
and
fastboot boot C:\Users\25D\Downloads\TWRP\twrp-3.2.1-0-lilac-14.img
to run successfully after rebooting in fastboot during the Xperifix process.
Still no joy though
The idea for correct path is, press shift + right mouse click on image file, then click copy path in contextmenu.
In cmd right mouse click and click on insert.
Thanks, I got the right path in the end and the flash recovery and boot seemed to run fine but it didn't seem to have any effect on the results from Xperifix
Free25 said:
Thanks, I got the right path in the end and the flash recovery and boot seemed to run fine but it didn't seem to have any effect on the results from Xperifix
Click to expand...
Click to collapse
Post the log files from C:\Xperiafix
This will show what's happening
Drivers is still my top guess
Related
My C6903 in LP 5.1.1 doesn't take photos (or videos) when the app tries to focus. Without focus enabled (using other app) it goes perfectly. I've tried with 14.6.A.1.236 Customized BAL, 15.5.A.0.242 Movistar AR and a few more, all obtained from XperiFirm.
I tried pushing that "4k and timeshift" .zip which I read could fix the camera but no luck.
Curious thing is that Rooting Status shows "Unknown", I don't know if this could be related or not. I bought the phone on eBay (used) and I couldn't tell you if it's been unlocked or not.
But I know that everything can't be messed up because in JB 4.3 (14.2.A.1.136 Generic BAL from XperiFirm) camera works well, and Rooting Status shows "Bootloader Unlock Allowed: Yes"; And in KK 4.4 (updated via OTA from mentioned JB firmware) camera stops working in the same way but Rooting Status keeps on "Bootloader Unlock Allowed: Yes".
What could I try? I think I've already read everything related to the Rooting Status Unknown and Camera freeze problems in this forum and still have no clue (even in other Xperias forums too).
Thanks by the way
PS: Yet I didn't tried unlocking bootloader just because it may bring more problems, but if needed I would do it in a blink
matidx said:
PS: Yes I didn't tried unlocking bootloader just because it may bring more problems, but if needed I would do it in a blink
Click to expand...
Click to collapse
This is definitely a bad way to troubleshoot your problem, but go ahead and make yourself a backup of your phone's TA partition and unlock the bootloader of your phone. As long as you made a backup of the partition, the DRM keys will stay intact when you re-lock the bootloader; thus, you won't lose any exclusive Sony features upon restore. Make sure you have the proper adb and fastboot drivers before you begin.
Backup TA partition: http://forum.xda-developers.com/showthread.php?t=2292598
Unlock bootloader: http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
Flash any custom ROM (don't flash the Marshmallow ROMs) found in either the Android Development or Original Development page for Z1. You can also flash a modified Sony ROM in the Android Development section that has mostly all of the features in Sony's stock ROM plus some additional ones picked from CM/AOSP ROMs. Either way, if your problem is fixed, then it's a problem with the FTFs you flashed. If not, restore your TA/DRM keys (it'll re-lock your phone's bootloader) and report back.
Good luck fixing your problem!
kentexcitebot said:
This is definitely a bad way to troubleshoot your problem, but go ahead and make yourself a backup of your phone's TA partition and unlock the bootloader of your phone. As long as you made a backup of the partition, the DRM keys will stay intact when you re-lock the bootloader; thus, you won't lose any exclusive Sony features upon restore. Make sure you have the proper adb and fastboot drivers before you begin.
Backup TA partition: http://forum.xda-developers.com/showthread.php?t=2292598
Unlock bootloader: http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
Flash any custom ROM (don't flash the Marshmallow ROMs) found in either the Android Development or Original Development page for Z1. You can also flash a modified Sony ROM in the Android Development section that has mostly all of the features in Sony's stock ROM plus some additional ones picked from CM/AOSP ROMs. Either way, if your problem is fixed, then it's a problem with the FTFs you flashed. If not, restore your TA/DRM keys (it'll re-lock your phone's bootloader) and report back.
Good luck fixing your problem!
Click to expand...
Click to collapse
Tried that but it looks like the volume up button isn't recognized when booting or something like that. What really matters is I can't enter to fastboot mode, tried everything. Any ideas?
matidx said:
Tried that but it looks like the volume up button isn't recognized when booting or something like that. What really matters is I can't enter to fastboot mode, tried everything. Any ideas?
Click to expand...
Click to collapse
Install proper drivers for fastboot. Power the phone off completely, then while plugging your phone into the computer, hold the top volume button. You should be able to enter fastboot if fastboot drivers are properly set up.
kentexcitebot said:
Install proper drivers for fastboot. Power the phone off completely, then while plugging your phone into the computer, hold the top volume button. You should be able to enter fastboot if fastboot drivers are properly set up.
Click to expand...
Click to collapse
Is there a way to know if fastboot drivers are properly installed? I've checked and reinstalled them about 5 times, but I'll try again tomorrow just to be sure I'm not missing anything.
I don't know if there are different drivers but always installed the flashtool ones. By the way I'm running Win10 but also tried in Win7 and no luck.
matidx said:
Is there a way to know if fastboot drivers are properly installed? I've checked and reinstalled them about 5 times, but I'll try again tomorrow just to be sure I'm not missing anything.
Click to expand...
Click to collapse
If your computer can successfully detect the device and output it's serial number when you input through command prompt:
Code:
fastboot.exe devices
you'll know that fastboot is working and drivers are set up correctly. If you look at your device LED, the LED will be lit blue. Remember: you need to already have downloaded and installed the applications through the executabe in the adt folder to get the fastboot and adb applications.
matidx said:
I don't know if there are different drivers but always installed the flashtool ones. By the way I'm running Win10 but also tried in Win7 and no luck.
Click to expand...
Click to collapse
Go here to download the correct fastboot driver files: http://doomlord.xperia-files.com/download.php?dlid=Rmxhc2h0b29sLWRyaXZlcnMtMS4zLTIwMTQwMjA5
If your computer can successfully detect the device and output it's serial number when you input through command prompt:
Click to expand...
Click to collapse
Right, I know what that command line does, but that will work only when drivers are properly installed AND phone is detected. What I believe is that there are some kind of problems with the phone to not go into fastboot mode, so it wont be detected at fastboot, always in flashmode.
Is there a way to know if drivers are properly installed even if the phone isn't recognized?
Remember: you need to already have downloaded and installed the applications through the executabe in the adt folder to get the fastboot and adb applications.
Click to expand...
Click to collapse
What is the adt folder? You mean adb or the obsolete Android Development Tools (now Android Studio)?
By the way, I'm also having this issue... http://forum.xda-developers.com/xperia-z1/help/baseband-lost-reboot-t3352858
Maybe it could be related someway (like motherboard going bad or something else).
matidx said:
What is the adt folder? You mean adb or the obsolete Android Development Tools (now Android Studio)?
Click to expand...
Click to collapse
My apologies, I should've been more clear and double-checked the information!
They apparently renamed the file. I was referring "adt" to my folder that's dated all the way back to 2013, so....whoops!
You can grab the download from here: http://developer.android.com/sdk/index.html. If you don't want the entire bundle, search for "Get just the command line tools" and click on the links for your platform.
matidx said:
Right, I know what that command line does, but that will work only when drivers are properly installed AND phone is detected. What I believe is that there are some kind of problems with the phone to not go into fastboot mode, so it wont be detected at fastboot, always in flashmode.
Is there a way to know if drivers are properly installed even if the phone isn't recognized?
Click to expand...
Click to collapse
Just download the S1 driver file through the link I provided earlier, install, reboot computer, then run the same command as I told you from my previous post: if it outputs the serial number of your phone, then you're fine; but if it doesn't, post back. As long as your computer can establish a basic connection to your Z1 (PC can see it in flash mode, could access it somehow), your phone is capable of fastboot.
kentexcitebot said:
My apologies, I should've been more clear and double-checked the information!
They apparently renamed the file. I was referring "adt" to my folder that's dated all the way back to 2013, so....whoops!
You can grab the download from here: http://developer.android.com/sdk/index.html. If you don't want the entire bundle, search for "Get just the command line tools" and click on the links for your platform.
Just download the S1 driver file through the link I provided earlier, install, reboot computer, then run the same command as I told you from my previous post: if it outputs the serial number of your phone, then you're fine; but if it doesn't, post back. As long as your computer can establish a basic connection to your Z1 (PC can see it in flash mode, could access it somehow), your phone is capable of fastboot.
Click to expand...
Click to collapse
I think I've followed everything right but to be clear I'm gonna explain what I've done so far:
- Installed Android Studio (I believe it comes with those "just the command line tools").
- Installed Flashtool's driver (same as the DoomLord link you provided, even a later update than that link), also did that thing about "Disable Driver Signature Enforcement" because I'm on Win10 64bit.
- Always checked by cmd command line "fastboot.exe devices", I've never get any error (so cmd always detected it as a valid command line) or any other cmd print.
- I have a TA backup but after I made it tried to unlock bootloader but no luck. Anyway, just restored the backup and only sign I got is "Upgrading NFC firmware" or something like that after booting, the "NFC upgrade" went well but still no fastboot access.
---
- When I plug the usb + press volume up button to try get fastboot mode, phone's led goes red then green then it goes off and in flashtool I get flashmode with no led on.
---
By the way, I have an Xperia SP and already unlocked bootloader so I pretty know how it should go. Having no problem with it accessing fastboot or even locking or unlocking on the XSP.
Because of this and baseband problem, I can't stop thinking motherboard is messed up.. But anyway, whatever you think I could try just let me know.
I've followed all of the steps from this guide: http://forum.xda-developers.com/showpost.php?p=56938530&postcount=1
I've got to the end where I am running the code snippets to flash everything, but everything fails. The error stated is FAILED: remote failure. I am not sure if this is related to my developer options being turned off, but I think it might be.
Is there a way to turn developer options on while in fastboot mode or perhaps a way around this error? The reason I am stuck in the fastboot is because the boot image can't be validated, I am not at the fastboot by choice, haha.
No. If your recovery is still stock, flash the Android N Preview 1 OTA or an Android 6.0.1 OTA image from Google. One of those will restore your Nexus to operating condition, and from there you can try again. If your recovery is TWRP, flash a custom ROM.
Strephon Alkhalikoi said:
No. If your recovery is still stock, flash the Android N Preview 1 OTA or an Android 6.0.1 OTA image from Google. One of those will restore your Nexus to operating condition, and from there you can try again. If your recovery is TWRP, flash a custom ROM.
Click to expand...
Click to collapse
I apologize for my ignorance since this is all new to me, but could you explain a few things to me.
Is this what you're referring to when you say Android N Preview 1 OTA: 'https://developer.android.com/preview/download.html'
Secondly, in order to flash these, am I still following the steps I was before, or should I be following a new set of steps?
You don't need the N Preview anymore. Download your Android 6.0.1 image from the Google page and flash using the instructions given on that page.
I went to the page and followed the directions. Still doesn't work. The flash-all script reboots after the first two commands, which lock the phone. But even then, it is still giving the error FAILED:remote failure.
me too!
I seem to be having the exact same issue! i just bought a Nexus 6 online that wasn't booting, it would only show a green led when plugged in. so here I am doing everything I can think of to fix the issue but then I get hit with the "remote failure" when i try to oem unlock the bootloader! (and since the phone wont't boot i can't check the "unlock bootloader" box in the developer options) so yeah I am going to keep researching this but if anyone has any good ideas about to get around the bootloader being locked please jump right in.
anyways I may have deeper issues, the battery will not charge. i know this because when i load up the fastboot menu, which i have to do by holding the buttons while plugging it in, it should say battery charging but all it says is battery ok
I also can't load recovery because when im in the fastboot menu and i choose recovery the phone freezes and the green led comes back on... *sigh*
They have the full ota packages posted on Google site now you can and push through the stock recovery
Here just make sure you get the shame version
https://developers.google.com/android/nexus/ota#hammerhead
Sent from my Nexus 6 using XDA-Developers mobile app
I have the OTA. I also installed Wugs toolkit.
My phone is in fastboot mode due to the boot image not being able to be validated. I didn't voluntarily open up fastboot using the shortcut.
The phone is UNLOCKED until bootloader is rebooted, then it is LOCKED. If I click start, it becomes UNLOCKED again. Wug's toolkit tries to UNLOCK the phone even while the phone says it is UNLOCKED. I don't think the phone is actually UNLOCKED, however whenever it tells me it is UNLOCKED, I try to proceed with flashing and it gives me a remote failure message on each command.
The next thing I am going try is the drivers and Wug's toolkit has a driver option, so I will try that. Besides the drivers, any other ideas?
You seem to be inexperienced in rooting Android devices. If you aren't, I apologize for the assumption. However, you should learn how to use adb and fastboot without relying on the toolkit. Toolkits tend to hide diagnostic messages that adb and fastboot generate while running. This missing information makes solving problems much more difficult.
Strephon Alkhalikoi said:
You seem to be inexperienced in rooting Android devices. If you aren't, I apologize for the assumption. However, you should learn how to use adb and fastboot without relying on the toolkit. Toolkits tend to hide diagnostic messages that adb and fastboot generate while running. This missing information makes solving problems much more difficult.
Click to expand...
Click to collapse
I am inexperienced, I stated that earlier. I have check a bunch of different forum posts and a bunch of different guides. Nothing seems to be helping and it seems like such a simple problem, a boot image that can't be validated. I am not trying to do anything special with my phone, I am just trying to get it to work. I woke up and it was stuck in this 'AP Fastboot Flash Mode (Secure)' mode. It is very bare bones, not even similar to the screens within videos I have seen. One moment the phone says it's UNLOCKED, the next it's LOCKED.
You are the expert, I am not. I am merely following your directions and they don't seem to be working. I did some outside research, came to a toolkit. Toolkits are great for beginners, especially since they are UI built, are built by someone who knows the area of interest, which makes researching easier and more efficient, but on top of that, it seems to be getting me much farther than your advice, although nothing is successful at this moment.
Here is a little more context into my situation. My phone seems to be recognized by Fastboot, but not ADB (From what I found, fastboot will find devices in fastboot, and adb will find devices functioning normally, don't know how true that is.). In addition, my phone seems to switch from UNLOCKED TO LOCKED after reboots, but can become UNLOCKED again if I push ANY button. Every command I issue (i.e flash bootloader, flash radio, flash system, flash userdata) result in the message, FAILED:remote failure, which I am not sure how to avoid (I have googled, checked these forums, checked other forums and there doesn't seem to be much, if any documentation on the error), but I think it is related to the fact my developer options are turned OFF. My next course of action is to install new drivers (I checked my drivers which are said to be up to date, I also installed google USB driver through the sdk, but now I am going to look into an adb or universal driver?) and attempt to rerun everything successfully.
If you have any other ideas, or don't think its the drivers, feel free to bring it up.
As a couple of fellows said before, try this:
https://developers.google.com/android/nexus/ota
Flash a FULL OTA from the link above, not a factory image. To flash any OTA you don't need to be unlocked. I think you might be confusing the terms (with the OTA you don't have to flash anything using fastboot)
In the link there are the instructions, it's pretty straight forward and easy if you have the correct drivers installed.
OTA requires that u can startup into recovery, I cannot I can startup fastboot through key combo but when I go to select recovery the green led comes back on and the screen displaying the fastboot options remains static
I think the phone freezes because it does not appear to be able to use the battery. though there is a firm battery connection it will not charge or power on without being plugged in. maybe when I select recovery I can quickly unplug and replug the USB and maybe hold the power button to try to simulate a successful reboot.. idk just thinking aloud and working with what I got..
I also can not start in recovery mode and the OTA requires ADB, which isn't recognizing my device. I have also stated that I have followed those instructions, and nothing resulted from them, except the same messages I have been stating these last few posts.
I will try this first chance I get later tonight..
http://forum.xda-developers.com/nexus-6/help/solution-stuck-bootloop-locked-t3053783
Listen the ota doesn't get installed through fast boot, you have to select recovery through the fast boot then install the update by pushing it as bootloader does not need to be unlocked!
Sent from my Nexus 6 using XDA-Developers mobile app
holeindalip said:
Listen the ota doesn't get installed through fast boot, you have to select recovery through the fast boot then install the update by pushing it as bootloader does not need to be unlocked!
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Ok, well it seems we are at an impasse. You seem to think I can do something, so I am going to show some pictures of my screen. Its going to be blurry because I had to take it with my computer, so I apologize, but I will elaborate on each picture.
Qwertyismypw said:
Ok, well it seems we are at an impasse. You seem to think I can do something, so I am going to show some pictures of my screen. Its going to be blurry because I had to take it with my computer, so I apologize, but I will elaborate on each picture.
Click to expand...
Click to collapse
The first two pictures are when the phone is 'UNLOCKED'. The second two pictures are when the phone is 'LOCKED'. The moment I press anything in 'LOCKED' mode, the little android man goes away, and it becomes the first two pictures. WHENEVER I push a button in 'UNLOCKED' mode, nothing happens, except in the bootloader logs screen says, 'FAILED TO VALIDATE BOOT IMAGE RET -1'. I have done everything on that OTA page in every way possible. It has done me no good.
Ok, I made a little progress I think. Wugs toolkit allowed me to use TWRP on my phone and ADB is recognizing my phone now. There are a lot of options within TWRP though, so I am going to look through them all for anything relevant. Anything I should keep an extra eye out for?
If you can use twrp just download a custom ROM to your phone and move it over to SD card and flash it, then you will be able to boot and unlock the bootloader in developer ootions, that is your best bet, if you keep getting force closes after flashing a custom ROM your going to have to do a factory reset from within twrp
Sent from my Nexus 6 using XDA-Developers mobile app
holeindalip said:
If you can use twrp just download a custom ROM to your phone and move it over to SD card and flash it, then you will be able to boot and unlock the bootloader in developer ootions, that is your best bet, if you keep getting force closes after flashing a custom ROM your going to have to do a factory reset from within twrp
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
I don't have an SD card, can I move it to the internal storage? And how exactly do I do this? I can't copy/paste anything into the phone (it says the phone doesn't actually exist, even though adb is recognizing it as in recovery) or do I sideload it? When I try to sideload it though, the device disappears (and device manager sees nexus 6 under other devices, but the driver isn't up to date and no drivers seem to work. I've tried the google usb driver with no luck.) and it won't allow me to sideload it.
Hey everyone
Not sure if anyone can help
I just got some used 5th gen tablets, they were in a storage unit i just purchased. I turned on one of the fire units and it says it was a kids fire, so no real use to me. I hit power to standby and left it in my office, went back to list it and it was updated with new software. The second one, seems like it is stuck in a boot loop, comes on and goes off again. So i looked at the one that updated, said it now updated, had 5.6 on it, so i said maybe i could use it. Did some research, read you can but just android on it.
Well, i read you have to downgrade to 5.3 or older to install android. Not even sure if this is right.
So i followed some youtube genius with software from rootjunky.
I used the adb to flash update-kindle-global-37.5.4.2_user_542168620.bin
Everything was working, installing 100%, then i unplugged and selected 1 from the tablet to reboot.
Needless to say, nothing comes on now, no logo, no nothing, will not respond to recovery mode, down and power.
I just tried taking the back off and unplugging the battery and holding power 20 secs, nothing.
Anyone have any ideas to salvage these, or one of them or are they paperweights haha?
Good news is, the unit had all kinds of stuff in it, i have made my money back already, these were just bonus
Any help would be great, thanks
vetteguy82 said:
Hey everyone
Not sure if anyone can help
I just got some used 5th gen tablets, they were in a storage unit i just purchased. I turned on one of the fire units and it says it was a kids fire, so no real use to me. I hit power to standby and left it in my office, went back to list it and it was updated with new software. The second one, seems like it is stuck in a boot loop, comes on and goes off again. So i looked at the one that updated, said it now updated, had 5.6 on it, so i said maybe i could use it. Did some research, read you can but just android on it.
Well, i read you have to downgrade to 5.3 or older to install android. Not even sure if this is right.
So i followed some youtube genius with software from rootjunky.
I used the adb to flash update-kindle-global-37.5.4.2_user_542168620.bin
Everything was working, installing 100%, then i unplugged and selected 1 from the tablet to reboot.
Needless to say, nothing comes on now, no logo, no nothing, will not respond to recovery mode, down and power.
I just tried taking the back off and unplugging the battery and holding power 20 secs, nothing.
Anyone have any ideas to salvage these, or one of them or are they paperweights haha?
Good news is, the unit had all kinds of stuff in it, i have made my money back already, these were just bonus
Any help would be great, thanks
Click to expand...
Click to collapse
Permanently bricked; can't downgrade below 5.4. Sell it for parts or take it to the target range.
Thanks
Thanks for the reply
Ok, so the one that will not turn on at all , well technically it must be on when i plug it into my pc, it does chime, and then a few seconds later it chimes again. Like it is turning itself on and off, but because you can not see anything on the screen, you can not tell.
What about the second one? It turns on and you see amazon, but then it turns itself off. It does let you go to fastboot and recovery in the corner of the screen using the buttons. However, all you see is that, recovery only says recovery, does not go into the recovery menu.
Any ideas if the second one is recoverable?
Thanks
vetteguy82 said:
Thanks for the reply
Ok, so the one that will not turn on at all , well technically it must be on when i plug it into my pc, it does chime, and then a few seconds later it chimes again. Like it is turning itself on and off, but because you can not see anything on the screen, you can not tell.
What about the second one? It turns on and you see amazon, but then it turns itself off. It does let you go to fastboot and recovery in the corner of the screen using the buttons. However, all you see is that, recovery only says recovery, does not go into the recovery menu.
Any ideas if the second one is recoverable?
Thanks
Click to expand...
Click to collapse
If you can not access the stock recovery menu there is no known method for recovering these devices with one exception: early build devices (bootloader version 5.00 & 5.01) can boot a twrp image from fastboot. If that works you'll be able to install a custom ROM (two choices) assuming nothing else is wrong with the hardware.
fastboot boot <twrp.img>
thanks
I must be doing something wrong again, i download the twrp.imga dn saved it in the fast boot adb folder. I put the kindle in fastboot mode, and plugged into pc, driver installed, from folder i went in to command prompt. in command prompt i added fastboot twrp.img and hit enter command prompt shows all the command prompts and definitions.
Is there something else i should do?
Thanks
Davey126 said:
If you can not access the stock recovery menu there is no known method for recovering these devices with one exception: early build devices (bootloader version 5.00 & 5.01) can boot a twrp image from fastboot. If that works you'll be able to install a custom ROM (two choices) assuming nothing else is wrong with the hardware.
fastboot boot <twrp.img>
Click to expand...
Click to collapse
vetteguy82 said:
I must be doing something wrong again, i download the twrp.imga dn saved it in the fast boot adb folder. I put the kindle in fastboot mode, and plugged into pc, driver installed, from folder i went in to command prompt. in command prompt i added fastboot twrp.img and hit enter command prompt shows all the command prompts and definitions.
Is there something else i should do?
Thanks
Click to expand...
Click to collapse
You need to install this tool on the host PC. Make note of the installation folder as you will need to execute the fastboot command from there. You'll also need to copy any necessary files (eg: twrp image) to that folder unless versed in referencing other folders from the command prompt.
Keep in mind it is highly unlikely your looping device will be able to boot twrp. Only the earliest models had this vulnerability which Amazon quickly plugged.
Crossposting from the Lineage 15 thread, as it may be a more general problem...
I installed lineage 15 a couple days ago.
I followed the OP, flashed the partition firmware first, then the ROM, TWRP, GAPPS, rebooted, flashed Magisk. Everything was working fine.
I took the 0210 nightly OTA. Google Play Services and all Google apps stopped working.
I figured I'd start fresh through fastboot, but now any command that would actually help (flash, boot, etc) returns "failed: unknown command". Can't boot into TWRP.
"fastboot devices" returns the device ID fine, fastboot reboot works.
Tried a factory reset based off another post I found, still in the same boat.
Any ideas?
Horror Business said:
Crossposting from the Lineage 15 thread, as it may be a more general problem...
I installed lineage 15 a couple days ago.
I followed the OP, flashed the partition firmware first, then the ROM, TWRP, GAPPS, rebooted, flashed Magisk. Everything was working fine.
I took the 0210 nightly OTA. Google Play Services and all Google apps stopped working.
I figured I'd start fresh through fastboot, but now any command that would actually help (flash, boot, etc) returns "failed: unknown command". Can't boot into TWRP.
"fastboot devices" returns the device ID fine, fastboot reboot works.
Tried a factory reset based off another post I found, still in the same boat.
Any ideas?
Click to expand...
Click to collapse
What happened is that you messed up the installation order.
https://forum.xda-developers.com/showpost.php?p=78037053&postcount=685
You only use the zip and rom before the restart and then Gapps and Magisk after.
If nothing else works, then I'd suggest flash stock and start from step one.
The factory reset only, normally, only clears the data partition.
Your bootloader and system partitions are bad as TWRP is written to the bootloader and Gapps installs to the system.
Don't quote me on the bad bootloader though; worst case, you'll want a blankflash and flash stock before starting over again.
[EDIT]
I may have alleviated worst case scenario, read the bottom: https://forum.xda-developers.com/showpost.php?p=78046198&postcount=692
dougo007 said:
What happened is that you messed up the installation order.
https://forum.xda-developers.com/showpost.php?p=78037053&postcount=685
You only use the zip and rom before the restart and then Gapps and Magisk after.
If nothing else works, then I'd suggest flash stock and start from step one.
The factory reset only, normally, only clears the data partition.
Your bootloader and system partitions are bad as TWRP is written to the bootloader and Gapps installs to the system.
Don't quote me on the bad bootloader though; worst case, you'll want a blankflash and flash stock before starting over again.
[EDIT]
I may have alleviated worst case scenario, read the bottom: https://forum.xda-developers.com/showpost.php?p=78046198&postcount=692
Click to expand...
Click to collapse
I definitely got the installation order correct for the fresh install. I used the built-in updater in lineage to update the OS, so it's entirely possible that there's a slot issue related to that...
The firmware link at the bottom of your post was the very first thing I did.
A blankflash file I found that I think should be recent enough for my device just shows <waiting for device>. I ran ADB and it shows the device as connected, so I don't think it's a driver issue. I know nada about blankflash, though.
Researching now. Thanks for the help.
Horror Business said:
I definitely got the installation order correct for the fresh install. I used the built-in updater in lineage to update the OS, so it's entirely possible that there's a slot issue related to that...
The firmware link at the bottom of your post was the very first thing I did.
A blankflash file I found that I think should be recent enough for my device just shows <waiting for device>. I ran ADB and it shows the device as connected, so I don't think it's a driver issue. I know nada about blankflash, though.
Researching now. Thanks for the help.
Click to expand...
Click to collapse
I have a whole package I created with links to different XDA threads on this device, but I don't have it with me at the moment.
You will definitely need to know what variant you're using.
I found one for XT1900-1 and one for XT1900-7.
There is a phone button combo you'll need to use and good timing.
dougo007 said:
I have a whole package I created with links to different XDA threads on this device, but I don't have it with me at the moment.
You will definitely need to know what variant you're using.
I found one for XT1900-1 and one for XT1900-7.
There is a phone button combo you'll need to use and good timing.
Click to expand...
Click to collapse
I have XT1900-1.
Thanks!
Here is my 'data dump' from my text file on what to do in the worst case scenario; I grabbed and linked what I could together below.
Don't take the words as direct advice from me as I never did this myself before.
--------------------------------------------------------------------------------------------------------
Enter download Mode: Power & Volume - (down) for ten seconds [ or volume +]
blank flash (two different files, not sure which to use)
Generic Instructions:
https://www.droidsavvy.com/unbrick-qualcomm-mobiles/
Device Instructions:
https://forum.xda-developers.com/moto-x4/help/hard-bricked-how-enter-emergency-t3757472
https://forum.xda-developers.com/showpost.php?p=77847019&postcount=606
https://forum.xda-developers.com/showpost.php?p=77847374&postcount=44
https://www.aryk.tech/2017/09/moto-x4-unbrick-solutions.html
use qualcomm driver first with blank flash
MAY NEED TO ENTER PC INTO TEST MODE:
Make your PC into Test Mode.
Then run “CMD” or “Windows Terminal” as administrator and type:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
(Restart computer)
***When you no longer need it.***
###To deactivate it we will use the following command.###
Bcdedit.exe -set loadoptions ENABLE_INTEGRITY_CHECKS
Bcdedit.exe -set TESTSIGNING OFF
Once the two commands have been executed, we must restart our computer so that the changes take effect and this mode is deactivated correctly.
If process completed successful then your mobile will restart into bootloader screen and your hard brick problem has been resolved. after that you can reboot into recovery by pressing power and volume down button again if required. Once you are in recovery mode then you can flash correct stock ROM into your mobile.
use manual and brick help to load system partition
ROMS: https://androidfilehost.com/?a=show&w=files&flid=229118
Data upload
There is one more file too big or here mentioned in the PDF.
I don't know which ROM is the best to use but you should use a PAYTON_FI for the XT1900-1
dougo007 said:
Data upload
There is one more file too big or here mentioned in the PDF.
Click to expand...
Click to collapse
Massive, massive thanks, man!
Got me rolling back to being able to flash a stock rom, which is good enough for me on this device!
I'm still guessing that slots jacked something up, but I'm not going to try to replicate the problem at this point, LOL!
One last note.
I noticed that flashing stock doesn't make the device genuine.
It appears that a trick I used to use on my old device works here; rooting with Magisk will mark the phone as certified.
To make sure this is the case, install the manager and if there is one RED and one GREEN; you're good to go on the install.
[EDIT]
Also, you can remove the unlocked bootloader warning with a patched image; I don't know if these two things will conflict though.
[EDIT 2]
I also don't know if either will conflict with OTA updates, assuming they work after you fixed your phone.
You can let me know below if you can provide any useful data.
If you have any other questions, make another post/thread. @Horror_Business
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.