Related
I've been trying to update my HOX to JB since yesterday but to no avail:
Im on everything stock (ROM, Recovery etc) and phone is un-rooted. I relocked the bootloader too. but when the update downloads and the phone restarts after a few while, a red triangle with exclamation marks appear and phone restarts.
I've tried to do this 3 times now with no avail.
alternately i've been trying to follow this and when i reach the flashing firmware part, it fails after 2 tries and after the 3rd it just stucks:
C:\fastboot>fastboot flash zip firmware.zip
sending 'zip' (12875 KB)...
OKAY [ 1.683s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 1.886s
C:\fastboot>fastboot flash zip firmware.zip
sending 'zip' (12875 KB)...
FAILED (remote: (00000008))
finished. total time: 0.001s
C:\fastboot>fastboot flash zip firmware.zip
sending 'zip' (12875 KB)...
after 3rd attempt it just stays in sending 'zip' state
anyone got a clue how i can solve either problem?! :/
note my camera app is a modified version. rest all ROM is stock. could this be the issue?! if so, then any way to resolve this other than RUU method?
The last method you tried will not work if the bootloader is still locked !
The red triangle is normally an indication that you do not have the stock recovery. Try to reflash recovery and then fastboot erase cache before trying again, You would need to unlock bootloader in order to fastboot flash recovery. As pointed out in my other reply to you, you would probably need to revert to the stock camera app as well.
Using the fastboot flash zip method, you need to have a locked bootloader and then enter command fastboot oem rebootRUU before running the fastboot flash zip command.
Ah like that ! Thanks clyde :thumbup:
I did not read carefully... was kinda busy with my mac & cheese !!!
MarcelHofs said:
Ah like that ! Thanks clyde :thumbup:
I did not read carefully... was kinda busy with my mac & cheese !!!
Click to expand...
Click to collapse
ClydeB1 said:
Click to expand...
Click to collapse
LOL !
ClydeB1 said:
The red triangle is normally an indication that you do not have the stock recovery. Try to reflash recovery and then fastboot erase cache before trying again, You would need to unlock bootloader in order to fastboot flash recovery. As pointed out in my other reply to you, you would probably need to revert to the stock camera app as well.
Using the fastboot flash zip method, you need to have a locked bootloader and then enter command fastboot oem rebootRUU before running the fastboot flash zip command.
Click to expand...
Click to collapse
thanks, will try the OTA method 1st by installing the RUU. if that works then brilliant! otherwise try the 2nd
ClydeB1 said:
Using the fastboot flash zip method, you need to have a locked bootloader and then enter command fastboot oem rebootRUU before running the fastboot flash zip command.
Click to expand...
Click to collapse
worked like a charm, thnx mate! :good:
Didnt work for me
Asad_612 said:
worked like a charm, thnx mate! :good:
Click to expand...
Click to collapse
I get to the rebootRUU step and that works, but when I try to flash the firmware.zip it always comes up with "error: cannot load "fastboot.zip" : Unknown error" do you know what the problem might be?
mewazhere said:
I get to the rebootRUU step and that works, but when I try to flash the firmware.zip it always comes up with "error: cannot load "fastboot.zip" : Unknown error" do you know what the problem might be?
Click to expand...
Click to collapse
Fastboot.zip ..... Yeah that's wrong
Fastboot flash zip firmware.zip
And the firmware file need to be named firmware.zip !
Hi all
I have the HTC ONE X International TEGRA 3 version.
Could do with some help.
I've updated HBOOT to 1.28 and when i try to install aokp_ICJ422-V2.9.5.zip in recovery this is what i get:
updating partition details...
installing '/sdcard/0/roms/aokp_ICJ422-V2.9.5.zip'...
checking for md5 file...
skipping md5 check: no md5 file found.
assert failed: getprop("ro.bootloader") == "1.28.0000" ||
E:error in 'sdcard/0/roms/aokp_ICJ422-V2.9.5.zip'
updating partition details...
Then it says Failed underneath
This is using Team Win Recovery Project v2.4.1.0
Any help is appreciated
AFAIK it should work on 1.28 hboot but it seems that LorD made a slight mistake while writing the updater script...
Is there any way you could update the hboot even further?
Sent from my IceCold One X
TToivanen said:
AFAIK it should work on 1.28 hboot but it seems that LorD made a slight mistake while writing the updater script...
Is there any way you could update the hboot even further?
Sent from my IceCold One X
Click to expand...
Click to collapse
I dont think i can as it was what was on the htc dev website and i just use the identifier token thats shown in cmd prompt
Ahem, hboot version has nothing to do with either htcdev or identifier token.
Please do:
fastboot oem readcid
And post the result here.
Sent from my IceCold One X
TToivanen said:
Ahem, hboot version has nothing to do with either htcdev or identifier token.
Please do:
fastboot oem readcid
And post the result here.
Sent from my IceCold One X
Click to expand...
Click to collapse
INFODEBUG: cid: HTC__001
You can go up to 1.39. Please stand by for instructions.
Download this: http://goo.gl/M0hLq
Rename it "firmware" if it isn't already named so. Copy it to the fastboot folder.
Put your Unlock_code.bin to your fastboot folder (search email inbox if you've lost it)
Then do the commands one by one:
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip firmware.zip (do several times if it fails)
fastboot flash unlocktoken Unlock_code.bin
Then flash the recovery of your choice and proceed.
jaymz_uk said:
INFODEBUG: cid: HTC__001
Click to expand...
Click to collapse
just checked in recovery and it still says HBOOT-1.12.0000 even though ive done " fastboot flash unlocktoken Unlock_code.bin
So as it stands i have bootloader and recovery but no OS.
Thanks for the help usually i can install rom's fine as i was using the 4.2.1 AOKP rom
Ive done what you said hboot is still 1.12.0000
firmware.zip keeps saying failed remote not allowed and remote 000000008.
still failing on writing zip
TToivanen said:
You can go up to 1.39. Please stand by for instructions.
Download this: http://goo.gl/M0hLq
Rename it "firmware" if it isn't already named so. Copy it to the fastboot folder.
Put your Unlock_code.bin to your fastboot folder (search email inbox if you've lost it)
Then do the commands one by one:
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip firmware.zip (do several times if it fails)
fastboot flash unlocktoken Unlock_code.bin
Then flash the recovery of your choice and proceed.
Click to expand...
Click to collapse
Will it write the zip file if its relocked?
jaymz_uk said:
Will it write the zip file if its relocked?
Click to expand...
Click to collapse
Still not working can someone help me get this sorted as i need my phone.
jaymz_uk said:
Will it write the zip file if its relocked?
Click to expand...
Click to collapse
It MUST be relocked in order to flash.
Sent from my IceCold One X
TToivanen said:
It MUST be relocked in order to flash.
Sent from my IceCold One X
Click to expand...
Click to collapse
well it keeps saying failed when trying to write. Should i just keep trying it?
jaymz_uk said:
well it keeps saying failed when trying to write. Should i just keep trying it?
Click to expand...
Click to collapse
It should flash fine after 2-3 tries.
Sent from my IceCold One X
TToivanen said:
It should flash fine after 2-3 tries.
Sent from my IceCold One X
Click to expand...
Click to collapse
for some reason it keeps saying failed when writing and then it just says waiting for device for ages
Does it have to be s-off as mines s-on
jaymz_uk said:
for some reason it keeps saying failed when writing and then it just says waiting for device for ages
Does it have to be s-off as mines s-on
Click to expand...
Click to collapse
Also rebooting the RUU is it supposed to show the word htc then go to something or do i reboot
jaymz_uk said:
Also rebooting the RUU is it supposed to show the word htc then go to something or do i reboot
Click to expand...
Click to collapse
Ok it worked turned phone off waited a couple of minutes then tried it all again and it worked. Just got to try the rom now will post back if all worked.
Thanks
All sorted and working just got to set it up. your a life save thanks for the help.
Great! Enjoy that masterpiece of a ROM.
Sent from my IceCold One X
any one can help me to get my phone to stoke ????
i am new in this so pleas help me step by step
thank you
oneabdo said:
any one can help me to get my phone to stoke ????
i am new in this so pleas help me step by step
thank you
Click to expand...
Click to collapse
Here, This should help you
http://forum.xda-developers.com/showthread.php?t=1592355
oneabdo said:
any one can help me to get my phone to stoke ????
i am new in this so pleas help me step by step
thank you
Click to expand...
Click to collapse
Post the result of "fastboot getvar version-main" just to be sure about the base...
vipul0309 said:
Here, This should help you
http://forum.xda-developers.com/showthread.php?t=1592355
Click to expand...
Click to collapse
He wants to get back to stock, not install a Custom ROM...
Oops mistake
Sent from my HTC One X
---------- Post added at 03:30 PM ---------- Previous post was at 03:24 PM ----------
http://forum.xda-developers.com/showthread.php?t=1832891
Scroll down to reverting to stock and you shall find it
my htc spftwer number is 2.18.751.7
i have been try RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_TW_3.14.709.20_Radio_5.1204.162.29_release_292865_signed.exe
and it give me error 159
oneabdo said:
my htc spftwer number is 2.18.751.7
i have been try RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_TW_3.14.709.20_Radio_5.1204.162.29_release_292865_signed.exe
and it give me error 159
Click to expand...
Click to collapse
I'm not talking about the software number of bootloader...
Do as I told and post the result of
Code:
fastboot getvar version-main
Then we can find a correct RUU for your device or a nandroid backup!
vin4yak said:
I'm not talking about the software number of bootloader...
Do as I told and post the result of
Code:
fastboot getvar version-main
Then we can find a correct RUU for your device or a nandroid backup!
Click to expand...
Click to collapse
version-main: 2.18.751.7
oneabdo said:
version-main: 2.18.751.7
Click to expand...
Click to collapse
Ohk! Your CID is CID HTC__621??
Cross check by doing this command:
Code:
fastboot getvar cid
Post back result... I think you will need to first upgrade your firmware and then restore the a nandroid backup...
There's no RUU available for you, can't find a nandroid backup as well...
vin4yak said:
Ohk! Your CID is CID HTC__621??
Cross check by doing this command:
Code:
fastboot getvar cid
Post back result... I think you will need to first upgrade your firmware and then restore the a nandroid backup...
There's no RUU available for you, can't find a nandroid backup as well...
Click to expand...
Click to collapse
yes my cid is 621
how to upgrade my firmware and then restore the a nandroid backup??
thank you
Download this firmware : http://www.androidrevolution.nl/downloader/download.php?file=3.14.709.20.zip and then rename it to firmware.zip and put it in your
relock your bootloader by:
Code:
fastboot oem lock
Now flash the zip:
Code:
fastboot flash zip firmware.zip
You might have to do it a few times to get it successfully!
vin4yak said:
Download this firmware : http://www.androidrevolution.nl/downloader/download.php?file=3.14.709.20.zip and then rename it to firmware.zip and put it in your
relock your bootloader by:
Code:
fastboot oem lock
Now flash the zip:
Code:
fastboot flash zip firmware.zip
You might have to do it a few times to get it successfully!
Click to expand...
Click to collapse
i have this
error: cannot load 'firmware.zip'
oneabdo said:
i have this
error: cannot load 'firmware.zip'
Click to expand...
Click to collapse
Have you put the firmware.zip into fastboot folder? is your phone in fastboot USB mode while connection to PC and running the command??
vin4yak said:
Have you put the firmware.zip into fastboot folder? is your phone in fastboot USB mode while connection to PC and running the command??
Click to expand...
Click to collapse
yes i put it on computer folder of fastboot folder and my phone it was relocked and in fastboot usb mode
oneabdo said:
yes i put it on computer folder of fastboot folder and my phone it was relocked and in fastboot usb mode
Click to expand...
Click to collapse
Ohkk Go to fastboot mode and then run the following command:
Code:
fastboot oem rebootRUU
and then run this:
fastboot flash zip firmware.zip
Flash it 2-3 times until you get a successful message!
vin4yak said:
Ohkk Go to fastboot mode and then run the following command:
Code:
fastboot oem rebootRUU
and then run this:
fastboot flash zip firmware.zip
Flash it 2-3 times until you get a successful message!
Click to expand...
Click to collapse
is it take long time ???
now sending !!!
oneabdo said:
is it take long time ???
now sending !!!
Click to expand...
Click to collapse
Didn't get you... what sending?
When you do rebootRUU, it will take you to Black HTC Screen... wait for few seconds and then flash the firmware.zip...
if you get an error,, then again flash the firmware zip 2-3 times till you get a successful message...
vin4yak said:
Didn't get you... what sending?
When you do rebootRUU, it will take you to Black HTC Screen... wait for few seconds and then flash the firmware.zip...
if you get an error,, then again flash the firmware zip 2-3 times till you get a successful message...
Click to expand...
Click to collapse
it dostn work it stay in sending 'zip' (12869 KB)...
oneabdo said:
it dostn work it stay in sending 'zip' (12869 KB)...
Click to expand...
Click to collapse
It means connection is lost between the phone and PC...
using latest HTC Sync manager and SDK?
Download this fastboot folder and try again : http://d-h.st/8Jr
Make sure you have sufficient amount of battery as well.
vin4yak said:
It means connection is lost between the phone and PC...
using latest HTC Sync manager and SDK?
Download this fastboot folder and try again : http://d-h.st/8Jr
Make sure you have sufficient amount of battery as well.
Click to expand...
Click to collapse
this is what i got
...
(bootloader) Save data from original MSC...
(bootloader) Save data from SIF...
(bootloader) Update partition data to SIF partition
(bootloader) Update partition data from original MSC...
(bootloader) [MSG] OKAY
OKAY [ 0.221s]
finished. total time: 0.221s
C:\Users\abdourrahem\Desktop\fastboot_2\fastboot>fastboot flash zip firmware.zi
sending 'zip' (12869 KB)...
OKAY [ 1.672s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
FAILED (remote: 99 unknown fail)
finished. total time: 2.294s
C:\Users\abdourrahem\Desktop\fastboot_2\fastboot>fastboot flash zip firmware.zi
sending 'zip' (12869 KB)...
FAILED (remote: (00030003))
finished. total time: 0.002s
C:\Users\abdourrahem\Desktop\fastboot_2\fastboot>fastboot flash zip firmware.zi
sending 'zip' (12869 KB)...
Edit : wrong thread !
Edit :
I see everywhere you write fasboot flash zip firmware.zi
Its firmware.zip
Don't know if you typed it wrong here or on the pc
All know is I can only boot into Fastboot Mode and Stock Recovery mode, but every way I try to get the flash the stock rom or TWRP won't work.
Device state is unlocked.
Reinstalled Google Drivers.
I will use taimen-opm1.171019.013-factory-6d9954c3
Android Debug Bridge version 1.0.32
Revision eac51f2bb6a8-android
fastboot version eac51f2bb6a8-android
Unified Android Toolkit:
Booting TWRP recovery-twrp-3.2.1.0-taimen.img ..
downloading 'boot.img'...
FAILED (remote: unknown command)
finished. total time: 0.007s
Click to expand...
Click to collapse
Cannot flash TWRP
PS C:\adb> fastboot devices
711KPVH0902199 fastboot
PS C:\adb> fastboot flash recovery twrp.img
sending 'recovery' (40960 KB)...
FAILED (remote: Requested download size is more than max allowed)
finished. total time: 0.009s
Click to expand...
Click to collapse
ADB sideload
PS C:\adb> adb sideload C:\taimen\taimen-opm1.171019.013-factory-6d9954c3.zip
loading: 'C:\taimen\taimen-opm1.171019.013-factory-6d9954c3.zip'
* cannot read 'C:\taimen\taimen-opm1.171019.013-factory-6d9954c3.zip' *
Click to expand...
Click to collapse
If I use flash-all.bat:
sending 'bootloader' (36344 KB)...
FAILED (unknown status code)
finished. total time: 343.328s.
Click to expand...
Click to collapse
If I use flash-all command in cmd:
PS C:\Users\tiger\Desktop\tamien> flash-all
error: cannot load 'bootloader-taimen-tmz10n.img'
rebooting into bootloader...
FAILED (remote: unknown command)
finished. total time: 0.007s
error: cannot load 'radio-taimen-g8998-00122-1708311414.img'
rebooting into bootloader...
FAILED (remote: unknown command)
finished. total time: 0.007s
W/ ( 9820): Unable to open 'image-taimen-opd1.170816.025.zip': No such file or directory
error: failed to open zip file 'image-taimen-opd1.170816.025.zip': I/O Error
Click to expand...
Click to collapse
Do you have the latest adb downloaded from Google?
Also, there is no recovery partition any longer, it's built in to the boot partition.
You can try the command "fastboot boot TWRP.img" to boot to TWRP.
azntiger said:
All know is I can only boot into Fastboot Mode and Stock Recovery mode, but every way I try to get the flash the stock rom or TWRP won't work. Device state is unlocked.
Unified Android Toolkit:
Cannot flash TWRP
ADB sideload
If I use flash-all.bat:
If I use flash-all command in cmd:
Click to expand...
Click to collapse
First, have you read this? https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Second, are your SDK platform-tools up to date??
Have you taken an OTA?
Your twrp command is wrong like the post after yours stated.
Did you give both bootloader unlock commands?
fastboot flashing unlock
And
fastboot flashing unlock_critical
ilal2ielli said:
Do you have the latest are downloaded from Google?
Also, there is no recovery partition any longer, it's built in to the boot partition.
You can try the command "fastboot boot TWRP.img" to boot to TWRP.
Click to expand...
Click to collapse
Yes. I reinstalled Google Drivers. I'm using taimen-opd1.170816.025-factory-907c4030.
I tried boot twrp.img, but it just hangs during the downloading boot.img.
PS C:\adb> fastboot devices
711KPVH0902199 fastboot
PS C:\adb> fastboot boot twrp.img
downloading 'boot.img'...
Click to expand...
Click to collapse
azntiger said:
Yes. I reinstalled Google Drivers. I'm using taimen-opd1.170816.025-factory-907c4030.
I tried boot twrp.img, but it just hangs during the downloading boot.img.
Click to expand...
Click to collapse
Why are you trying to flash the November build?
Badger50 said:
Why are you trying to flash the November build?
Click to expand...
Click to collapse
8.1 causes my proximity sensor to malfunction. The screen wouldn't turn on back on after a call. Alway-on didn't work because it thought the proximity sensor was blocked.
azntiger said:
8.1 causes my proximity sensor to malfunction. The screen wouldn't turn on back on after a call. Alway-on didn't work because it thought the proximity sensor was blocked.
Click to expand...
Click to collapse
That's a phone app problem. Either uninstall the phone app update, or find the phone app 16.0 on apk mirror. However, if you want to downgrade, look here.
https://www.google.com/amp/s/forum....-2-xl/help/downgrade-8-1-to-8-0-t3726641/amp/
Badger50 said:
That's a phone app problem. Either uninstall the phone app update, or find the phone app 16.0 on apk mirror. However, if you want to downgrade, look here.
https://www.google.com/amp/s/forum....-2-xl/help/downgrade-8-1-to-8-0-t3726641/amp/
Click to expand...
Click to collapse
I'll take a look if I can get my phone working again lol.
Badger50 said:
First, have you read this? https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Second, are your SDK platform-tools up to date??
Have you taken an OTA?
Your twrp command is wrong like the post after yours stated.
Did you give both bootloader unlock commands?
fastboot flashing unlock
And
fastboot flashing unlock_critical
Click to expand...
Click to collapse
SDK is up to date.
Not sure what you mean by "taken" an OTA.
So now I have a device null, but fastboot devices is seen.
"fastboot flashing unlock" hangs, but I imagine that's because no device was found?
PS C:\Users\tiger\Desktop\Pixel> fastboot devices
711KPVH0902199 fastboot
PS C:\Users\tiger\Desktop\Pixel> adb reboot bootloader
adb server is out of date. killing...
* daemon started successfully *
error: device '(null)' not found
PS C:\Users\tiger\Desktop\Pixel> fastboot flashing unlock
...
Click to expand...
Click to collapse
azntiger said:
I'll take a look if I can get my phone working again lol.
SDK is up to date.
Not sure what you mean by "taken" an OTA.
So now I have a device null, but fastboot devices is seen.
"fastboot flashing unlock" hangs, but I imagine that's because no device was found?
Click to expand...
Click to collapse
You may have to use this to get back on track my friend.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
I'm not entirely sure what the issue is (it could be a couple of things), but here are some issues that I see to help you troubleshoot:
1. Adb commands don't work in bootloader mode, only fastboot commands, which is why your device is visible to fastboot and not adb.
2. The file that you tried to adb sideload was a factory image, not an OTA. Adb sideload can only be used with OTA images. And even if you were using an OTA image, OTA images cannot be used to downgrade to a previous firmware version.
3. The latest version of adb is 1.0.39. You are using an older version. That fact itself doesn't really matter since adb will not help you in this situation, but fastboot will and if your adb is obsolete, I'd be willing to bet that your fastboot is too. Pixel 2 support was added in the October 2017 release of adb and fastboot. If yours is older than that, you're gonna have a bad time.
4. "Unable to open 'image-taimen-opd1.170816.025.zip': No such file or directory." Fastboot can't find your firmware files. Try placing the entire contents of the factory image, including the .zip file listed here, into the same directory as fastboot.exe (based on your post, it seems like the folder you want is C:\adb). Then rerun flash-all.bat. The script is assuming that fastboot.exe and all of the firmware files are in the same folder and if they're not, that could be a problem.
5. You do not have driver issues. The fact that fastboot devices worked means that your drivers/connection are/is working fine.
PS: Get the latest adb and fastboot here: https://developer.android.com/studio/releases/platform-tools.html
UPDATE: I did a Google search for adb/fastboot version eac51f2bb6a8-android. I found a reference to it in a forum post dated mid-2016. There's your problem. Or one of them, anyway. If you do adb --version or fastboot --version on the latest releases, they will tell you that they are version 0.0.1-4500957.
TheSt33v said:
4. "Unable to open 'image-taimen-opd1.170816.025.zip': No such file or directory." Fastboot can't find your firmware files. Try placing the entire contents of the factory image, including the .zip file listed here, into the same directory as fastboot.exe (based on your post, it seems like the folder you want is C:\adb). Then rerun flash-all.bat. The script is assuming that fastboot.exe and all of the firmware files are in the same folder and if they're not, that could be a problem.
Click to expand...
Click to collapse
I updated adb and fastboot:
Android Debug Bridge version 1.0.39
fastboot version 0.0.1-4500957
All of taimen-opm1.171019.013-factory-6d9954c3 & all contents of image-taimen-opm1.171019.013.zip were placed into C:\adb which has the adb and fastboot. After running flash-all.bat, this is what I got:
Code:
target didn't report max-download-size
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.008s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.007s
target didn't report max-download-size
sending 'radio' (60428 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.008s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.005s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (40 MB) to disk... took 0.395s
target didn't report max-download-size
error: Failed to identify current slot
Press any key to exit...
azntiger said:
I updated adb and fastboot:
Android Debug Bridge version 1.0.39
fastboot version 0.0.1-4500957
All of taimen-opm1.171019.013-factory-6d9954c3 & all contents of image-taimen-opm1.171019.013.zip were placed into C:\adb which has the adb and fastboot. After running flash-all.bat, this is what I got:
Click to expand...
Click to collapse
Open up your SDK and look for a file named "platform-tools" that is where all your files should be placed.
Badger50 said:
Open up your SDK and look for a file named "platform-tools" that is where all your files should be placed.
Click to expand...
Click to collapse
All the platform-tools and the stock rom are together in folder.
azntiger said:
All the platform-tools and the stock rom are together in folder.
Click to expand...
Click to collapse
Did you extract the factory image first, or just put the whole zip file in platform-tools?
azntiger said:
I updated adb and fastboot:
Android Debug Bridge version 1.0.39
fastboot version 0.0.1-4500957
All of taimen-opm1.171019.013-factory-6d9954c3 & all contents of image-taimen-opm1.171019.013.zip were placed into C:\adb which has the adb and fastboot. After running flash-all.bat, this is what I got:
Code:
target didn't report max-download-size
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.008s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.007s
target didn't report max-download-size
sending 'radio' (60428 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.008s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.005s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (40 MB) to disk... took 0.395s
target didn't report max-download-size
error: Failed to identify current slot
Press any key to exit...
Click to expand...
Click to collapse
Hmm. Fastboot is definitely having issues communicating with your phone. "Failed to identify current slot" is a bad sign. If I were you, I would try flashing the most recent factory image (not the November 8.0 image you're trying to flash) first just to see if you can get everything up to date again and clear out any mismatched files that may have been flashed during your attempts. Once you manage that, then try to downgrade. If you can, try a different computer too, preferably one with a type C input that you can use the stock USB cable with.
---------- Post added at 04:03 PM ---------- Previous post was at 04:01 PM ----------
Badger50 said:
Did you extract the factory image first, or just put the whole zip file in platform-tools?
Click to expand...
Click to collapse
The fact that he's not getting "not found" errors means that all the expected files are found by fastboot.
The fact that he's not getting "not found" errors means that all the expected files are found by fastboot.[/QUOTE]
Thanks man. I learned something new today :good:
Wonder if his transfer cable. I've seen that cause headaches as well ?
It was definitely an issue between my laptop and my phone. I was able to easily use flash-all.bat on a different computer.
I really appreciate both of your help! I was stressed out.
azntiger said:
It was definitely an issue between my laptop and my phone. I was able to easily use flash-all.bat on a different computer.
I really appreciate both of your help! I was stressed out.
Click to expand...
Click to collapse
Oh nice! Glad you got it figured out. This stuff can be a bit tricky at times. I know I've lost some hair from pulling it out when things didn't go right! ?
azntiger said:
It was definitely an issue between my laptop and my phone. I was able to easily use flash-all.bat on a different computer.
I really appreciate both of your help! I was stressed out.
Click to expand...
Click to collapse
I was on edge just reading this! I would also look into Deuce's script. It can save the 'device can't boot' issue once and for good.
Kudos on not having a faulty device~!
Hello i am writing here the very first time.
This is what happened :
I unlocked the bootloader.
Downloaded Twrp for Honor 7x from xda
Tried to flash it using ADB but it showed this :
C:\android-sdk-windows platform-tools>fastboot flash recovery twrp_Honor_7x.img
target reported max download size of 471859200 bytes
sending 'recovery' (25158 KB)...
OKAY [ 0.9695)
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 1.000s
Please someone help, and if possible provide me a link to the working twrp img
Thanks
If you're on oreo, the partition names have changed.
Use this command instead:
fastboot flash recovery_ramdisk twrpname.img
TWRP for oreo: https://forum.xda-developers.com/devdb/project/dl/?id=28883
crayonicle said:
If you're on oreo, the partition names have changed.
Use this command instead:
fastboot flash recovery_ramdisk twrpname.img
Click to expand...
Click to collapse
Okk let me check using this command and thanks for replying I will let you know in a bit
MeChiku said:
Okk let me check using this command and thanks for replying I will let you know in a bit
Click to expand...
Click to collapse
I also attached the link for a working TWRP for oreo, don't go flashing the nougat TWRP on oreo lol
crayonicle said:
I also attached the link for a working TWRP for oreo, don't go flashing the nougat TWRP on oreo lol
Click to expand...
Click to collapse
Thank you so much dear?
crayonicle said:
I also attached the link for a working TWRP for oreo, don't go flashing the nougat TWRP on oreo lol
Click to expand...
Click to collapse
Thanks a ton bro Twrp Installed Successfully, Please can you suggest the best treble rom for honor 7x i am looking for DOT OS or Lineage