Hey everyone!
I'm a long time reader, but never had the occasion to post until now. I have somewhat recently started tinkering with my phones. I'm a programmer by trade so I'm not at all seperated from technology, however, I fear I may have gotten myself into a but of a ?.
So, here's what I broke: I have a Verizon Wireless Pixel 2. A few weeks ago I read that there was a boot loader unlock for it. As such, I rebooted to the boot loader, ran the "fastboot flashing lock_critical" command. After being unlocked I then proceeded to flash TWRP and then Magisk Manager. All was well until my phone had an unrelated warranty issue. As such, I filed a claim, and got my new phone.
Today I was trying to recover my phone to factory and am getting a few errors. I downloaded this Image from Google "8.0.0 (OPD3.170816.023, Nov 2017, Verizon) - https://dl.google.com/dl/android/aosp/walleye-opd3.170816.023-factory-f269631e.zip"). I extracted it, and ran "flash_all.bat". Througout the process I get an error stating that it can't find a recovery.img. I looked in the .zip and found that to be true. I downloaded the standard stock .zip and noticed it doesn't have one either. In addition, when it gets to the part about flashing the system image I get the following error:
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
--------------------------------------------
Bootloader Version...: mw8998-002.0066.00
Baseband Version.....: g8998-00164-1710262031
Serial Number........: REMOVED
--------------------------------------------
checking product...
OKAY [ 0.000s]
checking version-bootloader...
OKAY [ 0.001s]
checking version-baseband...
OKAY [ -0.000s]
sending 'boot' (32768 KB)...
OKAY [ 0.744s]
writing 'boot'...
OKAY [ 0.000s]
sending sparse 'system' (524284 KB)...
OKAY [ 12.589s]
writing 'system'...
OKAY [ -0.000s]
sending sparse 'system' (524284 KB)...
FAILED (remote: No such partition.)
finished. total time: 13.631s
Anyone have any idea how to remedy this? I'm simply trying to get it back to stock. In addition, if I can get it returned to stock is relocking the bootloader even possible?
Thanks in advance for any help!
-Sofie
is your phone currently on 8.0.0 or have you been updated to at least 8.1?
you can't flash to a lower version than what you already have. i have verizon and i plan on flashing back to stock and you should be flashing to the 013 version from January.
iridium7777 said:
is your phone currently on 8.0.0 or have you been updated to at least 8.1?
you can't flash to a lower version than what you already have. i have verizon and i plan on flashing back to stock and you should be flashing to the 013 version from January.
Click to expand...
Click to collapse
It was on 8.1. Makes sense, I'll download the latest and try that. I just chose that because it says "VZW" in the name.
iridium7777 said:
is your phone currently on 8.0.0 or have you been updated to at least 8.1?
you can't flash to a lower version than what you already have. i have verizon and i plan on flashing back to stock and you should be flashing to the 013 version from January.
Click to expand...
Click to collapse
SweetSofie said:
It was on 8.1. Makes sense, I'll download the latest and try that. I just chose that because it says "VZW" in the name.
Click to expand...
Click to collapse
Well, that didn't help at all. :crying:
SweetSofie said:
Well, that didn't help at all. :crying:
Click to expand...
Click to collapse
try everything over and start clean:
1) delete all your stuff from your comp (all previous tools and images)
2) download the fresh set of latest adb tools from google
3) download the latest walleye stock image from google
4) put all those things in the same directory and uncompress them there (so flash-all.bat is in the same folder as adb, along with the img and zip files for walleye).
5) adb reboot bootloader
6) flash-all
are those similar to the steps that you did before?
SweetSofie said:
Hey everyone!
I'm a long time reader, but never had the occasion to post until now. I have somewhat recently started tinkering with my phones. I'm a programmer by trade so I'm not at all seperated from technology, however, I fear I may have gotten myself into a but of a ?.
So, here's what I broke: I have a Verizon Wireless Pixel 2. A few weeks ago I read that there was a boot loader unlock for it. As such, I rebooted to the boot loader, ran the "fastboot flashing lock_critical" command. After being unlocked I then proceeded to flash TWRP and then Magisk Manager. All was well until my phone had an unrelated warranty issue. As such, I filed a claim, and got my new phone.
Today I was trying to recover my phone to factory and am getting a few errors. I downloaded this Image from Google "8.0.0 (OPD3.170816.023, Nov 2017, Verizon) - https://dl.google.com/dl/android/aosp/walleye-opd3.170816.023-factory-f269631e.zip"). I extracted it, and ran "flash_all.bat". Througout the process I get an error stating that it can't find a recovery.img. I looked in the .zip and found that to be true. I downloaded the standard stock .zip and noticed it doesn't have one either. In addition, when it gets to the part about flashing the system image I get the following error:
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
--------------------------------------------
Bootloader Version...: mw8998-002.0066.00
Baseband Version.....: g8998-00164-1710262031
Serial Number........: REMOVED
--------------------------------------------
checking product...
OKAY [ 0.000s]
checking version-bootloader...
OKAY [ 0.001s]
checking version-baseband...
OKAY [ -0.000s]
sending 'boot' (32768 KB)...
OKAY [ 0.744s]
writing 'boot'...
OKAY [ 0.000s]
sending sparse 'system' (524284 KB)...
OKAY [ 12.589s]
writing 'system'...
OKAY [ -0.000s]
sending sparse 'system' (524284 KB)...
FAILED (remote: No such partition.)
finished. total time: 13.631s
Anyone have any idea how to remedy this? I'm simply trying to get it back to stock. In addition, if I can get it returned to stock is relocking the bootloader even possible?
Thanks in advance for any help!
-Sofie
Click to expand...
Click to collapse
Just so you know, those "archive does not contain" errors are normal. I get them all the time. Always did on the original Pixel too. I'm not sure about the one at the end. Can't say I've ever seen that on either the Pixel 1 or 2.
SweetSofie said:
Well, that didn't help at all. :crying:
Click to expand...
Click to collapse
Were you able to sort out your issue?
If not, I have heard good things about using this tool to install the latest factory image. Just download this script and follow the instructions in that thread.
If that goes well, then you should be able to boot to the latest build and ready to lock the bootloader, which will factory reset the phone as part of the process.
adb reboot bootloader
fastboot flashing lock
If that process makes you feel uncomfortable, I found this post from another thread doing a similar method (but not using the script above)
Good Luck!
robocuff said:
Just so you know, those "archive does not contain" errors are normal. I get them all the time. Always did on the original Pixel too. I'm not sure about the one at the end. Can't say I've ever seen that on either the Pixel 1 or 2.
Click to expand...
Click to collapse
Thanks for the re-assurance. I did notice that the zips literally dont contain a recovery.img. Is that normal for the Pixel 2?
SweetSofie said:
Thanks for the re-assurance. I did notice that the zips literally dont contain a recovery.img. Is that normal for the Pixel 2?
Click to expand...
Click to collapse
Yes. The recovery is in the boot.img now.
Duhman72 said:
Were you able to sort out your issue?
If not, I have heard good things about using this tool to install the latest factory image. Just download this script and follow the instructions in that thread.
If that goes well, then you should be able to boot to the latest build and ready to lock the bootloader, which will factory reset the phone as part of the process.
adb reboot bootloader
fastboot flashing lock
If that process makes you feel uncomfortable, I found this post from another thread doing a similar method (but not using the script above)
Good Luck!
Click to expand...
Click to collapse
I tried this tool and had no luck either. I ultimately just locked the bootloder, as-is, and sent it back. ? Hopefully the think it's just a component level failure since the boot loader is locked. I guess we will see... ?
SweetSofie said:
I tried this tool and had no luck either. I ultimately just locked the bootloder, as-is, and sent it back. ? Hopefully the think it's just a component level failure since the boot loader is locked. I guess we will see... ?
Click to expand...
Click to collapse
They won't even check, they don't care. They will inspect it for physical abuse and water damage. That is all.
TonikJDK said:
They won't even check, they don't care. They will inspect it for physical abuse and water damage. That is all.
Click to expand...
Click to collapse
I think you're right! So far so good. I haven't had any backlash from Verizon so far. Thanks!
Related
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...
my nexus 5 is almost dead. not pass the logo of the bootloader. I have tried to install custom rom, stock rom, factory reset, but the device does not allow it shows an error so disk write.
C: \>
C: \> fastboot flash boot C :/ nexus / boot.img
sending 'boot' (8700 KB) ...
OKAY [0.481s]
writing 'boot' ...
FAILED (remote: flash write failure)
finished. Total time: 0.664s
C: \>
******************************************
--------------------------------------------
Bootloader Version ...: HHZ11k
Baseband Version .....: M8974A-2.0.50.1.13
Serial Number ........: 04b5a293438497a3
--------------------------------------------
checking product ...
OKAY [0.101s]
checking version-bootloader ...
OKAY [0.097s]
checking version-baseband ...
OKAY [0.097s]
sending 'boot' (8700 KB) ...
OKAY [0.488s]
writing 'boot' ...
OKAY [0.730s]
sending 'recovery' (9284 KB) ...
OKAY [0.546s]
writing 'recovery' ...
FAILED (remote: flash write failure)
finished. Total time: 2.649s
************************************************** *********
sending 'recovery' (13586 KB) ...
OKAY [0.542s]
writing 'recovery' ...
FAILED (remote: flash write failure)
finished. Total time: 0.727s
Have TWRP installed but do not allow any action from this. team allowed to enter boot mode and download mode, but when entering TWRP does not allow any action or file copy .. A technician has reviewed and tells me that the memory can be corrupted uyno allows rewrite.
and try some of the usual methods for restauralr but nothing has worked.
any suggestions to recover and repair my nexus 5.??
please your help urgent
arroyave76 said:
-
Click to expand...
Click to collapse
Try relocking your bootloader with fastboot oem lock, then reboot into bootloader again. If the lock state doesn't stick goes back to being unlocked after the reboot then it might be bad eMMC and you'll have to RMA your device. If it does stay locked afterwards, try using LG Flashtool: http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833
My Nexus 5 is dying
Lethargy said:
Try relocking your bootloader with fastboot oem lock, then reboot into bootloader again. If the lock state doesn't stick goes back to being unlocked after the reboot then it might be bad eMMC and you'll have to RMA your device. If it does stay locked afterwards, try using LG Flashtool: http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833
Click to expand...
Click to collapse
does google will receive the device even when I rooteed and changed the sw?
arroyave76 said:
does google will receive the device even when I rooteed and changed the sw?
Click to expand...
Click to collapse
If you bought it from the Play Store from Google they don't care if you unlocked the bootloader or have a custom ROM or whatever. As long as it's a real manufacturing defect. If you bought it elsewhere you'll have to go straight to LG and they'll probably charge you or maybe even refuse.
What was the result of trying to relock the bootloader?
arroyave76 said:
does google will receive the device even when I rooteed and changed the sw?
Click to expand...
Click to collapse
Google does not care about root or custom rom.
Can you please reboot to fastboot and post the "VARIANT" line here. Thanks.
@Lethargy you have asked why there are two type of memory brand. I think this is how google managed to rise the production of nexus 5 to avoid that all nexus 5s are being sold on the first day and there will be no more until next month like what happend with nexus 4.
bitdomo said:
@Lethargy you have asked why there are two type of memory brand. I think this is how google managed to rise the production of nexus 5 to avoid that all nexus 5s are being sold on the first day and there will be no more until next month like what happend with nexus 4.
Click to expand...
Click to collapse
Ah, that would make sense then :good:
I bought this today and all I know is it's a 64gb One Plus and it was force closing every 2 seconds and basically not usable. After some searching I downloaded the One Plus toolkit and flashed it back to CM11s. It boots back up but I get the AudioFx has stopped every second. Some people have said you need to flash the sound zip and it will fix it. Well, I tried 2 different ones, med and high and still I get the force closing.
Then I found stock fastboot files and tried to bring it back to stock that way but I keep getting this when it gets to system:
checking product... OKAY [ 0.002s]
sending 'boot' (5606 KB)... OKAY [ 0.423s]
writing 'boot'... OKAY [ 0.091s]
ding 'recovery' (7458 KB)... OKAY [ 0.548s]
writing 'recovery'... OKAY [ 0.115s]
ding 'system' (774864 KB)... FAILED (remote: data too large)
I;ve tried this with multiple files and still get the same thing. I even restarted the computer a, updated the SDK and still can't do jack. I used the tool to flash back to CM11s, installed Twrp and tried to install a bone stock OTA rom by Caulkulin. I get failed to mount errors in recovery.
I'm stumped with this phone and need some help
thanks
edit: I know its not technically bricked, but its inoperable as a brick entails. I managed to flash all kinds of stock software, system images, etc but AudioFX still comes up.
Edit 2: I decided to flash a rom without audio fx, I choose Slim Kat, and it boots without the AudioFX but now it boots but after a few seconds will reboot. Over and over. Is this ONE Plus defective?
phone
2strokenut said:
I bought this today and all I know is it's a 64gb One Plus and it was force closing every 2 seconds and basically not usable. After some searching I downloaded the One Plus toolkit and flashed it back to CM11s. It boots back up but I get the AudioFx has stopped every second. Some people have said you need to flash the sound zip and it will fix it. Well, I tried 2 different ones, med and high and still I get the force closing.
Then I found stock fastboot files and tried to bring it back to stock that way but I keep getting this when it gets to system:
checking product... OKAY [ 0.002s]
sending 'boot' (5606 KB)... OKAY [ 0.423s]
writing 'boot'... OKAY [ 0.091s]
ding 'recovery' (7458 KB)... OKAY [ 0.548s]
writing 'recovery'... OKAY [ 0.115s]
ding 'system' (774864 KB)... FAILED (remote: data too large)
I;ve tried this with multiple files and still get the same thing. I even restarted the computer a, updated the SDK and still can't do jack. I used the tool to flash back to CM11s, installed Twrp and tried to install a bone stock OTA rom by Caulkulin. I get failed to mount errors in recovery.
I'm stumped with this phone and need some help
thanks
Click to expand...
Click to collapse
where did you buy the phone..Is it stock or rooted phone when you buy it?
paztine said:
where did you buy the phone..Is it stock or rooted phone when you buy it?
Click to expand...
Click to collapse
I have a cell phone store, guy came in to sell it, says he rooted it but couldn't get it to stop force closing.
Edit:
I got that rom loaded up on the phone from TWRP and I STILL get that damn AudioFx thing force closing. WTF?
format data
2strokenut said:
I have a cell phone store, guy came in to sell it, says he rooted it but couldn't get it to stop force closing.
Edit:
I got that rom loaded up on the phone from TWRP and I STILL get that damn AudioFx thing force closing. WTF?
Click to expand...
Click to collapse
You can try format data from twrp this will do a clean install of OS but it will wipe whatever you have in you phone..but not the OS..This is different from data wipe..cache wipe..etc..It will prompt you to say yes or no if you want to wipe..
paztine said:
You can try format data from twrp this will do a clean install of OS but it will wipe whatever you have in you phone..but not the OS..This is different from data wipe..cache wipe..etc..It will prompt you to say yes or no if you want to wipe..
Click to expand...
Click to collapse
You can do that from fastboot with: fastboot format data ; but as stated, it WILL wipe everything on your device; copy your precious files to your pc.
try this
2strokenut said:
I bought this today and all I know is it's a 64gb One Plus and it was force closing every 2 seconds and basically not usable. After some searching I downloaded the One Plus toolkit and flashed it back to CM11s. It boots back up but I get the AudioFx has stopped every second. Some people have said you need to flash the sound zip and it will fix it. Well, I tried 2 different ones, med and high and still I get the force closing.
Then I found stock fastboot files and tried to bring it back to stock that way but I keep getting this when it gets to system:
checking product... OKAY [ 0.002s]
sending 'boot' (5606 KB)... OKAY [ 0.423s]
writing 'boot'... OKAY [ 0.091s]
ding 'recovery' (7458 KB)... OKAY [ 0.548s]
writing 'recovery'... OKAY [ 0.115s]
ding 'system' (774864 KB)... FAILED (remote: data too large)
I;ve tried this with multiple files and still get the same thing. I even restarted the computer a, updated the SDK and still can't do jack. I used the tool to flash back to CM11s, installed Twrp and tried to install a bone stock OTA rom by Caulkulin. I get failed to mount errors in recovery.
I'm stumped with this phone and need some help
thanks
Click to expand...
Click to collapse
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot reboot
try this with factory image cm-11.0-XNPH30O-bacon-signed-fastboot.zip .
source: http://forum.xda-developers.com/show....php?t=2770535
---------- Post added at 06:02 PM ---------- Previous post was at 05:44 PM ----------
If you can go to twrp..fastboot. and all that jazz.your phone is not brick..
paztine said:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot reboot
try this with factory image cm-11.0-XNPH30O-bacon-signed-fastboot.zip .
source: http://forum.xda-developers.com/show....php?t=2770535
---------- Post added at 06:02 PM ---------- Previous post was at 05:44 PM ----------
If you can go to twrp..fastboot. and all that jazz.your phone is not brick..
Click to expand...
Click to collapse
that link gives me error 404
teh roxxorz said:
You can do that from fastboot with: fastboot format data ; but as stated, it WILL wipe everything on your device; copy your precious files to your pc.
Click to expand...
Click to collapse
I've already done a clean install from twrp, wipe data, system, cache, dalvik. Shouldn't that be clean enough? Why does the audiofx keep popping up?
2strokenut said:
I bought this today and all I know is it's a 64gb One Plus and it was force closing every 2 seconds and basically not usable. After some searching I downloaded the One Plus toolkit and flashed it back to CM11s. It boots back up but I get the AudioFx has stopped every second. Some people have said you need to flash the sound zip and it will fix it. Well, I tried 2 different ones, med and high and still I get the force closing.
Then I found stock fastboot files and tried to bring it back to stock that way but I keep getting this when it gets to system:
checking product... OKAY [ 0.002s]
sending 'boot' (5606 KB)... OKAY [ 0.423s]
writing 'boot'... OKAY [ 0.091s]
ding 'recovery' (7458 KB)... OKAY [ 0.548s]
writing 'recovery'... OKAY [ 0.115s]
ding 'system' (774864 KB)... FAILED (remote: data too large)
I;ve tried this with multiple files and still get the same thing. I even restarted the computer a, updated the SDK and still can't do jack. I used the tool to flash back to CM11s, installed Twrp and tried to install a bone stock OTA rom by Caulkulin. I get failed to mount errors in recovery.
I'm stumped with this phone and need some help
thanks
Click to expand...
Click to collapse
Use this guide
thegiolly said:
Use this guide
Click to expand...
Click to collapse
I just followed this guide, downloaded the file, unzipped, flashed everything but the last step, it gives me an error:
C:\Cyanogen>fastboot update -w cm-11.0-XNPH30O-bacon-signed-fastboot.zip
error: failed to load '-w'
2strokenut said:
I just followed this guide, downloaded the file, unzipped, flashed everything but the last step, it gives me an error:
C:\Cyanogen>fastboot update -w cm-11.0-XNPH30O-bacon-signed-fastboot.zip
error: failed to load '-w'
Click to expand...
Click to collapse
Took out the -w, still gives me the error failed data too large
Flash stock rom through odin
Sent from my GT-I8190N using XDA Free mobile app
JoniSerenius said:
Flash stock rom through odin
Sent from my GT-I8190N using XDA Free mobile app
Click to expand...
Click to collapse
haha
Do I need to relock the bootloader on this?
2strokenut said:
I just followed this guide, downloaded the file, unzipped, flashed everything but the last step, it gives me an error:
C:\Cyanogen>fastboot update -w cm-11.0-XNPH30O-bacon-signed-fastboot.zip
error: failed to load '-w'
Click to expand...
Click to collapse
Try using this slim SDK
thegiolly said:
Try using this slim SDK
Click to expand...
Click to collapse
That actually allowed me to flash system without the error! Unfortunately, I still get the audioFX has stopped when it boots
So it doesn't give me the -w error anymore earlier but now its giving me this:
C:\Cyanogen>fastboot update -w cm-11.0-XNPH30O-bacon-signed-fastboot.zip
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
error: update package missing system.img
So it doesn't give me the -w error anymore earlier but now its giving me this:
C:\Cyanogen>fastboot update -w cm-11.0-XNPH30O-bacon-signed-fastboot.zip
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
error: update package missing system.img
Edit: I got it to finally flash all this and everything seemed to go smooth, until it boots the same goddamn audioFx force close. What is going on with this phone?
2strokenut said:
So it doesn't give me the -w error anymore earlier but now its giving me this:
C:\Cyanogen>fastboot update -w cm-11.0-XNPH30O-bacon-signed-fastboot.zip
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
error: update package missing system.img
Edit: I got it to finally flash all this and everything seemed to go smooth, until it boots the same goddamn audioFx force close. What is going on with this phone?
Click to expand...
Click to collapse
After flashing with fastboot, wipe cache and data from recovery...
thegiolly said:
After flashing with fastboot, wipe cache and data from recovery...
Click to expand...
Click to collapse
same thing. See first post.
I've tried slim kat and PA and both can boot up fine without an FC but after a few seconds they immediately reboot, over and over
EDIT: Guys it worked. Some weird **** happened first, keyboard wasn't working on stock rom and everything was buggy but after an update with HiSuite and a factory reset everything works fine. Thank you for all your support.
I bricked my Honor 8 (FRD-L09) while trying to go back to stock rom. I can only acces eRecovery and Fastboot, when I try to access normal recovery, the screen just freezes at "Your device is booting now". After reading multiple guides, I tried unbricking with the Huawei Multitool but I always get these errors:
sending 'boot' (15464 KB)...
OKAY [ 0.334s]
writing 'boot'...
OKAY [ 0.371s]
finished. total time: 0.710s
target reported max download size of 471859200 bytes
sending 'cust' (433554 KB)...
OKAY [ 9.343s]
writing 'cust'...
FAILED (remote: partition error)
finished. total time: 9.358s
target reported max download size of 471859200 bytes
sending 'recovery' (36996 KB)...
OKAY [ 0.794s]
writing 'recovery'...
OKAY [ 0.883s]
finished. total time: 1.682s
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (435393 KB)...
OKAY [ 10.280s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 10.327s
I'm desperate and I don't know what to do.
EDIT: I HAVE MANAGED TO INSTALL RR BUT STILL CAN'T GO BACK TO STOCK.
Rommco05 said:
Hi, what about twrp u loos access?
Click to expand...
Click to collapse
I have regained access to twrp. I have installed a custom rom, but still can't install stock rom.
Rommco05 said:
Your hole model number is? U try yo flash stock rom via twrp?
Click to expand...
Click to collapse
FRD-L09. I haven't flashed stock rom via TWRP. I tried the huawei extractor method right now, I'm probably doing something wrong, I'll look more into it . I'm calm now that I managed to install a custom rom.
Rommco05 said:
Ok, so if still without luck try to download full stock fw B360 or B381 (2 zips)
Click to expand...
Click to collapse
Ok.. I will try that. My phone is stuck at "your device is booting up" screen after flashing stock recovery.
Note that there is also recovery2 in first update.zip when you extract it via Huawei Multitool. Thats probably why recovery never boots up, it's not all. Try to send the first basic ones - boot, recovery, recovery2, erecovery, and so on (don't exactly remember which). Then you should be fine to dload or flash the rest through fastboot (if possible). And remember to always use full-ota-mf-pv version of software (like FRD-L09C432B381) with about 2.37 GB total (2 zip files).
Rommco05 said:
You can flash back twrp?
Click to expand...
Click to collapse
Yes, I can.
So, did it work?!
PalakMi said:
So, did it work?!
Click to expand...
Click to collapse
I'm at work now. I'll try after a few hours.
Radu Florin said:
I'm at work now. I'll try after a few hours.
Click to expand...
Click to collapse
Good luck, I hope it works after all
Guys it worked. Some weird **** happened first, keyboard wasn't working on stock rom and everything was buggy but after an update with HiSuite and a factory reset everything works fine. Thank you for all your support.
Radu Florin said:
Guys it worked. Some weird **** happened first, keyboard wasn't working on stock rom and everything was buggy but after an update with HiSuite and a factory reset everything works fine. Thank you for all your support.
Click to expand...
Click to collapse
Great , your device is back :highfive:
I tried to root by flashing the patched boot image as describe in https://forum.xda-developers.com/ho...agisk-root-honor-view-10-mate-10-pro-t3749280. After that, the phone went into a bootloop.
When I get to the eRecovery screen, I tried 'Download latest version and recovery.' It got to 'getting package information from server' but then stopped with 'getting package info failed.'
I then tried 'Wipe data/factory reset' and it rebooted but nothing changed.
I don't know what else to try with this phone. None of the current versions of twrp would run on it. I've never bricked a device in years of rooting.
thecdn said:
I tried to root by flashing the patched boot image as describe in https://forum.xda-developers.com/ho...gisk-root-honor-view-10-mate-10-pro-t3749280. After that, the phone went into a bootloop.
When I get to the eRecovery screen, I tried 'Download latest version and recovery.' It got to 'getting package information from server' but then stopped with 'getting package info failed.'
I then tried 'Wipe data/factory reset' and it rebooted but nothing changed.
I don't know what else to try with this phone. None of the current versions of twrp would run on it. I've never bricked a device in years of rooting.
Click to expand...
Click to collapse
You need to restore your original ramdisk. Also, you have to patch your own ramdisk.img with Magisk Manager if you want to try rooting your device.
And btw, this is a development forum, not General or Q&A one. Read carefully before trying to mod this device, or you will end up with an expensive brick.
please contact me on hangouts i may be able to help [email protected]
You can download the appropriate images to restore your device below. These are for the US variant (BKL-L04)
https://drive.google.com/open?id=1kfNAjIwiMj8wpeDuJayiH2t-srYBBvN3
Edit: Link updated
[email protected]_USA said:
You can download the appropriate images to restore your device below. These are for the US variant (BKL-L04)
https://drive.google.com/open?id=1kf...yiH2t-srYBBvN3
Click to expand...
Click to collapse
I"m getting a web page not found 404 when I try that link.
thecdn said:
I"m getting a web page not found 404 when I try that link.
Click to expand...
Click to collapse
Same
thecdn said:
I"m getting a web page not found 404 when I try that link.
Click to expand...
Click to collapse
freeza said:
Same
Click to expand...
Click to collapse
look like chris didnt updated the link,
bdw here you guys go https://drive.google.com/open?id=1kfNAjIwiMj8wpeDuJayiH2t-srYBBvN3
I flashed the system.img and the recovery_ramdisk.img. It booted to the eRecovery screen again.
I tried 'Download latest version and recovery' and it failed with the 'getting package info failed' error again.
I then tried 'Wipe data/factory reset' and unlike before, it actually went through and said it was successfully completed. But then it rebooted twice and went back to the eRecovery screen again.
Any ideas on how to proceed from here?
ETA: When I pressed vol up/power after this it went to a screen which said 'software install failed' instead of the recovery screen I thougt it would go to. After the first time, pressing vol up/power goes to the EMUI screen with the options of 'Reboot' 'Wipe data/factory reset' and 'Wipe cache partition.'
thecdn said:
I flashed the system.img and the recovery_ramdisk.img. It booted to the eRecovery screen again.
I tried 'Download latest version and recovery' and it failed with the 'getting package info failed' error again.
I then tried 'Wipe data/factory reset' and unlike before, it actually went through and said it was successfully completed. But then it rebooted twice and went back to the eRecovery screen again.
Any ideas on how to proceed from here?
ETA: When I pressed vol up/power after this it went to a screen which said 'software install failed' instead of the recovery screen I thougt it would go to. After the first time, pressing vol up/power goes to the EMUI screen with the options of 'Reboot' 'Wipe data/factory reset' and 'Wipe cache partition.'
Click to expand...
Click to collapse
You need to restore ramdisk, not recovery_ramdisk.
Pretoriano80 said:
You need to restore ramdisk, not recovery_ramdisk.
Click to expand...
Click to collapse
I did 'fastboot flash ramdisk ramdisk.img' and it still does a couple of reboots and then goes back to the EMUI screen with the recovery/reset/reboot/shutdown options.
In summary, this morning I did:
'fastboot flash system system.img' which resulted in 7 occurances of 'sending sparse system x/7 (xxxx KB)...' - which I have never seen before but all finished with OKAY
'fastboot flash recovery_ramdisk recovery_ramdisk.img'
'fastboot flash ramdisk ramdisk.img'
Is there something else I could do or redo in a particular order?
thecdn said:
I did 'fastboot flash ramdisk ramdisk.img' and it still does a couple of reboots and then goes back to the EMUI screen with the recovery/reset/reboot/shutdown options.
In summary, this morning I did:
'fastboot flash system system.img' which resulted in 7 occurances of 'sending sparse system x/7 (xxxx KB)...' - which I have never seen before but all finished with OKAY
'fastboot flash recovery_ramdisk recovery_ramdisk.img'
'fastboot flash ramdisk ramdisk.img'
Is there something else I could do or redo in a particular order?
Click to expand...
Click to collapse
Try to also flash kernel : fastboot flash kernel kernel.img
Pretoriano80 said:
Try to also flash kernel : fastboot flash kernel kernel.img
Click to expand...
Click to collapse
No joy yet but I do appreciate all the help.
thecdn said:
No joy yet but I do appreciate all the help.
Click to expand...
Click to collapse
Did you tried a factory reset from stock recovery?
Pretoriano80 said:
Did you tried a factory reset from stock recovery?
Click to expand...
Click to collapse
I've tried two factory resets after completing the above mentioned actions. Both times reported they were successful it still won't boot to the os, goes to the EMUI screen after several boot attempts.
Same problem here on a US BKL-L04 =(
I flashed a magisk modified ramdisk.img and have been in bootloop ever since.
I've downloaded and flashed recovery_ramdisk.img, ramdisk.img, and kernel.img from the link earlier in this thread: https://drive.google.com/drive/folders/1kfNAjIwiMj8wpeDuJayiH2t-srYBBvN3
I've then did "Wipe data/factory reset" from Huawei eRecovery - no luck
$ fastboot flash ramdisk ramdisk.img
target reported max download size of 471859200 bytes
sending 'ramdisk' (16384 KB)...
OKAY [ 0.401s]
writing 'ramdisk'...
OKAY [ 0.083s]
finished. total time: 0.484s
$ fastboot flash recovery_ramdisk recovery_ramdisk.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (32768 KB)...
OKAY [ 0.807s]
writing 'recovery_ramdisk'...
OKAY [ 0.164s]
finished. total time: 0.971s
sek stock2 $ fastboot flash kernel kernel.img
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.615s]
writing 'kernel'...
OKAY [ 0.128s]
finished. total time: 0.745s
Aside from fastboot happing very quickly (< 1 second even for 32 meg recovery_ramdisk.img) everything seems to work fine... The phone just no longer boots - it trys a few times - displaying the "Your device has been unlocked and can't be trusted" screen for quite a while and the non-animated blue honor screen briefly and then ends up in EMUI eRecovery.
Are these files still up to date? Or perhaps there were newer versions on my phone and that's why flashing the older ones isn't working?
Also worth noting, I'm flashing from a mac with Android sdk fastbook:
$ fastboot --version
fastboot version 0.0.1-4500957
Installed as /Users/sek/Library/Android/sdk/platform-tools/fastboot
Thanks for any help / tips!
akasek said:
I flashed a magisk modified ramdisk.img and have been in bootloop ever since.
I've downloaded and flashed recovery_ramdisk.img, ramdisk.img, and kernel.img from the link earlier in this thread: https://drive.google.com/drive/folders/1kfNAjIwiMj8wpeDuJayiH2t-srYBBvN3
I've then did "Wipe data/factory reset" from Huawei eRecovery - no luck
$ fastboot flash ramdisk ramdisk.img
target reported max download size of 471859200 bytes
sending 'ramdisk' (16384 KB)...
OKAY [ 0.401s]
writing 'ramdisk'...
OKAY [ 0.083s]
finished. total time: 0.484s
$ fastboot flash recovery_ramdisk recovery_ramdisk.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (32768 KB)...
OKAY [ 0.807s]
writing 'recovery_ramdisk'...
OKAY [ 0.164s]
finished. total time: 0.971s
sek stock2 $ fastboot flash kernel kernel.img
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.615s]
writing 'kernel'...
OKAY [ 0.128s]
finished. total time: 0.745s
Aside from fastboot happing very quickly (< 1 second even for 32 meg recovery_ramdisk.img) everything seems to work fine... The phone just no longer boots - it trys a few times - displaying the "Your device has been unlocked and can't be trusted" screen for quite a while and the non-animated blue honor screen briefly and then ends up in EMUI eRecovery.
Are these files still up to date? Or perhaps there were newer versions on my phone and that's why flashing the older ones isn't working?
Also worth noting, I'm flashing from a mac with Android sdk fastbook:
$ fastboot --version
fastboot version 0.0.1-4500957
Installed as /Users/sek/Library/Android/sdk/platform-tools/fastboot
Thanks for any help / tips!
Click to expand...
Click to collapse
Flash stock kernel, ramdisk and recovery ramdisk for your model in fastboot and you'll be able to boot again
Rommco05 said:
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Use this tool for flash full fw
Click to expand...
Click to collapse
Thanks for the info, that tool looks interesting. Where can I get the stock files for BKL-L04 US version Honor View 10?
I have now tried flashing kernel, ramdisk, recovery_ramdisk and system from both of these sources:
- https://drive.google.com/drive/folders/1kfNAjIwiMj8wpeDuJayiH2t-srYBBvN3
- http://arter97.com/browse/v10/stock/BKL-L04/
They all appear to flash fine. I tried flashing vendor.img as well, but get an error on that:
$ fastboot flash vendor vendor.img
target reported max download size of 471859200 bytes
Invalid sparse file format at header magic
sending sparse 'vendor' 1/2 (445713 KB)...
OKAY [ 9.718s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 9.724s
It still doesn't want to boot. I end up in eRecovery each time.
I am able to flash TWRP from Pretoriano80: https://forum.xda-developers.com/honor-view-10/development/recovery-twrp-3-2-1-0-t3769917
It seems to be working properly, perhaps that helps me somehow?
Finally back up and running - Thanks Tecalote!
FYI: I am finally back up and running - Tecalote's post worked perfectly (and BKL-L04 update zips are linked earlier in the thread also): https://forum.xda-developers.com/showpost.php?p=76331841&postcount=46
akasek said:
Thanks for the info, that tool looks interesting. Where can I get the stock files for BKL-L04 US version Honor View 10?
I have now tried flashing kernel, ramdisk, recovery_ramdisk and system from both of these sources:
- https://drive.google.com/drive/folders/1kfNAjIwiMj8wpeDuJayiH2t-srYBBvN3
- http://arter97.com/browse/v10/stock/BKL-L04/
They all appear to flash fine. I tried flashing vendor.img as well, but get an error on that:
$ fastboot flash vendor vendor.img
target reported max download size of 471859200 bytes
Invalid sparse file format at header magic
sending sparse 'vendor' 1/2 (445713 KB)...
OKAY [ 9.718s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 9.724s
It still doesn't want to boot. I end up in eRecovery each time.
I am able to flash TWRP from Pretoriano80: https://forum.xda-developers.com/honor-view-10/development/recovery-twrp-3-2-1-0-t3769917
It seems to be working properly, perhaps that helps me somehow?
Click to expand...
Click to collapse
akasek said:
Thanks for the info, that tool looks interesting. Where can I get the stock files for BKL-L04 US version Honor View 10?
I have now tried flashing kernel, ramdisk, recovery_ramdisk and system from both of these sources:
- https://drive.google.com/drive/folders/1kfNAjIwiMj8wpeDuJayiH2t-srYBBvN3
- http://arter97.com/browse/v10/stock/BKL-L04/
They all appear to flash fine. I tried flashing vendor.img as well, but get an error on that:
$ fastboot flash vendor vendor.img
target reported max download size of 471859200 bytes
Invalid sparse file format at header magic
sending sparse 'vendor' 1/2 (445713 KB)...
OKAY [ 9.718s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 9.724s
It still doesn't want to boot. I end up in eRecovery each time.
I am able to flash TWRP from Pretoriano80: https://forum.xda-developers.com/honor-view-10/development/recovery-twrp-3-2-1-0-t3769917
It seems to be working properly, perhaps that helps me somehow?
Click to expand...
Click to collapse
try to install twrp and then do hruupdate from twrp
get your files from firmware finder and search xda forums to how to install those files
its very easy and your system will be back in stock format
after that you can try to root and install custom rom
thecdn said:
No joy yet but I do appreciate all the help.
Click to expand...
Click to collapse
Hi, what helped you there? I have a similar situation.
"Hi,
I need some advice on what can be done with my Honor View10 as it keeps gracing a bootloop followed by fasrboot mode.
Mine is a C675 variant and I was on 190 when I decided to unroot and update the device to 218. Once that was done, I flashed a patched recovery_ramdisk boot image that was patched using magisk to support it. Worked fine. Did a reboot and it got stuck in a bootloop.
I have tried flashing other patch.imgs too, due instance tried extracting recovery.img of the current version of rom, flashed it, no luck!
Tried flashing the patched version of that, still did not help.
I am on EMUI9, any help please?
Also can anyone help me with the link of one of the latest versions of C675 update please? "
This is what happened to me