Related
I am looking to download the stock recovery for version 4.20.651.10.
I've found the zip of all previous recoveries here: http://forum.xda-developers.com/showpost.php?p=56557802&postcount=84
Is there a place I can download the stock recovery for 4.20.651.10. I need that recovery so I can download the update just released, 4.25.651.14 as I run stock with root and my current recovery is TWRP. The older recoveries are not allowing the update to run.
ReproOne said:
I am looking to download the stock recovery for version 4.20.651.10.
I've found the zip of all previous recoveries here: http://forum.xda-developers.com/showpost.php?p=56557802&postcount=84
Is there a place I can download the stock recovery for 4.20.651.10. I need that recovery so I can download the update just released, 4.25.651.14 as I run stock with root and my current recovery is TWRP. The older recoveries are not allowing the update to run.
Click to expand...
Click to collapse
I extracted the recovery from 4.25.651.14 and flashed it. The update applied, but upon final restart it locked up and currently it will not start. I can force it to reboot, I get the startup screen for a few seconds, then it goes to a blank screen.
Any ideas?
ReproOne said:
I extracted the recovery from 4.25.651.14 and flashed it. The update applied, but upon final restart it locked up and currently it will not start. I can force it to reboot, I get the startup screen for a few seconds, then it goes to a blank screen.
Any ideas?
Click to expand...
Click to collapse
Either flash a custom recovery again from fastboot or RUU. Are you still unlocked bootloader? If not and you modified any system files, that would be why it will not boot.
Unlock your bootloader and it might boot with stock recovery. Otherwise RUU is the way to go, then you can take the OTA, unlock the boot, install custom recovery and root and do whatever you want from there.
Also, stock recovery is not required for RUU but you must lock the bootloader if you are s-on, not sure about s-off but if youi are and try, if it fails just lock it and try again.
dopy25 said:
Either flash a custom recovery again from fastboot or RUU. Are you still unlocked bootloader? If not and you modified any system files, that would be why it will not boot.
Unlock your bootloader and it might boot with stock recovery. Otherwise RUU is the way to go, then you can take the OTA, unlock the boot, install custom recovery and root and do whatever you want from there.
Also, stock recovery is not required for RUU but you must lock the bootloader if you are s-on, not sure about s-off but if youi are and try, if it fails just lock it and try again.
Click to expand...
Click to collapse
It will not boot to fastboot, just the splash screen then blank. Is there a way around this?
ReproOne said:
It will not boot to fastboot, just the splash screen then blank. Is there a way around this?
Click to expand...
Click to collapse
Have you tried to boot into the bootloader and then using the volume keys to navigate to "fastboot" and pressing power?
S-ON or S-OFF? If you are S-ON you should have the super security still and would have almost no possibility of a brick and should still be able to boot into the bootloader, if you can at least get there you are still in a (semi) working device and only takes a few things to do to get back to fully functional.
dopy25 said:
Have you tried to boot into the bootloader and then using the volume keys to navigate to "fastboot" and pressing power?
S-ON or S-OFF? If you are S-ON you should have the super security still and would have almost no possibility of a brick and should still be able to boot into the bootloader, if you can at least get there you are still in a (semi) working device and only takes a few things to do to get back to fully functional.
Click to expand...
Click to collapse
I am s-on, it is only HTC unlocked so I can have root access. So far, I cannot get it to boot to the boot loader via power and volume down.
ReproOne said:
I am s-on, it is only HTC unlocked so I can have root access. So far, I cannot get it to boot to the boot loader via power and volume down.
Click to expand...
Click to collapse
That's odd, all you did was unlock using HTC dev?
Are you charged to enough battery power? That could be a huge factor.
dopy25 said:
That's odd, all you did was unlock using HTC dev?
Are you charged to enough battery power? That could be a huge factor.
Click to expand...
Click to collapse
Yes unlock with HTCDev and then root. Phone charge 91%.
To get to the bootloader while having a bootloop : Hold Power + VolUp + VolDown until screen turns off. Then ... IMMEDIATELY release Power and volume UP, and keep hold of volume Down.
ReproOne said:
I am s-on, it is only HTC unlocked so I can have root access. So far, I cannot get it to boot to the boot loader via power and volume down.
Click to expand...
Click to collapse
Fastboot reboot-bootloader
From your PC...just throwing it out there it might work.
BTW I have only seen the HK firmware posted 4.25.654.14 but I wouldn't think it would flash at all since you are s-on.
BD619 said:
Fastboot reboot-bootloader
From your PC...just throwing it out there it might work.
BTW I have only seen the HK firmware posted 4.25.654.14 but I wouldn't think it would flash at all since you are s-on.
Click to expand...
Click to collapse
I can now get it to the recovery screen, so what can I do from adb to possibly redo the update?
ReproOne said:
I can now get it to the recovery screen, so what can I do from adb to possibly redo the update?
Click to expand...
Click to collapse
You will have to wait for someone to upload the non HK firmware...I'm in the process of pulling the OTA and pulling the firmware right now.
I'll post a link when I'm done.
BD619 said:
You will have to wait for someone to upload the non HK firmware...I'm in the process of pulling the OTA and pulling the firmware right now.
I'll post a link when I'm done.
Click to expand...
Click to collapse
I will wait for your reply. I did find this, but it fails:
http://forum.xda-developers.com/showthread.php?t=2729173
ReproOne said:
I will wait for your reply. I did find this, but it fails:
http://forum.xda-developers.com/showthread.php?t=2729173
Click to expand...
Click to collapse
Fails how?
BD619 said:
Fails how?
Click to expand...
Click to collapse
I downloaded "0P6BIMG_Sprint_HTC_One_M8_4.20.651.10_RUU.zip" and renamed to 0P6BIMG.ZIP to my computer (not sdcard)
I then did the following:
fastboot oem rebootRUU
fastboot flash zip 0P6BIMG.ZIP
and I get this...
target reported max download size of 1826418688 bytes
sending 'zip' (1502254 KB)...
OKAY [ 48.930s]
writing 'zip'...
(bootloader) zip header checking...
FAILED (remote: 32 header error)
finished. total time: 51.090s
If I run the flash zip a second time it gives this...
target reported max download size of 1504755712 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 33557229 is not a multiple of th
e block size 4096
sending sparse 'zip' (1469484 KB)...
error: write_sparse_skip_chunk: don't care size 33557229 is not a multiple of th
e block size 4096
error: write_sparse_skip_chunk: don't care size 33557229 is not a multiple of th
e block size 4096
OKAY [ 49.480s]
writing 'zip'...
(bootloader) zip header checking...
FAILED (remote: 32 header error)
finished. total time: 49.620s
ReproOne said:
I downloaded "0P6BIMG_Sprint_HTC_One_M8_4.20.651.10_RUU.zip" and renamed to 0P6BIMG.ZIP to my computer (not sdcard)
I then did the following:
fastboot oem rebootRUU
fastboot flash zip 0P6BIMG.ZIP
and I get this...
target reported max download size of 1826418688 bytes
sending 'zip' (1502254 KB)...
OKAY [ 48.930s]
writing 'zip'...
(bootloader) zip header checking...
FAILED (remote: 32 header error)
finished. total time: 51.090s
If I run the flash zip a second time it gives this...
target reported max download size of 1504755712 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 33557229 is not a multiple of th
e block size 4096
sending sparse 'zip' (1469484 KB)...
error: write_sparse_skip_chunk: don't care size 33557229 is not a multiple of th
e block size 4096
error: write_sparse_skip_chunk: don't care size 33557229 is not a multiple of th
e block size 4096
OKAY [ 49.480s]
writing 'zip'...
(bootloader) zip header checking...
FAILED (remote: 32 header error)
finished. total time: 49.620s
Click to expand...
Click to collapse
You have to be S-OFF I believe to use that method.
Here is the Full Firmware 4.25.651.14
https://www.androidfilehost.com/?fid=95916177934552553
Use these instructions
-rename firmware to firmware.zip
-copy firmware.zip to your sdk folder
-boot into bootloader
-plug in usb
-select fastboot option (screen should say fastboot usb)
-type fastboot oem rebootRUU
-when u see the black screen w/ HTC, type fastboot flash zip firmware.zip
-when it's done, type fastboot reboot
I would relock bootloader run 4.20 ruu take 4.25 ota then unlock bootloader flash twrp then root.
Sent from 27.5244° N, 99.4906° W
BD619 said:
You have to be S-OFF I believe to use that method.
Here is the Full Firmware 4.25.651.14
https://www.androidfilehost.com/?fid=95916177934552553
Use these instructions
-rename firmware to firmware.zip
-copy firmware.zip to your sdk folder
-boot into bootloader
-plug in usb
-select fastboot option (screen should say fastboot usb)
-type fastboot oem rebootRUU
-when u see the black screen w/ HTC, type fastboot flash zip firmware.zip
-when it's done, type fastboot reboot
Click to expand...
Click to collapse
The file does not appear to be there, possibly still uploading?
ReproOne said:
The file does not appear to be there, possibly still uploading?
Click to expand...
Click to collapse
My bad I deleted it lol I will upload again
BD619 said:
My bad I deleted it lol I will upload again
Click to expand...
Click to collapse
Thanks. Can't give you a hard time as you are helping me!
Waiting for upload...
Hey,guys! I uesd fastboot to flash system,but it failed
code:
target max-sparse-size: 256MB
sending 'system' (256598 KB)...
OKAY [ 8.040s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 18.249s
anyone can help me please?
YOUNG MAN. said:
Hey,guys! I uesd fastboot to flash system,but it failed
code:
target max-sparse-size: 256MB
sending 'system' (256598 KB)...
OKAY [ 8.040s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 18.249s
anyone can help me please?
Click to expand...
Click to collapse
Try to use the mfastboot, because the system.img is to big to use the normal fastboot
libnijunior said:
Try to use the mfastboot, because the system.img is to big to use the normal fastboot
Click to expand...
Click to collapse
it failed too
code
target reported max download size of 536870912 bytes
sending 'system' (256089 KB)...
OKAY [ 8.035s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 13.062s
and sometimes it shows
target reported max download size of 536870912 bytes
sending 'system' (256598 KB)...
OKAY [ 8.046s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 13.224s
YOUNG MAN. said:
it failed too
code
target reported max download size of 536870912 bytes
sending 'system' (256089 KB)...
OKAY [ 8.035s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 13.062s
and sometimes it shows
target reported max download size of 536870912 bytes
sending 'system' (256598 KB)...
OKAY [ 8.046s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 13.224s
Click to expand...
Click to collapse
What version of boot loader do you have? If you already flashed the boot loader of 5.0.2 and you are trying to flash older system images that error appears.
juliospinoza said:
What version of boot loader do you have? If you already flashed the boot loader of 5.0.2 and you are trying to flash older system images that error appears.
Click to expand...
Click to collapse
I Just bought this phone yesterday and it was 5.0 when i got it. Then i updated to 5.1 and the BL version is 60.14 now . I tried to back to 5.0 so it showed this error.
Do you have any way to solve this problem? My phone is bootloop now.
Thanx
YOUNG MAN. said:
I Just bought this phone yesterday and it was 5.0 when i got it. Then i updated to 5.1 and the BL version is 60.14 now . I tried to back to 5.0 so it showed this error.
Do you have any way to solve this problem? My phone is bootloop now.
Thanx
Click to expand...
Click to collapse
you really shouldn't downgrade unless you know what you are doing.
Is the bootloader unlocked? Can you get into bootloader mode?
JulesJam said:
you really shouldn't downgrade unless you know what you are doing.
Is the bootloader unlocked? Can you get into bootloader mode?
Click to expand...
Click to collapse
Yes,it is unlocked and i can get into fastboot mode .Is that bootlodader mode?
YOUNG MAN. said:
Yes,it is unlocked and i can get into fastboot mode .Is that bootlodader mode?
Click to expand...
Click to collapse
Yes, they are synonyms. I would install Motorola Device Manager to your PC and let it attempt to repair your phone.
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
If it doesn't repair your phone, post back here.
YOUNG MAN. said:
Yes,it is unlocked and i can get into fastboot mode .Is that bootlodader mode?
Click to expand...
Click to collapse
I installed Motorola Device Manager, what should i do next?
JulesJam said:
you really shouldn't downgrade unless you know what you are doing.
Is the bootloader unlocked? Can you get into bootloader mode?
Click to expand...
Click to collapse
I installed Motorola Device Manager and tried again, it still did't work.
code:
C:\Users\Alan\Desktop\ccc>fastboot flash system F:\XT1095\system.img_sparsechunk
.0
target max-sparse-size: 256MB
sending 'system' (256598 KB)...
OKAY [ 8.047s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 13.217s
YOUNG MAN. said:
I installed Motorola Device Manager and tried again, it still did't work.
Click to expand...
Click to collapse
Did it detect your device at all? Did it try to repair it?
YOUNG MAN. said:
C:\Users\Alan\Desktop\ccc>fastboot flash system F:\XT1095\system.img_sparsechunk
.0
target max-sparse-size: 256MB
sending 'system' (256598 KB)...
OKAY [ 8.047s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 13.217s
Click to expand...
Click to collapse
If you are only trying to flash small sparsechunks, have you tried flashing using the latest version of fastboot from Root Junky's site?
http://rootjunkysdl.com/?device=Adb Fastboot Files
Go into developer options and enable OEM unlocking. Then try it.
Edit: Forgot you said you were bootlooped. Can you install the 5.1 image again?
Sent from my XT1095
JulesJam said:
Did it detect your device at all? Did it try to repair it?
If you are only trying to flash small sparsechunks, have you tried flashing using the latest version of fastboot from Root Junky's site?
Click to expand...
Click to collapse
NO,It not detect my phone,it just search new software when i open it.
And I tried the latest version of fastboot,still failed
YOUNG MAN. said:
NO,It not detect my phone,it just search new software when i open it.
And I tried the latest version of fastboot,still failed
Click to expand...
Click to collapse
Did you try RSDLite?
JulesJam said:
Did you try RSDLite?
Click to expand...
Click to collapse
it can't detect my phone
YOUNG MAN. said:
it can't detect my phone
Click to expand...
Click to collapse
When you are in recovery, what does
adb devices
show you? Of course when you open the cmd window you have to navigate to a folder where adb.exe and the other required files are stored in order to use adb commands.
JulesJam said:
When you are in recovery, what does
adb devices
show you? Of course when you open the cmd window you have to navigate to a folder where adb.exe and the other required files are stored in order to use adb commands.
Click to expand...
Click to collapse
it shows View attachment 3294009
but in fastboot mode it shows View attachment 3294012
and my recovery is TWRP 2.8.60
YOUNG MAN. said:
it shows View attachment 3294009
but in fastboot mode it shows View attachment 3294012
and my recovery is TWRP 2.8.60
Click to expand...
Click to collapse
No I mean, connect your phone to your PC when you are in TWRP. Then open a command window. Then navigate to where adb.exe is stored - i.e, at the command prompt type in cd c:\[fill in the directory where adb.exe is stored]
then when you are at the proper directory, at the command prompt in the command window type:
adb devices
then hit enter.
It should return the serial number of your device.
JulesJam said:
No I mean, connect your phone to your PC when you are in TWRP. Then open a command window. Then navigate to where adb.exe is stored - i.e, at the command prompt type in cd c:\[fill in the directory where adb.exe is stored]
then when you are at the proper directory, at the command prompt in the command window type:
adb devices
then hit enter.
It should return the serial number of your device.
Click to expand...
Click to collapse
it shows this:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
device
dustin_b said:
Go into developer options and enable OEM unlocking. Then try it.
Edit: Forgot you said you were bootlooped. Can you install the 5.1 image again?
Sent from my XT1095
Click to expand...
Click to collapse
NO,my recovery is TWRP now ,and I can't flash the original recovery ,it failed.
I can not enter a normal download mode ( to reflash) the P8 lite. So the only way now( I think ) is to use a fastboot mode ( That is the only that works. now) But fastboot &rescue mode screen says PHONE LOCKED.
I already use a minimal ADB and fastboot application but do not know what to do next
Can anyone give me a clue how to continue?
Thanks
Written using Google Translate.
Is it not possible to install the original version of the Huawei software from the microSD memory card using the dload folder and a combination of three buttons?
All information contained in the phone will be lost!
Wysłane z Mi A1
I do not know how to flash files there. The combination of three buttons does not work only fastboot mode but when I try to flash an image I will get the following error.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot BOOT.img
target reported max download size of 471859200 bytes
sending 'boot' (22672 KB)...
OKAY [ 0.742s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.772s
Does it mean the Phone is locked? Or a developer mode not enabled?
Jane11 said:
I do not know how to flash files there. The combination of three buttons does not work only fastboot mode but when I try to flash an image I will get the following error.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot BOOT.img
target reported max download size of 471859200 bytes
sending 'boot' (22672 KB)...
OKAY [ 0.742s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.772s
Does it mean the Phone is locked? Or a developer mode not enabled?
Click to expand...
Click to collapse
Enter fastboot mode and try to use Hi suite, hope it helps.
The 3 button combo, try to press all of them, when phone boots release power button but continue pressing volume one's.
Also don't forget to have the firmware update.app in dload folder on the root of sdcard.
Icone24 said:
Enter fastboot mode and try to use Hi suite, hope it helps.
The 3 button combo, try to press all of them, when phone boots release power button but continue pressing volume one's.
Also don't forget to have the firmware update.app in dload folder on the root of sdcard.
Click to expand...
Click to collapse
HiSuite says that Device is not connected even though the mobile is in fastboot mode and command fastboot devices lists the mobile as connected.
What now? Thanks
Jane11 said:
HiSuite says that Device is not connected even though the mobile is in fastboot mode and command fastboot devices lists the mobile as connected.
What now? Thanks
Click to expand...
Click to collapse
Try the combo way like i wrote. If it doesn't work i don't know how to help you.
anyone seen this before?
Sending 'bootloader_a' (8761 KB) OKAY [ 0.321s]
Writing 'bootloader_a' FAILED (remote: 'error getting device locked state No Response')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.045s]
Finished. Total time: 0.053s
< waiting for any device >
Sending 'radio_a' (82676 KB) OKAY [ 2.098s]
Writing 'radio_a' FAILED (remote: 'error getting device locked state No Response')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.036s]
Finished. Total time: 0.155s
< waiting for any device >
--------------------------------------------
Bootloader Version...: c2f2-0.2-5940465
Baseband Version.....: unknown
Serial Number........: 98011FFC4004AN
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' FAILED
Device product is 'unknown'.
Update requires 'flame' or 'coral'.
fastboot: error: requirements not met!
Press any key to exit...
thatotherguy.. said:
anyone seen this before?
Sending 'bootloader_a' (8761 KB) OKAY [ 0.321s]
Writing 'bootloader_a' FAILED (remote: 'error getting device locked state No Response')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.045s]
Finished. Total time: 0.053s
< waiting for any device >
Sending 'radio_a' (82676 KB) OKAY [ 2.098s]
Writing 'radio_a' FAILED (remote: 'error getting device locked state No Response')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.036s]
Finished. Total time: 0.155s
< waiting for any device >
--------------------------------------------
Bootloader Version...: c2f2-0.2-5940465
Baseband Version.....: unknown
Serial Number........: 98011FFC4004AN
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' FAILED
Device product is 'unknown'.
Update requires 'flame' or 'coral'.
fastboot: error: requirements not met!
Press any key to exit...
Click to expand...
Click to collapse
Is this the first time this has happened?
Fastboot up to date?
Are you using power shell?
Tried USB A to USB C cables and different USB ports?
Did you extract the factory image and place all the contents in the platform-tools folder?
Device drivers are up to date?
Did you see your phone ID # when you typed in "fastboot devices"?
Badger50 said:
:
Click to expand...
Click to collapse
Is this the first time this has happened? someone was trying to flash stock before
Fastboot up to date? Yes it is, I just flashed another phone just fine before this one
Are you using power shell? no I am using cmd
Tried USB A to USB C cables and different USB ports? yes I have
Did you extract the factory image and place all the contents in the platform-tools folder? yes
Device drivers are up to date? yes they are
Did you see your phone ID # when you typed in "fastboot devices"? yes it show up, but it no picture show on screen even though the pc see it
thatotherguy.. said:
Is this the first time this has happened? someone was trying to flash stock before
Fastboot up to date? Yes it is, I just flashed another phone just fine before this one
Are you using power shell? no I am using cmd
Tried USB A to USB C cables and different USB ports? yes I have
Did you extract the factory image and place all the contents in the platform-tools folder? yes
Device drivers are up to date? yes they are
Did you see your phone ID # when you typed in "fastboot devices"? yes it show up, but it no picture show on screen even though the pc see it
Click to expand...
Click to collapse
Are you sure the bootloader is unlocked?
Badger50 said:
Are you sure the bootloader is unlocked?
Click to expand...
Click to collapse
I'm not 100% sure of that, the other phone they have it was unlocked. but this one doesn't show baseband as unknown
thatotherguy.. said:
anyone seen this before?
Sending 'bootloader_a' (8761 KB) OKAY [ 0.321s]
Writing 'bootloader_a' FAILED (remote: 'error getting device locked state No Response')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.045s]
Finished. Total time: 0.053s
< waiting for any device >
Sending 'radio_a' (82676 KB) OKAY [ 2.098s]
Writing 'radio_a' FAILED (remote: 'error getting device locked state No Response')
Click to expand...
Click to collapse
thatotherguy.. said:
I'm not 100% sure of that, the other phone they have it was unlocked. but this one doesn't show baseband as unknown
Click to expand...
Click to collapse
Judging from all the "getting device locked state" warnings your getting, I'd say it's still locked.
Badger50 said:
Judging from all the "getting device locked state" warnings your getting, I'd say it's still locked.
Click to expand...
Click to collapse
guessing pretty it done for?
thatotherguy.. said:
guessing pretty it done for?
Click to expand...
Click to collapse
Huh?? If you want to unlock it, make sure OEM unlocking and USB debugging is turned on in developer options. Then go back into fastboot mode and run..fastboot flashing unlock..
This WILL wipe your device :good:
Badger50 said:
Huh?? If you want to unlock it, make sure OEM unlocking and USB debugging is turned on in developer options. Then go back into fastboot mode and run..fastboot flashing unlock..
This WILL wipe your device :good:
Click to expand...
Click to collapse
I've tried unlocked bootloader, give same error
Sent from my Pixel 4 XL using Tapatalk
thatotherguy.. said:
I've tried unlocked bootloader, give same error
Click to expand...
Click to collapse
Then, maybe you have a carrier bootloader locked device??
My attempt to install a custom rom has failed horribly and I'm left with a wiped phone. Is there a way to reinstall EMUI? Or still somehow get a custom rom?
I flashed lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bvS.img on system, but although there was no error message it didn't seem to do anything.
It's a LLD-L31
hasl3r said:
Is there a way to reinstall EMUI?
Click to expand...
Click to collapse
Maybe, in fastboot mode run commands :
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Some might fail, so don't worry about it.
If you want to flash GSI custom ROM , look here or here .
(ANE and LLD are basically identical devices).
Btw, I'm running LOS 19.0 by Andy Yan on ANE-LX1, works like a charm...
-Alf- said:
Maybe, in fastboot mode run commands :
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Some might fail, so don't worry about it.
If you want to flash GSI custom ROM , look here or here .
(ANE and LLD are basically identical devices).
Btw, I'm running LOS 19.0 by Andy Yan on ANE-LX1, works like a charm...
Click to expand...
Click to collapse
I don't seem able to get into fastboot anymore, only TWRP 3.2.1-0 boots. The menu "Reboot - Fastboot" leads back to TWRP and running "adb reboot fastboot" from console as well.
hasl3r said:
I don't seem able to get into fastboot anymore, only TWRP 3.2.1-0 boots. The menu "Reboot - Fastboot" leads back to TWRP and running "adb reboot fastboot" from console as well.
Click to expand...
Click to collapse
- Try the following: turn off your phone, press and hold Volume Down and connect phone to PC.
- Can you boot into eRecovery? (turn off, connect to PC and press and hold Power & Vol Up). If so, try to update phone via Wifi and option "Download latest....".
hasl3r said:
The menu "Reboot - Fastboot" leads back to TWRP and running "adb reboot fastboot" from console as well.
Click to expand...
Click to collapse
Do you have TWRP installed instead of Recovery or eRecovery?
hasl3r said:
It's a LLD-L31
Click to expand...
Click to collapse
What is your regional variant? (Cxxx)
-Alf- said:
- Try the following: turn off your phone, press and hold Volume Down and connect phone to PC.
Click to expand...
Click to collapse
That worked, I'm not around a PC at the moment, I'll run the commands as soon as possible
-Alf- said:
- Can you boot into eRecovery? (turn off, connect to PC and press and hold Power & Vol Up). If so, try to update phone via Wifi and option "Download latest....".
Do you have TWRP installed instead of Recovery or eRecovery?
Click to expand...
Click to collapse
That booted into TWRP as well, so I guess?
-Alf- said:
What is your regional variant? (Cxxx)
Click to expand...
Click to collapse
How to I find that out? I tried google but didn't find information.
All else I got are the IMEI and:
Serial number: FPM4C18622002338
Product ID: 71171281
Many thanks already for your help btw
hasl3r said:
How to I find that out?
Click to expand...
Click to collapse
through the mentioned fastboot commands.
-Alf- said:
through the mentioned fastboot commands.
Click to expand...
Click to collapse
>> fastboot oem get-build-number
(bootloader) :LLD-L31 9.1.0.189(C432E10R1P4)
>> fastboot oem get-product-model
(bootloader) LLD-L31
>> fastboot getvar vendorcountry
vendorcountry: hw/eu
>> fastboot oem oeminforead-CUSTOM_VERSION
(bootloader) :LLD-L31-CUST 9.1.0.10(C432)
>> fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :LLD-L31 9.1.0.117(C432E4R1P3)
hasl3r said:
>> fastboot oem get-build-number
(bootloader) :LLD-L31 9.1.0.189(C432E10R1P4)
>> fastboot oem get-product-model
(bootloader) LLD-L31
>> fastboot getvar vendorcountry
vendorcountry: hw/eu
>> fastboot oem oeminforead-CUSTOM_VERSION
(bootloader) :LLD-L31-CUST 9.1.0.10(C432)
>> fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :LLD-L31 9.1.0.117(C432E4R1P3)
Click to expand...
Click to collapse
Okay, try the following:
1. Download Service ROM
Unpack it, there's a dload file in Software folder. Copy dload as it is to the SD Card (without unpacking it!)
2. Download TWRP 3.2.1 https://mega.nz/#!tkcTlATI!A8UJGPBGtxJbLcUOJoxCGJj5PFZXzCnjbb3OkwqKTP8
and copy it to SD Card
3. also copy to SD stock Recovery_ramdisk-9.1.img , download here:
https://mega.nz/#!M0FHlYhb!4yWz8Onr3D1NATel4mZSK4SNdd5B3p6dnPg6oXPGWl8
4. Boot into your TWRP, select storage - SD Card, select "Install image", find TWRP-9.1 file and mark eRecovery, swipe. Go back, find recovery_ramdisk-9.1 file , mark Recovery, swipe.
5.Turn off the phone, use option 'Power Off' in TWRP's menu.
6. Press and hold Power & both Volume buttons .
-Alf- said:
Okay, try the following:
Click to expand...
Click to collapse
Amazing, thank you so much!
-Alf- said:
If you want to flash GSI custom ROM , look here or here .
(ANE and LLD are basically identical devices).
Btw, I'm running LOS 19.0 by Andy Yan on ANE-LX1, works like a charm...
Click to expand...
Click to collapse
Having the phone running again gave me hope, so I'll try to flash LineageOS 17.1 tomorrow.
hasl3r said:
Amazing, thank you so much!
Having the phone running again gave me hope, so I'll try to flash LineageOS 17.1 tomorrow.
Click to expand...
Click to collapse
Glad to help
-Alf- said:
Glad to help
Click to expand...
Click to collapse
Sorry to bother you again, just wondering if you have any advice. I tried flashing LineageOS 17.1, but realised that the bootloader is locked again. My unlock code doesn't seem to work anymore (check password failed) and I figured it's because I have to downgrade EMUI 9.1 to 8.0. Took me a while, but turns out that was not the issue.
Do you happen to have any idea what to try? Do I have to buy another DC Unlocker license?
I don't know if it's related, but "adb reboot fastboot" just reboots the device and I have to use the volume down key to get there.
hasl3r said:
the bootloader is locked again.
Click to expand...
Click to collapse
it's normal after using dload method
hasl3r said:
My unlock code doesn't seem to work anymore
Click to expand...
Click to collapse
Unlock code is permanent. Is OEM unlocking turned on in Developer options? (FRP unlock on fastboot screen?)
-Alf- said:
Unlock code is permanent. Is OEM unlocking turned on in Developer options? (FRP unlock on fastboot screen?)
Click to expand...
Click to collapse
Turns out the problem was copy/pasting the unlock code instead of hand typing it..
So I could flash it, but then the reset failed. Just realised that EMUI 9.1 is a requirement though, so I'll flash that first and try again.
Edit: Nvm fixed it. Sorry if you got a notification anyway.
-Alf- said:
If you want to flash GSI custom ROM , look here or here .
(ANE and LLD are basically identical devices).
Btw, I'm running LOS 19.0 by Andy Yan on ANE-LX1, works like a charm...
Click to expand...
Click to collapse
Hmm I tried it with a clean stock 9.1 but flashing didn't work
If you have no ideas, I'll just stick with the stock installation.
Code:
>> fastboot flash system losq-v224-201017-arm64-bgN.img
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (460796 KB)...
OKAY [ 12.198s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 12.678s
Code:
>>fastboot flash system "caos-v315+220228-arm64-bgZ.img"
target reported max download size of 471859200 bytes
Invalid sparse file format at header magi
sending sparse 'system' 1/7 (460796 KB)...
OKAY [ 12.284s]
writing 'system' 1/7...
FAILED (remote: sparse flash write failure)
finished. total time: 12.730s
hasl3r said:
Hmm I tried it with a clean stock 9.1 but flashing didn't work
If you have no ideas, I'll just stick with the stock installation.
Code:
>> fastboot flash system losq-v224-201017-arm64-bgN.img
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (460796 KB)...
OKAY [ 12.198s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 12.678s
Code:
>>fastboot flash system "caos-v315+220228-arm64-bgZ.img"
target reported max download size of 471859200 bytes
Invalid sparse file format at header magi
sending sparse 'system' 1/7 (460796 KB)...
OKAY [ 12.284s]
writing 'system' 1/7...
FAILED (remote: sparse flash write failure)
finished. total time: 12.730s
Click to expand...
Click to collapse
1. be sure that your bootloader is unlocked, try to unlock it again
2. In fastboot mode run command
fastboot erase system
and try to flash GSI again
3. Install TWRP 3.2.1 gaguga edition, in TWRP select Mount - mark System, go back, select Wipe > Advanced > mark System > Repaire or etc. > Resize file system > confirm, reboot .
Then flash back stock recovery and try to install GSI.
4. Downgrade to the lower build number via dload method
5. idk...