Hi all, first of all, sorry for being a complete noob to all this.
I was wondering if I could have some help installing Cyanogen mod on my HTC sensation as I find the stock ROM to be far to slow and bloated.
I have downloaded KGS Utility for all rooting/ S off purposes, my main issue at the moment is unlocking the bootloader,
I have got a unlock token from HTCdev but when I try and flash it, I get the following error:
sending 'unlocktoken' (0 KB)...
OKAY [ 0.151s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.159s
I have followed all the instructions to the letter and tried multiple times.
Does anyone know what could be causing this. The device is definitely in bootloader USB mode with fastboot off and USB debugging enabled (though I have tried different combinations of these settings with no luck).
My next question is when it comes to flashing the ROM what order do I need to do everything. From what I can gather, once the bootloader is unlocked, I need to root, S-off and then install a new recovery in that order before flashing cyanogen. Is this correct?
Thanks for any help in advance.
Tom
there is no need to open a second thread
i answered you to the other one
It said the key was invalid, get another one and make sure you don't type it incorrectly
Sent from my Galaxy Nexus using xda app-developers app
Related
here's what i did so far
factory reset on clockworkmod
phone will no longer boot
find out only solution is to flash stock ruu through fastboot
right ruu for my hboot and carrier not available
i have roger001 and hboot 1.13 bought from canada fido
i find out i can supercid to install ruu's from other countries
supercid procedure requires me to gain access to sd
i cannot access it (usb debugging not enabled im guessing, a i cant enable it because phone stuck in bootloop)
so now i cannot supercid
so i can not install any ruu without errors
i somehow broke clockworkmod cant get into it either
i need a way to install an ruu by just using the adp fastboot usb
help.... im kind of desperate
Seriously? Not even a single reply? Does that mean that there's absolutely nothing I can do? Give me SOME feedback please.
Can't you just fastboot flash a recovery, boot said recovery, mount usb storage in recovery and put a rom, and then flash that rom? Probably should clear data and system before flashing...
Sent from my HTC One S using xda app
lampel said:
Can't you just fastboot flash a recovery, boot said recovery, mount usb storage in recovery and put a rom, and then flash that rom? Probably should clear data and system before flashing...
Sent from my HTC One S using xda app
Click to expand...
Click to collapse
what recovery should i fastboot? i'm looking for something other than CWM
I use twrp. Never had an issue with it.
Sent from my HTC One S using xda app
lampel said:
I use twrp. Never had an issue with it.
Sent from my HTC One S using xda app
Click to expand...
Click to collapse
hmm it won't let me....
when i type into command and prompt "fastboot flash recovery twrp.img"
i get the following:
sending 'recovery' (8288 KB)... OKAY [ 1.474s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.158s
it won't even let me flash twrp
In your picture your bootloader is relocked. Did you re-unlock it?
sushiemaker said:
hmm it won't let me....
when i type into command and prompt "fastboot flash recovery twrp.img"
i get the following:
sending 'recovery' (8288 KB)... OKAY [ 1.474s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.158s
it won't even let me flash twrp
Click to expand...
Click to collapse
lampel said:
In your picture your bootloader is relocked. Did you re-unlock it?
Click to expand...
Click to collapse
wow, thank you so much, I forgot to re-unlock it...
now I have managed to get twrp installed, and I'm at the mounting stage, but my computer gives me the following message:
"You need to format this disk before you can use it. Do you want to format it?" and there is a "Format" or "Cancel" button I can press.
Should I click Format? I didn't want to act too hasty.
edit: ok i formatted it, now im in the process of finding a rom, any suggestions?
Trickdroid and energy are both great if you like sense roms.
Sent from my HTC One S using xda app
Hi all,
Looking for some insight here. I have a second-hand Nexus S GT-I9020A that was replaced because it would no longer boot. I took on the challenge of trying to fix it. Based on the reading I've done so far it may have bad a bad NAND chip, but I'm too stubborn to give up on it just yet. Here are the symptoms:
When booting normally, it hangs on the Google screen with all 4 hardware buttons lit up.
Fastboot works, however I can't flash anything because its bootloader is locked, which brings me to my next point.
When issuing the command fastboot oem unlock, I am prompted with the familiar Yes/no screen but when selecting Yes, nothing seems to happen. I've left it for about 6-7 hours and came back to a message in my PC command window stating "Status read Failed (too many links)".
I can get into the stock recovery but that's really of no help at all. I can wipe cache partition without an issue but get an error when trying to wipe data/factory reset.
I've attempted the One-Click UnBrick software which I read somewhere is compatible with the Nexus S. It did recognize the phone, send a command, and give a success message. The phone rebooted but nothing changed.
So, this leaves me with nothing left to try but to post here. It seems that since I cannot even unlock the bootloader that my hands are tied. Are there any other tools that I should be aware of that can diagnose bad NAND flash? I don't want to toss the phone until I know I've tried everything I can to troubleshoot.
Any help is greatly appreciated. I tried to give as much detail about the problem as I could but if I left out any important info let me know.
Thanks!
Same issue
stevz34 said:
Hi all,
Looking for some insight here. I have a second-hand Nexus S GT-I9020A that was replaced because it would no longer boot. I took on the challenge of trying to fix it. Based on the reading I've done so far it may have bad a bad NAND chip, but I'm too stubborn to give up on it just yet. Here are the symptoms:
When booting normally, it hangs on the Google screen with all 4 hardware buttons lit up.
Fastboot works, however I can't flash anything because its bootloader is locked, which brings me to my next point.
When issuing the command fastboot oem unlock, I am prompted with the familiar Yes/no screen but when selecting Yes, nothing seems to happen. I've left it for about 6-7 hours and came back to a message in my PC command window stating "Status read Failed (too many links)".
I can get into the stock recovery but that's really of no help at all. I can wipe cache partition without an issue but get an error when trying to wipe data/factory reset.
I've attempted the One-Click UnBrick software which I read somewhere is compatible with the Nexus S. It did recognize the phone, send a command, and give a success message. The phone rebooted but nothing changed.
So, this leaves me with nothing left to try but to post here. It seems that since I cannot even unlock the bootloader that my hands are tied. Are there any other tools that I should be aware of that can diagnose bad NAND flash? I don't want to toss the phone until I know I've tried everything I can to troubleshoot.
Any help is greatly appreciated. I tried to give as much detail about the problem as I could but if I left out any important info let me know.
Thanks!
Click to expand...
Click to collapse
I have the same problem wit an I9020T for australia and would appreciate any advice available as well.
Send to samsung service
stevz34 said:
Hi all,
Looking for some insight here. I have a second-hand Nexus S GT-I9020A that was replaced because it would no longer boot. I took on the challenge of trying to fix it. Based on the reading I've done so far it may have bad a bad NAND chip, but I'm too stubborn to give up on it just yet. Here are the symptoms:
When booting normally, it hangs on the Google screen with all 4 hardware buttons lit up.
Fastboot works, however I can't flash anything because its bootloader is locked, which brings me to my next point.
When issuing the command fastboot oem unlock, I am prompted with the familiar Yes/no screen but when selecting Yes, nothing seems to happen. I've left it for about 6-7 hours and came back to a message in my PC command window stating "Status read Failed (too many links)".
I can get into the stock recovery but that's really of no help at all. I can wipe cache partition without an issue but get an error when trying to wipe data/factory reset.
I've attempted the One-Click UnBrick software which I read somewhere is compatible with the Nexus S. It did recognize the phone, send a command, and give a success message. The phone rebooted but nothing changed.
So, this leaves me with nothing left to try but to post here. It seems that since I cannot even unlock the bootloader that my hands are tied. Are there any other tools that I should be aware of that can diagnose bad NAND flash? I don't want to toss the phone until I know I've tried everything I can to troubleshoot.
Any help is greatly appreciated. I tried to give as much detail about the problem as I could but if I left out any important info let me know.
Thanks!
Click to expand...
Click to collapse
Try flashing the official Android 4.1.2 image from Google in fastboot. See if it boots... Then maybe you will have more luck unlocking it! I would also try to wipe as many thing as possible before doing it. Try system, data, boot, cache, dalvik... Even sdcard might help...
Dark_Eyes_ said:
Try flashing the official Android 4.1.2 image from Google in fastboot. See if it boots... Then maybe you will have more luck unlocking it! I would also try to wipe as many thing as possible before doing it. Try system, data, boot, cache, dalvik... Even sdcard might help...
Click to expand...
Click to collapse
Tried this but as said fastboot is not recognised by my pc. Have installed almost all the drivers I can find to no avail. Must be something else to try.
Spanner127 said:
Tried this but as said fastboot is not recognised by my pc. Have installed almost all the drivers I can find to no avail. Must be something else to try.
Click to expand...
Click to collapse
Well, you should be able to flash official Google images in stock recovery too... Have you tried that?
Dark_Eyes_ said:
Well, you should be able to flash official Google images in stock recovery too... Have you tried that?
Click to expand...
Click to collapse
mY COMPUTER ONLY RECOGNISES abd IN SIDELOAD MODE. tHE FASTBOOT ANYTHING IS NOT RECOGNISED SO i CANNOT UPDATE OR FIX anything. Thanks for trying.
Can you try doing all the stuff you did in some another PC.
Worth a try.
Dark_Eyes_ said:
Try flashing the official Android 4.1.2 image from Google in fastboot. See if it boots... Then maybe you will have more luck unlocking it! I would also try to wipe as many thing as possible before doing it. Try system, data, boot, cache, dalvik... Even sdcard might help...
Click to expand...
Click to collapse
Tried as suggested, received the following output:
C:\Users\Steven\Downloads\sojua-jzo54k>flash-all
sending 'bootloader' (1536 KB)...
OKAY [ 0.187s]
writing 'bootloader'...
FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 0.203s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
sending 'radio' (12288 KB)...
OKAY [ 1.543s]
writing 'radio'...
FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 1.543s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXKA3
Baseband Version.....: I9020UCKF1
Serial Number........: 33311A4C1F8500EC
--------------------------------------------
checking product...
OKAY [ 0.016s]
checking version-bootloader...
FAILED
Device version-bootloader is 'I9020XXKA3'.
Update requires 'I9020XXLC2'.
finished. total time: 0.016s
Press any key to exit...
It would seem that I can't flash anything, including official firmware, if the bootloader is locked?
On the plus side, the phone responds fine to the fastboot commands and seems to transfer the images to it just fine, just still no luck getting the darn bootloader unlocked
stevz34 said:
Tried as suggested, received the following output:
C:\Users\Steven\Downloads\sojua-jzo54k>flash-all
sending 'bootloader' (1536 KB)...
OKAY [ 0.187s]
writing 'bootloader'...
FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 0.203s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
sending 'radio' (12288 KB)...
OKAY [ 1.543s]
writing 'radio'...
FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 1.543s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXKA3
Baseband Version.....: I9020UCKF1
Serial Number........: 33311A4C1F8500EC
--------------------------------------------
checking product...
OKAY [ 0.016s]
checking version-bootloader...
FAILED
Device version-bootloader is 'I9020XXKA3'.
Update requires 'I9020XXLC2'.
finished. total time: 0.016s
Press any key to exit...
It would seem that I can't flash anything, including official firmware, if the bootloader is locked?
On the plus side, the phone responds fine to the fastboot commands and seems to transfer the images to it just fine, just still no luck getting the darn bootloader unlocked
Click to expand...
Click to collapse
Normally it is possible to flash official ota from Google even if the bootloader is locked. What version did you have prior to your problems? Try flashing the ota package that came just after your version as it seems that the package your are trying with cannot be flashed over the version that you have right now!
Dark_Eyes_ said:
Normally it is possible to flash official ota from Google even if the bootloader is locked. What version did you have prior to your problems? Try flashing the ota package that came just after your version as it seems that the package your are trying with cannot be flashed over the version that you have right now!
Click to expand...
Click to collapse
Currently the phone has 2.3.6. I tried flashing 4.0.4, which was the next one, and it failed with the same error, indicating I need to unlock my bootloader. Also tried flashing the 2.3.6 firmware, received the same error. I'm starting to think I should probably give up on this phone.
Any more suggestions?
stevz34 said:
Currently the phone has 2.3.6. I tried flashing 4.0.4, which was the next one, and it failed with the same error, indicating I need to unlock my bootloader. Also tried flashing the 2.3.6 firmware, received the same error. I'm starting to think I should probably give up on this phone.
Any more suggestions?
Click to expand...
Click to collapse
Did you try the OTA update from Google? That's weird cause I flashed it back then and I was on stock 2.3.6 with locked bootloader and stock recovery and it worked. Have you don't anything particular with your phone or is it pure stock 2.3.6? Start there
http://forum.xda-developers.com/showthread.php?t=1063664
Dark_Eyes_ said:
Did you try the OTA update from Google? That's weird cause I flashed it back then and I was on stock 2.3.6 with locked bootloader and stock recovery and it worked. Have you don't anything particular with your phone or is it pure stock 2.3.6? Start there
http://forum.xda-developers.com/showthread.php?t=1063664
Click to expand...
Click to collapse
Thanks for posting that link. Still no luck though. I tried the 2.3.6 (GRK39C) -> 2.3.6 (GRK39F) OTA file and the 2.3.6 (GRK39F) -> 4.0.4 one as I am not sure which version of 2.3.6 that I have. Basically I am trying to use fastboot to apply the OTA update using fastboot -w update filename.zip however it is failing with the following message:
C:\Users\Steven\Downloads>fastboot -w update d1be8195481a.signed-sojua-GRK39F-fr
om-GRK39C.d1be8195.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
C:\Users\Steven\Downloads>
The OTA updates indicate they can be flashed using stock recovery. However when I enter the recovery on the phone and select update from sdcard, I get the message indicating that it cannot mount /sdcard. Is there another way I should be doing this?
stevz34 said:
Thanks for posting that link. Still no luck though. I tried the 2.3.6 (GRK39C) -> 2.3.6 (GRK39F) OTA file and the 2.3.6 (GRK39F) -> 4.0.4 one as I am not sure which version of 2.3.6 that I have. Basically I am trying to use fastboot to apply the OTA update using fastboot -w update filename.zip however it is failing with the following message:
C:\Users\Steven\Downloads>fastboot -w update d1be8195481a.signed-sojua-GRK39F-fr
om-GRK39C.d1be8195.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
C:\Users\Steven\Downloads>
The OTA updates indicate they can be flashed using stock recovery. However when I enter the recovery on the phone and select update from sdcard, I get the message indicating that it cannot mount /sdcard. Is there another way I should be doing this?
Click to expand...
Click to collapse
You have to rename the file to update.zip and place it on /sdcard. It will install it automatically. Stock recovery won't install custom zip file so that's why you need to do that. Let me know if it works...
so my phone froze today so I took out battery and turned it on and all it does is go to the boot loader.
So I decide to try recovery all this does is flash android logos and then back to same screen,
Next I try factory reset and same flashes to android logos and back to same screen
After reading this forum
I then go through the process of unlocking my boot loader via htc dev the process goes great I receive email etc etc
The final process should bring up a disclaimer on my screen but nothing
So my question is wtf what do I do?
Please help me
Check the guide at HTC side if you have done everything correctly, all is written how it should or copy and paste.
Without unlocked bootloader, there is no chance to rescue your phone.
Any information about your phone model and exactly the step it fails is important, too.
this problem has such a friend, and it does not solve constantly locked bootloader ...
Does anyone solved this problem?The same situation of my phone?Please help!
Hi,
i flash 2.8.4.0twrp, then make backup, after that (whit in recovery options) try to make factory reset, and after that my one sv is messed up like hell...
It is not booting...stuck for a while at htc logo, screen goes black, then loads bootloader, I am able to go to twrp (I have fresh backup of complete phone, did it with twrp above), but not able to flash anything...it fails every time, saying that is unable to mount cache...try advance wipe, but it is not able to mount any thing...
Since my phone was S-off, unlocked bootloader, superCID (it is k2ul), hboot2.0, I tryed with fastboot oem relock (to lock bootloader, and flash stock pl80img.zip) but that fails too, ends up with to many links message...and bootloader stays with tampered and unlocked sign...before flashing 2.8.4.0twrp phone was working great, but after factory reset it is not able to mount anything, and running pl80img.zip gives me all so only fail...fail...fail...
So..now i have latest twrp and totaly messed up phone...
How can U help me, anny advice???
THX in advance!
danrock1984 said:
so my phone froze today so I took out battery and turned it on and all it does is go to the boot loader.
So I decide to try recovery all this does is flash android logos and then back to same screen,
Next I try factory reset and same flashes to android logos and back to same screen
After reading this forum
I then go through the process of unlocking my boot loader via htc dev the process goes great I receive email etc etc
The final process should bring up a disclaimer on my screen but nothing
So my question is wtf what do I do?
Please help me
Click to expand...
Click to collapse
I have the same problem!!
The phone details:
Locked Bootloader
K2_UL XA SHIP S-ON RL
HBOOT 2.00.0000
T-mobile network lock
NO SuperCID
The phone doesn't boot up!
It boot to bootloader fastboot mode always!
The notification led blinks constantly!
When I wanted run the RUU (K2_UL_ICS_EUROPE...etc) the phone doesn't reboot black HTC Screen it goes back to bootloader, and it doesn't working
After I downloaded this:
https://www.androidfilehost.com/?fid=23212708291675772
After I download it rename to PL80IMG.zip and it loading after checking, and goes back to bootloader, no volume up to update option!
After I downloaded OTA_K2_UL_JB_45_S_Voda-Hutch_AU_2.14.862.9-1.17.862.9_release_3136147vue6nb55rwgyw0d.zip
After I extracted the firmware zip from it, edited the android-info.txt CID number to HTC__032 and place it to SD, rename to PL80IMG.zip after I get the same problem!
After these problems are try another method with fastboot!
fastboot flash zip flash firmware zip and I got this:
C:\Users\Erkaft\Desktop\Új mappa>fastboot flash zip firmware.zip
sending 'zip' (33772 KB)...
OKAY [ 2.668s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 5.264s
C:\Users\Erkaft\Desktop\Új mappa>
And when i want to erase all with fastboot I got this:
C:\Users\Erkaft\Desktop\Új mappa>fastboot erase all
erasing 'all'...
FAILED (remote: not allowed)
finished. total time: 0.000s
C:\Users\Erkaft\Desktop\Új mappa>fastboot erase boot
erasing 'boot'...
FAILED (remote: not allowed)
finished. total time: -0.000s
C:\Users\Erkaft\Desktop\Új mappa>fastboot erase system
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: -0.000s
I also tried bootloader unlock but the last message didn't appear on the phone and it stay locked
Any idea to ressurection this phone?
You need ti unlock your phone,otherwise you can't do anything.
So 10 hours ago I decided I wanted to root my phone to install some apps and maybe even a cool ROM.
I read that the first step is to unlock the bootloader. I have trying my hardest to do this first step for 10 hours.
I've read 4-5 different tutorials twice on xda.
My phone is:
HTC One A9(hiae), bought in Sweden
hTc download mode
*** LOCKED ***
htc_hiaeuhl PVT S-ON
LK-1.0.0.000
[email protected]
OpenDSP-7.8.2.00197-8952_1228
OS-1.56.401.70
Jan 22 2016....
I have tried the normal way through htcdev.com even had the Unlock_code.bin at one point. But I had to reinstall all drivers twice to get it.
I have tried using the WinDroid Toolkit, no better than the manual way.
I got my hard earned token ID through both ways.
I find that every time I want to use fasstboot to send over a file i.e. "fastboot flash recovery twrp.img" hTc download mode is stuck at Start download, like I need to confirm it but can't because the command failed. The same goes for the Unlock_code.bin, can't send it over.
Code:
C:\adb>fastboot devices
HT5AVBE04449 fastboot
C:\adb>fastboot flash unlocktoken Unlock_code.bin
target didn't report max-download-size
sending 'unlocktoken' (0 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.003s
I can get past this next problem temporarily by reinstalling all drivers, tedious.
Code:
C:\adb>fastboot oem get_identifier_token
...
FAILED (command write failed (Unknown error))
finished. total time: 5.002s
Possible problems:
hTc download mode: I need to accept the download before fastboot give up, instant.
Win10: Bad OS for this?
USB connectors: Not enough power? Some other USB devices don't work here normally.
HTC Sync Manager: I've not bother installing the software.
Solution
I've made it;
I'm not sure if I was in the real download mode at the time, but that might have been it.
Also this time I redid everything, deleted all the drivers correctly and installed via Universal Naked Drivers
Hello,
Did you check OEM unlocking to allow the bootloader to be unlocked in Settings/Developper options (hidden by default, appears when you tap Build number 10x in Setting/About/ Software information/More/ Build number) ?
ouioui01 said:
Hello,
Did you check OEM unlocking to allow the bootloader to be unlocked in Settings/Developper options (hidden by default, appears when you tap Build number 10x in Setting/About/ Software information/More/ Build number) ?
Click to expand...
Click to collapse
For my phone it is 8 taps and yes. Every time I start a new Android I do a OEM unlock.
But I might be correct to change USB connector.
Dear people,
First of all, although dilligent and trying to do my homework, I am a total newbie regarding anything Android. Therefore, if I am posting on the wrong section of the site, please let me know and I will try my best to fix it.
That being said, I have a Moto G3 (Moto G 2015), model XT1543 (osprey), that is stuck in the fastboot boot. I have searched a lot of the web trying to find solutions and, after having failed all of them, decided to come here for assistance.
My device only boots and displays:
AP Fastboot Flash Mode (Secure)
version downgrade for recovery
failed to validate recovery image
ERROR: Failed to pass verification, backup to fastboot
Fastboot Reason: Fall-through from recovery boot mode
I already downloaded the appropriate TWRP recovery image for the device (osprey), but the bootloader is locked and, since I can't get into the system properly, I can't switch the "Unlock OEM boot" flag when the full system is running.
In particular, when I try to flash TWRP, this is what I get:
# fastboot flash recovery twrp-3.1.0-1-osprey.img
target reported max download size of 268435456 bytes
sending 'recovery' (7546 KB)...
OKAY [ 0.373s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.454s
Indeed, since I am only in fastboot mode, I went away and requested a boot unlock code from Motorola and trying to unlock the bootloader and this is what I get:
# fastboot oem unlock <my-code-here>
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.034s
I already tried looking at similar questions in many, many forums and no answer actually applied to my device (including, for example, https://forum.xda-developers.com/2015-moto-g/help/moto-g3-struck-fastboot-screen-t3542147 and even others for other models and vendors).
Thanks in advance for any help.
At this point your only option to flash the same or newer factory image through fastboot. The is no way to unlock the bootloader without the OEM unlock in developer options checked, and with a locked bootloader you can't flash an older version. See the thread on flashing factory images.
Sent from my MotoG3 using Tapatalk
riggerman0421 said:
At this point your only option to flash the same or newer factory image through fastboot. The is no way to unlock the bootloader without the OEM unlock in developer options checked, and with a locked bootloader you can't flash an older version. See the thread on flashing factory images.
Click to expand...
Click to collapse
OK. So, now, I know how to direct my energies and avoid useless efforts.
Thank you so very much, @riggerman0421. Now, to find which factory image was the one that was installed on this device (it is actually my father's device).
rtbrito said:
OK. So, now, I know how to direct my energies and avoid useless efforts.
Thank you so very much, @riggerman0421. Now, to find which factory image was the one that was installed on this device (it is actually my father's device).
Click to expand...
Click to collapse
You can follow the guide here. Try it with the latest firmware available here.
Broadcasted from Zeta Reticuli