Hello guys,
I present the problem. My XT925 now seems dead. A few months ago I received tamto expected update to Android 4.4.2 ... everything went well until now.
Unlocking the phone to call and all processes ranging android crash ... but everyone, I can not use your smartphone so I decided to restart it ... and voila 'since then remains locked on the screen "Warning Bootloader Unlocked" and is wrong ... does not turn off even.
Pressing on Power + Volume Down I can go the fastboot mode (but not in recovery mode). I tried changing the recovery, but fastboot me back "FAILED to Write".
In desperation I tried to restore the firmware 4.1.2 via RSD .... hangs in step 2 (write error !!!). I run all these steps several times (in the past I had the CM 11, then returned to the stock to wait for the OTA 4.4.2 ufficilae), so I do not think it was wrong.
What do you think? I'm waiting to discharge the battery to make other desperate attempts.
thanks
I've tried to flash tz.mbn...it fail. Below result:
sending 'tz' (210 KB)...
OKAY [ 0.036s]
writing 'tz'...
Failed to erase partition
Failed to flash partition tz
FAILED (remote failure)
finished. total time: 0.317s
If I understand correctly, you're phone updated without problems and then for some reason failed while in use, and because of that, you tried to hard reset it. Yes?
If that's the case perhaps you don't know that the combination of buttons to access recovery changed for kk bootloader . You have to press power and then volume(+) briefly, while still holding power when the distressed android appears after selected “recovery" in the first place.
If that's not the case, I don't see why you should flash “tz" file, since this particular solution (as far as I know) comes handy when the update fails flashing and the fastboot screen shows something like “failed GPT“ or so. Even more, your bootloader still unlocked -according to you- which is different to the security reasons “locked bootloader" when the update fails.
I say the best you can do is flash another ROM but, with fastboot commands instead of RSDLite. You may flash the
Jellybean version you had previous to the KK OTA and then let the update con again.
kokinator02 said:
If I understand correctly, you're phone updated without problems and then for some reason failed while in use, and because of that, you tried to hard reset it. Yes?
If that's the case perhaps you don't know that the combination of buttons to access recovery changed for kk bootloader . You have to press power and then volume(+) briefly, while still holding power when the distressed android appears after selected “recovery" in the first place.
If that's not the case, I don't see why you should flash “tz" file, since this particular solution (as far as I know) comes handy when the update fails flashing and the fastboot screen shows something like “failed GPT“ or so. Even more, your bootloader still unlocked -according to you- which is different to the security reasons “locked bootloader" when the update fails.
I say the best you can do is flash another ROM but, with fastboot commands instead of RSDLite. You may flash the
Jellybean version you had previous to the KK OTA and then let the update con again.
Click to expand...
Click to collapse
Dear kokinator,
i'm not able to enter into recovery mode. If i try to do it, phone start full boot and stop on logo interface "Warning...bootloader unlocked ...etc".
I've tried to flash Jelly Bean using fastboot, but it fails...for example i see:
flash partition partition_signed
sending 'partition' (32 KB)...
OKAY [ 0.022s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 0.183s
What do you think I can do?
Thanks and Best Regards
Hello, are your fastboot files up to date? Are you trying to do this on a commands console or from a toolkit?
kokinator02 said:
Hello, are your fastboot files up to date? Are you trying to do this on a commands console or from a toolkit?
Click to expand...
Click to collapse
Hi kokinator02,
i've tried to call fastboot from commands console. I've tried to use RSD Lite also, but result is the same.
I've always the same result: Failed to Write.....
It could be a hardware problem ... for example on the memory?
Thanks a lot
what region is your phone from? what stock did you go back to when you wanted to wait for 4.4.2 OTA?
hbenz2008 said:
what region is your phone from? what stock did you go back to when you wanted to wait for 4.4.2 OTA?
Click to expand...
Click to collapse
Hi hbenz2008,
my phone is Orange UK version. I've flashed Jelly Bean 4.1.2 Orange UK version for wait 4.4.2 OTA update. I've flashed 9.8.2Q-8-XT925_VQU-26_USERSIGNED_S7_USAVANQUGBOR031.0R_LSAVNQJBEEGB_P011_A006_CFC.xm.
This is screen shot after 4.4.2 OTA update:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks a lot
Did you try flashing gpt and tz i sent you?
hbenz2008 said:
Did you try flashing gpt and tz i sent you?
Click to expand...
Click to collapse
Yes, i've tried using fastboot from command line, but i have always Write Error.
sending 'tz' (210 KB)...
OKAY [ 0.036s]
writing 'tz'...
Failed to erase partition
Failed to flash partition tz
FAILED (remote failure)
finished. total time: 0.317s
do you have the Orange 4.4.2 ota? you just need the right files.
hbenz2008 said:
do you have the Orange 4.4.2 ota? you just need the right files.
Click to expand...
Click to collapse
No hbenz2008,
i'haven't Orange 4.4.2 files. I'm not able to find it on Internet. I've received via OTA. I've only tried to flash old 4.1.2 Jelly Bean available on web.
ok, just to understand correctly. You tried flashing gpt first, then tz and both failed.right?
hbenz2008 said:
ok, just to understand correctly. You tried flashing gpt first, then tz and both failed.right?
Click to expand...
Click to collapse
Yes, correct.
mitsus said:
Yes, correct.
Click to expand...
Click to collapse
Now i've find this: https://docs.google.com/a/acotel.com/file/d/0B8vZjOPRNHL_aEdXOUluYlhXZWs/edit.
Do you think that i can try to flash it?
hunt for gpt and tz from orange 4.4.2 ota ;just throw it out there . I am sure someone caught the OTA. I will do a quick check.
check with ukmotofan
http://forum.xda-developers.com/showthread.php?t=2625448&page=2
update is in system/cache
hbenz2008 said:
hunt for gpt and tz from orange 4.4.2 ota ;just throw it out there . I am sure someone caught the OTA. I will do a quick check.
check with ukmotofan
http://forum.xda-developers.com/showthread.php?t=2625448&page=2
update is in system/cache
Click to expand...
Click to collapse
Dear hbenz2008,
I am very grateful for your interest. I wrote to ask him to UKMotofan files.
Thanks again
anytime man, you will revive your xt 925, no doubt. If my xt 925 wasnt missing buttons, I would have rsd orange and got you the OTA. With nandorid backup , this would have been just a matter of 10 min tops.
I don't understand why mitsus should flash gpt/tz files if fastboot screen doesn't report failure with it, any way, I once had to flash both to my Razr (which, at the time being was “security write locked up" stocked in fastboot screen screaming gpt writing failure). The thing is, I recall I didn't get the fr retail files (I was on JB FR CEE Retail updating to KK) but the Brazilian retail gpt/tz and it worked, after flashing, the KK update resumed and finished as if nothing had happened.
---------- Post added at 06:04 PM ---------- Previous post was at 05:58 PM ----------
mitsus said:
I've tried to flash tz.mbn...it fail. Below result:
sending 'tz' (210 KB)...
OKAY [ 0.036s]
writing 'tz'...
Failed to erase partition
Failed to flash partition tz
FAILED (remote failure)
finished. total time: 0.317s
Click to expand...
Click to collapse
Hello, I still think this is not the problem but, let's give it a try, worst it can happen is another write failure, right?
Please tell me the exact order and commands you have entered in cmd console.
kokinator02 said:
I don't understand why mitsus should flash gpt/tz files if fastboot screen doesn't report failure with it, any way, I once had to flash both to my Razr (which, at the time being was “security write locked up" stocked in fastboot screen screaming gpt writing failure). The thing is, I recall I didn't get the fr retail files (I was on JB FR CEE Retail updating to KK) but the Brazilian retail gpt/tz and it worked, after flashing, the KK update resumed and finished as if nothing had happened.
---------- Post added at 06:04 PM ---------- Previous post was at 05:58 PM ----------
Hello, I still think this is not the problem but, let's give it a try, worst it can happen is another write failure, right?
Please tell me the exact order and commands you have entered in cmd console.
Click to expand...
Click to collapse
Hi kokinator02,
i've tried (via console) all commands, executed in order how RSD Lite does.
I've tried:
fastboot flash partion partition_signed
fastboot flash sbl1 sbl1_signed
etc
For all i've same errors:
Failed to flash ...
FAILED (remote failure)
I've tried also use RSD Lite, but only with Jelly Bean UK version
Thanks a lot
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...
So my friend gave me her old first gen Moto G (XT1032 from Telus in Canada) because it stopped working for her. She told me nothing special happened before and she did not try to do an update. I have no way to know what version of Android the device was running before it bricked. I am familiar with Android devices but mostly Nexus phones so I thought I could try to fix it myself. So right now, here is what it does :
- If I try to turn it on, it stays stuck on the Motorola logo
- If I try to go in the bootloader, I can see it and it says the version number is 41.18 (also the device is locked and was never rooted or anything)
- When in the bootloader, if I try to Normal startup it reboots and stays stuck on the Motorola logo
- If I try to go to recovery or factory reset, the phone just shuts down and nothing happens
I have seen other posts on XDA which seem to relate to the same problem but none of them could fix the one I have. Any help would be much appreciated.
Thanks
Unstable hardware. It happened to me too after throwing on the floor for the 1000th time. The screen is still 100% healthy LoL.
Try returning it if it's still in warranty. If not, try unlocking the bootloader and flashing the latest GPE
Sent from my XT1562 using Tapatalk
Hi,
Seems like firmware goes away... **** happens, even without "throwing" it on the floor a thousand times Unlock it, install a custom recovery (latest Twrp is 2.8.7.0) and flash firmware you want...
If you get an error when flashing, maybe due to your bootloader version... Latest roms require latest bootloader (41.1A). There is a bootloader upgrader tool available in the general section of Moto G forum.
Sorry if I don't give you direct links but I'm on my phone Don't worry, you'll find easily...
Let us know evolution
Can't flash recovery
satanas17 said:
Hi,
Seems like firmware goes away... **** happens, even without "throwing" it on the floor a thousand times Unlock it, install a custom recovery (latest Twrp is 2.8.7.0) and flash firmware you want...
If you get an error when flashing, maybe due to your bootloader version... Latest roms require latest bootloader (41.1A). There is a bootloader upgrader tool available in the general section of Moto G forum.
Sorry if I don't give you direct links but I'm on my phone Don't worry, you'll find easily...
Let us know evolution
Click to expand...
Click to collapse
OK So Im trying to flash TWRP (2.8.6.0) with fastboot but when I do I get 2 errors :
target max-sparse-size: 256MB
sending 'recovery' (8480 KB)...
OKAY [ 10.195s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 15.208s
It seems my recovery partition is not formatted or something. What should I do now ? Also Im on a MAC so I think there is now way for me to update the bootloader which is not at 41.18
I also tried to boot the recovery (both stock and twrp 2.8.6.0 and 2.8.7.0) instead of flashing it by doing this :
fastboot boot recovery.img
I get this :
downloading 'boot.img'...
OKAY [ 5.330s]
booting...
FAILED (remote failure)
finished. total time: 15.383s
Im not sure where the boot.img is supposed to come from. Am I doing something wrong?
Thanks!
I flash the factory image with the flash-all.bat, but I got these.
What shoule I do?
Code:
target didn't report max-download-size
sending 'bootloader' (38728 KB)...
FAILED (remote: Uploaded data exceeds max-download-size)
finished. total time: 0.000s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
target didn't report max-download-size
sending 'radio' (60428 KB)...
FAILED (remote: Uploaded data exceeds max-download-size)
finished. total time: -0.000s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.003s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (32 MB) to disk... took 0.188s
target didn't report max-download-size
error: Failed to identify current slot
Press any key to exit...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The bootloader that came with our phone is borked and doesn't allow flashing the new bootloader. Need to download the OTA image from Google and follow their steps for flashing it via recovery. Make sure to flash the stock boot.img for your current setup beforehand to unroot. The OTA will overwrite the bootloader and fix the issue so in the future you will be able to flash-all with the factory images as usual.
Ra6idr0y said:
The bootloader that came with our phone is borked and doesn't allow flashing the new bootloader. Need to download the OTA image from Google and follow their steps for flashing it via recovery. Make sure to flash the stock boot.img for your current setup beforehand to unroot. The OTA will overwrite the bootloader and fix the issue so in the future you will be able to flash-all with the factory images as usual.
Click to expand...
Click to collapse
if the bootloader is unlocked, the flash all command does not work ? If you are on a custom kernel, can't you just download the stock image then run the script then relock the bootloader ?
mikeprius said:
if the bootloader is unlocked, the flash all command does not work ? If you are on a custom kernel, can't you just download the stock image then run the script then relock the bootloader ?
Click to expand...
Click to collapse
The flash all command works fine on an unlocked bootloader. I've used it several times (I play around too much ) As for your second question, I haven't used a custom kernel but I have flashed Magisk which writes to the bootloader and I've never had a problem using the flash-all.bat file. Some people for some reason or another were able to use it (the flash all) for the December update but it would fail to write the bootloader for some reason or another. Some tried flashing the bootloader manually with fastboot and that would fail too. From what I've seen, the only way out for those with that problem was to flash the OTA. I don't know how many of them were using custom kernels so I can't really say if that's the problem or not. I can only tell you I flashed the December update using the flash all and had no problems at all.
Ra6idr0y said:
The bootloader that came with our phone is borked and doesn't allow flashing the new bootloader. Need to download the OTA image from Google and follow their steps for flashing it via recovery. Make sure to flash the stock boot.img for your current setup beforehand to unroot. The OTA will overwrite the bootloader and fix the issue so in the future you will be able to flash-all with the factory images as usual.
Click to expand...
Click to collapse
I have sloved this problem, I changed TYPE-C to TYPE-C cable to TYPE-C to TYPE-A cable and I flashed it.
I think it's google's cable's problem.
My one plus 6 device suddenly bricked without any sign. Shows only boot loader screen. I can reach recovery mood. I wiped all data (I select "erase everything(Music, pics, etc). Then I tried MSM tool (Run as administrator). After complete download it reboot again and wait for 1/2 min. It gose again to boot loop. Then I tried fastboot method. It said "failed to load 'images.zip': Not enough space". I try to wipe data by command "fastboot erase userdata". It said "FAILED (remote: Erase is not allowed in Lock State)". Also run "flash-all.bat" and it said "FAILED (remote: Flashing is not allowed in Lock State)". Nothing happen on my phone screen. Typed "fastboot continue" and it goes to boot loop. Now I stacked in boot loop screen. What should i do now??
you can go into recovery mod that means your phone is not brick.should you try to use fastboot rom?
soihuvuontrang said:
you can go into recovery mod that means your phone is not brick.should you try to use fastboot rom?
Click to expand...
Click to collapse
of course i tried that method. Download latest OOS and adb - platform tools v28.0.0. pest all into OSS file after unzip. I went to fastboot recovery mood. Run "flash-all.bat" and it said "FAILED (remote: Flashing is not allowed in Lock State)". Nothing happen on mobile screen. (NB: when I type command "fastboot devices" it can recognize my device).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
zobayer.a.m said:
of course i tried that method. Download latest OOS and adb - platform tools v28.0.0. pest all into OSS file after unzip. I went to fastboot recovery mood. Run "flash-all.bat" and it said "FAILED (remote: Flashing is not allowed in Lock State)". Nothing happen on mobile screen. (NB: when I type command "fastboot devices" it can recognize my device).
Click to expand...
Click to collapse
Of course You can't flash anything in fastboot nor in recovery...when you fleshed with msm download tool first time you've LOCKED YOUR BOOTLOADER...SO NO MORE FASTBOOT AND RECOVERY FLASHES...TRY WITH MSM TOOL AGAIN...AND DON'T CHANGE ANYTHING...OR UNLOCK YOUR BOOTLOADER AGAIN...YOU CAN READ HOW BASED ON WHAT OOS VERSION IS YOU ON. READ ABOUT IT. AND REMEMBER WHEN IT SAYS LOCKED STATE AND CAN'T FLASH IN FASTBOOT IT MEANS YOUR BOOTLOADER IS LOCKED...
James Blode said:
Of course You can't flash anything in fastboot nor in recovery...when you fleshed with msm download tool first time you've LOCKED YOUR BOOTLOADER...SO NO MORE FASTBOOT AND RECOVERY FLASHES...TRY WITH MSM TOOL AGAIN...AND DON'T CHANGE ANYTHING...OR UNLOCK YOUR BOOTLOADER AGAIN...YOU CAN READ HOW BASED ON WHAT OOS VERSION IS YOU ON. READ ABOUT IT. AND REMEMBER WHEN IT SAYS LOCKED STATE AND CAN'T FLASH IN FASTBOOT IT MEANS YOUR BOOTLOADER IS LOCKED...
Click to expand...
Click to collapse
distinguish beetwen Msm tool and fastboot rom(https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665)
your phone isnot brick,it boot into fastboot mood,you can you fastboot rom (link above). goodluck!
soihuvuontrang said:
distinguish beetwen Msm tool and fastboot rom(https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665)
your phone isnot brick,it boot into fastboot mood,you can you fastboot rom (link above). goodluck!
Click to expand...
Click to collapse
Unfortunately my boot loader is locked. This will not work. I tried it also
James Blode said:
Of course You can't flash anything in fastboot nor in recovery...when you fleshed with msm download tool first time you've LOCKED YOUR BOOTLOADER...SO NO MORE FASTBOOT AND RECOVERY FLASHES...TRY WITH MSM TOOL AGAIN...AND DON'T CHANGE ANYTHING...OR UNLOCK YOUR BOOTLOADER AGAIN...YOU CAN READ HOW BASED ON WHAT OOS VERSION IS YOU ON. READ ABOUT IT. AND REMEMBER WHEN IT SAYS LOCKED STATE AND CAN'T FLASH IN FASTBOOT IT MEANS YOUR BOOTLOADER IS LOCKED...
Click to expand...
Click to collapse
Ok i understand. I tried MSM tool also. After connect my phone with PC this software show connected status. After hit start it start to update. All process work perfectly fine and goes to completed status (text in MSM tool become green). My phone boot up and 1 or 2 min later it shows welcome screen without any touch response. Touch do not work (though touch was ok). After a few second my phone reboot again and stuck into bool loop again. I tried "enchilada_22_O.09_180517", "ANDROID+9+OOS+9.0.8+enchilada_22_O.33_190801_repack", "ANDROID+10+OOS+10.3.2+enchilada_22_J.44_200222". All MSM tools ended up with same result
Are you not able to unlock bootloader via fastboot and then flash a fastboot ROM?
zobayer.a.m said:
Ok i understand. I tried MSM tool also. After connect my phone with PC this software show connected status. After hit start it start to update. All process work perfectly fine and goes to completed status (text in MSM tool become green). My phone boot up and 1 or 2 min later it shows welcome screen without any touch response. Touch do not work (though touch was ok). After a few second my phone reboot again and stuck into bool loop again. I tried "enchilada_22_O.09_180517", "ANDROID+9+OOS+9.0.8+enchilada_22_O.33_190801_repack", "ANDROID+10+OOS+10.3.2+enchilada_22_J.44_200222". All MSM tools ended up with same result
Click to expand...
Click to collapse
Ok...i think you haven't tried full stock firmware which is msmdonwload tool but with 5.1.6 firmware...or you tried it?that might change everything...
Plus if that didn't worked as well...you should search for oneplus 6 fastboot roms here in xda...mauronofrio has a dedicated thread for it...search oneplus 6 fastboot rom on google and you should see an xda thread...go there download latest 10.3.3 and read all the instructions CAREFULLY...it might help you...try it and give us a feedback...
°Washy said:
Are you not able to unlock bootloader via fastboot and then flash a fastboot ROM?
Click to expand...
Click to collapse
Yes i tried it also. Download fastboot rom and copy all file to adb - platform tools v28.0.0. After clicking all-flash.bat it continuing some work and at last says "FAILED (remote: Flashing is not allowed in Lock State)"
James Blode said:
Ok...i think you haven't tried full stock firmware which is msmdonwload tool but with 5.1.6 firmware...or you tried it?that might change everything...
Plus if that didn't worked as well...you should search for oneplus 6 fastboot roms here in xda...mauronofrio has a dedicated thread for it...search oneplus 6 fastboot rom on google and you should see an xda thread...go there download latest 10.3.3 and read all the instructions CAREFULLY...it might help you...try it and give us a feedback...
Click to expand...
Click to collapse
Yes i tried it also. Download fastboot rom (9.0.9-OnePlus6Oxygen_22_OTA_034_all_1909112343_dd26-FASTBOOT) and copy all file to adb - platform tools v28.0.0. After clicking all-flash.bat it continuing some work and at last says "FAILED (remote: Flashing is not allowed in Lock State)"
I also do some nonseance work. I tried "MsmDownloadToolV4.0InternationalVersionOxygenOS5.1.5" and then enchilada_22_O.09_180517 2 times, later on "ANDROID+10+OOS+10.3.0+enchilada_22_J.42_191214". It worked!! My phone showing welcome screen. Every things seems ok. But i a few min latter realize that none of phone sensor working. So i decided switch other OOS. but 1st i unlock boot loaded. Use "fulldowngrade_wipe_MSM_17819_181025_2315_user_MP1_release.zip" role back pack via local OTA update. But its not working. stack in boot loop. Use fastboot rom "9.0.9-OnePlus6Oxygen_22_OTA_034_all_1909112343_dd26-FASTBOOT.zip". Same this goes there. stuck in boot loop. how can i get my phone sensor worked or Is there any way to role back?
zobayer.a.m said:
Yes i tried it also. Download fastboot rom (9.0.9-OnePlus6Oxygen_22_OTA_034_all_1909112343_dd26-FASTBOOT) and copy all file to adb - platform tools v28.0.0. After clicking all-flash.bat it continuing some work and at last says "FAILED (remote: Flashing is not allowed in Lock State)"
I also do some nonseance work. I tried "MsmDownloadToolV4.0InternationalVersionOxygenOS5.1.5" and then enchilada_22_O.09_180517 2 times, later on "ANDROID+10+OOS+10.3.0+enchilada_22_J.42_191214". It worked!! My phone showing welcome screen. Every things seems ok. But i a few min latter realize that none of phone sensor working. So i decided switch other OOS. but 1st i unlock boot loaded. Use "fulldowngrade_wipe_MSM_17819_181025_2315_user_MP1_release.zip" role back pack via local OTA update. But its not working. stack in boot loop. Use fastboot rom "9.0.9-OnePlus6Oxygen_22_OTA_034_all_1909112343_dd26-FASTBOOT.zip". Same this goes there. stuck in boot loop. how can i get my phone sensor worked or Is there any way to role back?
Click to expand...
Click to collapse
Did you switch on "unlock bootloader" under developer options? It could be the reason for bootloop after MSm flash.
James Blode said:
Ok...i think you haven't tried full stock firmware which is msmdonwload tool but with 5.1.6 firmware...or you tried it?that might change everything...
Plus if that didn't worked as well...you should search for oneplus 6 fastboot roms here in xda...mauronofrio has a dedicated thread for it...search oneplus 6 fastboot rom on google and you should see an xda thread...go there download latest 10.3.3 and read all the instructions CAREFULLY...it might help you...try it and give us a feedback...
Click to expand...
Click to collapse
Yes i tried it also. Download fastboot rom and copy all file to adb - platform tools v28.0.0. After clicking all-flash.bat it continuing some work and at last says "FAILED (remote: Flashing is not allowed in Lock State)"
I also do some nonsense work. I flash "MsmDownloadToolV4.0InternationalVersionOxygenOS5.1.5" and flash "enchilada_22_O.09_180517" 2 times and then flash "ANDROID+10+OOS+10.3.0+enchilada_22_J.42_191214.zip". Surprisingly it worked!! I dont know why and how it worked.
But after e few min i realize that none of my phone sensor working. I decided to role back to android 9. I unlock boot loader. Flash "fulldowngrade_wipe_MSM_17819_181025_2315_user_MP1_release" role back pack via local OTA update. But it again goes to boot loop. After that i try fastboot rom "9.0.9-OnePlus6Oxygen_22_OTA_034_all_1909112343_dd26-FASTBOOT". but again goes to boot loop. [N.B all rom i maintained in above were flash successfully]. Is there any way to get back my phone sensor worked or goes to previous version??
zobayer.a.m said:
Yes i tried it also. Download fastboot rom and copy all file to adb - platform tools v28.0.0. After clicking all-flash.bat it continuing some work and at last says "FAILED (remote: Flashing is not allowed in Lock State)"
Click to expand...
Click to collapse
you did not unlock bootbloader.and fastboot rom was completely failed.you should read on forum how to unblock bootloader,root oneplus 6.wish you success!
°Washy said:
Did you switch on "unlock bootloader" under developer options? It could be the reason for bootloop after MSm flash.
Click to expand...
Click to collapse
Negative. When I laslt flas MSM tool oos 10.3.0 boot loader was locked. I unlocked it as normal procedure (under developer opetion
turn on oem, usb debugging and other then go to fastboot mood any type command "fastboot oem unlock").
zobayer.a.m said:
Yes i tried it also. Download fastboot rom and copy all file to adb - platform tools v28.0.0. After clicking all-flash.bat it continuing some work and at last says "FAILED (remote: Flashing is not allowed in Lock State)"
I also do some nonsense work. I flash "MsmDownloadToolV4.0InternationalVersionOxygenOS5.1.5" and flash "enchilada_22_O.09_180517" 2 times and then flash "ANDROID+10+OOS+10.3.0+enchilada_22_J.42_191214.zip". Surprisingly it worked!! I dont know why and how it worked.
But after e few min i realize that none of my phone sensor working. I decided to role back to android 9. I unlock boot loader. Flash "fulldowngrade_wipe_MSM_17819_181025_2315_user_MP1_release" role back pack via local OTA update. But it again goes to boot loop. After that i try fastboot rom "9.0.9-OnePlus6Oxygen_22_OTA_034_all_1909112343_dd26-FASTBOOT". but again goes to boot loop. [N.B all rom i maintained in above were flash successfully]. Is there any way to get back my phone sensor worked or goes to previous version??
Click to expand...
Click to collapse
Flash whatever build you want...and then go to mauronofrios xda page where it has fastboot roms for op6...download the oos version that you have...and there will be one option FLASH ONLY PERSIST(FLASH PERSIST)...flash it via fastboot with oos installed and sensors should work...but for that you have to unlock your bootloader first...
Feels like you've damaged your phones critical partitions....I SAID READ MAURONOFRIOS THREAD CAREFULLY... ESPECIALLY FLASHING INSTRUCTIONS...
Wait here for a minute...
Read this carefully...i said you damaged all your phones CRITICALS...SO WHAT YOU NEED TO DO?
ALSO READ FOR THE SENSOR FLASH THAT I'VE SAID...AND TRY IT...i also had a sensor problem back in the days(touch worked...but no other sensor like proximity or gyro working)...and tried msmtool several times... didn't helped me...but this guys thread helped a lot with that...
Here is the thread also if You can't find it
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665/amp/
zobayer.a.m said:
Yes i tried it also. Download fastboot rom and copy all file to adb - platform tools v28.0.0. After clicking all-flash.bat it continuing some work and at last says "FAILED (remote: Flashing is not allowed in Lock State)"
Click to expand...
Click to collapse
you should use miniADB and fastboot tool to unlock bootbloader using instruction in forum.
fastboot rom,you only run all-flash.bat by clicking on it (not copy all files to adb-platform tool)before run the line" flash-all.bat" you should unzip file images.zip in fastboot rom.
soihuvuontrang said:
you should use miniADB and fastboot tool to unlock bootbloader using instruction in forum.
fastboot rom,you only run all-flash.bat by clicking on it (not copy all files to adb-platform tool)before run the line" flash-all.bat" you should unzip file images.zip in fastboot rom.
Click to expand...
Click to collapse
I do that and click all-flash.bat. All work perfectly on PC CMD command prompt. Successfully finish and it seems like bellow
-----
sending sparse 'vendor' 1/2 (504897 KB)...
OKAY [ 12.021s]
writing 'vendor' 1/2...
OKAY [ 0.003s]
sending sparse 'vendor' 2/2 (284097 KB)...
OKAY [ 9.762s]
writing 'vendor' 2/2...
OKAY [ 0.003s]
Setting current slot to 'b'...
OKAY [ 18.228s]
erasing 'userdata'...
OKAY [ 0.714s]
sending 'userdata' (5273 KB)...
OKAY [ 0.134s]
writing 'userdata'...
OKAY [ 0.003s]
rebooting...
finished. total time: 129.194s
Press any key to exit...
----
My phone reboot again and nothing actually happen. I stuck in boot loader as like before.
zobayer.a.m said:
I do that and click all-flash.bat. All work perfectly on PC CMD command prompt. Successfully finish and it seems like bellow
-----
sending sparse 'vendor' 1/2 (504897 KB)...
OKAY [ 12.021s]
writing 'vendor' 1/2...
OKAY [ 0.003s]
sending sparse 'vendor' 2/2 (284097 KB)...
OKAY [ 9.762s]
writing 'vendor' 2/2...
OKAY [ 0.003s]
Setting current slot to 'b'...
OKAY [ 18.228s]
erasing 'userdata'...
OKAY [ 0.714s]
sending 'userdata' (5273 KB)...
OKAY [ 0.134s]
writing 'userdata'...
OKAY [ 0.003s]
rebooting...
finished. total time: 129.194s
Press any key to exit...
----
My phone reboot again and nothing actually happen. I stuck in boot loader as like before.
Click to expand...
Click to collapse
it's quite strange.Did you unzipped the file"IMAGES.ZIP"?
---------- Post added at 10:31 AM ---------- Previous post was at 10:27 AM ----------
zobayer.a.m said:
My one plus 6 device suddenly bricked without any sign. Shows only boot loader screen. I can reach recovery mood. I wiped all data (I select "erase everything(Music, pics, etc). Then I tried MSM tool (Run as administrator). After complete download it reboot again and wait for 1/2 min. It gose again to boot loop. Then I tried fastboot method. It said "failed to load 'images.zip': Not enough space". I try to wipe data by command "fastboot erase userdata". It said "FAILED (remote: Erase is not allowed in Lock State)". Also run "flash-all.bat" and it said "FAILED (remote: Flashing is not allowed in Lock State)". Nothing happen on my phone screen. Typed "fastboot continue" and it goes to boot loop. Now I stacked in boot loop screen. What should i do now??
Click to expand...
Click to collapse
error at"images.zip" it means that you have to unzip the file images.zip.
Hello, someone have bootloader unlocked and Is willing to try Lineage OS?
Here is the roms: Lineage OS 16.x, 17.x, 18.x
Download the a/b versión (treble_arm64_bv)
no root needed or twrp, just bootloader unlocked and a pc.
If someone tried, please let me know!
Did you try to install any GSI rom ???
works with all gsi? so I test
Niick.Ok said:
works with all gsi? so I test
Click to expand...
Click to collapse
Yes, should work with any GSI roms, please Let me know if you tried!
Someone tried this? I dont know how to install the rom, but i've already installed twrp
CæsarAM said:
Someone tried this? I dont know how to install the rom, but i've already installed twrp
Click to expand...
Click to collapse
For install roms, you need the stock recovery.
Here is a mini tutorial If anyone want yo try it!
start the phone in fastboot mode, then connect to the computer via USB.
enter at the PC: fastboot reboot fastboot
when the phone is restarted, fastbootd (look for the “d” at the end of fastboot) should appear.
now type: fastboot flash system image-name.img (e.g. lineage-17.1-20210615-UNOFFICIAL-treble_arm64_bvS.img)
when all this is finished, type: fastboot reboot recovery
in the original recovery, go to delete all data, then restart the phone.
The first start take while, please be patient! Enjoy!
SaocMc said:
For install roms, you need the stock recovery.
Here is a mini tutorial If anyone want yo try it!
start the phone in fastboot mode, then connect to the computer via USB.
enter at the PC: fastboot reboot fastboot
when the phone is restarted, fastbootd (look for the “d” at the end of fastboot) should appear.
now type: fastboot flash system image-name.img (e.g. lineage-17.1-20210615-UNOFFICIAL-treble_arm64_bvS.img)
when all this is finished, type: fastboot reboot recovery
in the original recovery, go to delete all data, then restart the phone.
The first start take while, please be patient! Enjoy!
Click to expand...
Click to collapse
Don't works for this phone, when I flash the system image it says "FAILED (remote: 'Not enough space to resize partition')". I think it's because this device has dynamic partitions
CæsarAM said:
Don't works for this phone, when I flash the system image it says "FAILED (remote: 'Not enough space to resize partition')". I think it's because this device has dynamic partitions
Click to expand...
Click to collapse
yes, because of it, you need to flash via fastbootd
After some research, this could be a posible solution:
flash the stock vbmeta with fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
deleted product partition with fastboot delete-logical-partition product
flash the rom with fastboot flash --u system lineage-17.1-20210615-UNOFFICIAL-treble_arm64_bvS.img
Factory reset from recovery
you can extract the vbmeta file from stock rom, https://mirrors.lolinet.com/firmware/moto/astro/official/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
same error
I tried to install the gsi roms with the new recovery that they released for this phone and it didn't let me erase the system partition, I couldn't install the gsi image either, none of the three recovery variants that they released worked for me
Niick.Ok said:
I tried to install the gsi roms with the new recovery that they released for this phone and it didn't let me erase the system partition, I couldn't install the gsi image either, none of the three recovery variants that they released worked for me
Click to expand...
Click to collapse
because this device has dynamic partitions, can't install rom via recovery, only via fastbootd, but seems the lineage OS is larger than the system partition of our device, so we need to find a lighter rom or keep searching a solution
What size would the rom need? And another query, how is fastboot mode different from fastbootd mode? I see that the D is attached to the end many
Niick.Ok said:
What size would the rom need? And another query, how is fastboot mode different from fastbootd mode? I see that the D is attached to the end many
Click to expand...
Click to collapse
Basically, Fastbootd is a newer version of fastboot.
fastboot -w (warning : this will wipe all your data)
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot reboot
This steps are how fusion+ flash GSI roms(Copied from here: https://forum.xda-developers.com/t/rom-11-official-omnirom-liber.4232413/), the boot, dtbo and vmeta files are from stock rom, If anyone wants to try this, please let me know! Remember you need stock recovery and a factory reset after flashing the rom
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system Havoc-OS-v4.1-20210208-arm64-ab-Official.img
target reported max download size of 536870912 bytes
sending sparse 'system_a' 1/6 (458752 KB)...
OKAY [ 14.145s]
writing 'system_a' 1/6...
OKAY [ 2.422s]
sending sparse 'system_a' 2/6 (458752 KB)...
OKAY [ 14.199s]
writing 'system_a' 2/6...
OKAY [ 2.429s]
sending sparse 'system_a' 3/6 (458752 KB)...
OKAY [ 14.093s]
writing 'system_a' 3/6...
FAILED (remote: Operation not permitted)
finished. total time: 47.854s
Niick.Ok said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system Havoc-OS-v4.1-20210208-arm64-ab-Official.img
target reported max download size of 536870912 bytes
sending sparse 'system_a' 1/6 (458752 KB)...
OKAY [ 14.145s]
writing 'system_a' 1/6...
OKAY [ 2.422s]
sending sparse 'system_a' 2/6 (458752 KB)...
OKAY [ 14.199s]
writing 'system_a' 2/6...
OKAY [ 2.429s]
sending sparse 'system_a' 3/6 (458752 KB)...
OKAY [ 14.093s]
writing 'system_a' 3/6...
FAILED (remote: Operation not permitted)
finished. total time: 47.854s
Click to expand...
Click to collapse
Can you double check that your bootloader is unlocked and you are flashing vía fastbootd?
Some users report that error is caused by the bootloader locked, maybe, somehow your bootloader got locked again.
That's what I thought, when I got that error yesterday I tried to unlock the bootloader again, I tried via fastbootd and it didn't let me, I had to do it from the bootloader menu and there it left me, from fastbootd it told me that it did not know the commands, (summarizing I tried to unlock the bootloader again from the fastbootd menu and it wouldn't let me, so I tried from bootloader and it left me, but it told me that it was already unlocked, any other solution?
I think I already found the problem yesterday when trying to install gsi, yesterday wn fastbootd it appeared (secure boot = yes) I flashed the vbmeta of the official rom and I did not deactivate it, I would need you to pass me a modified vbmeta to flash it and deactivate the secure boot, from there I try to flash again, 2- another possible solution I think would be flashing magisk, see if it manages to pass that verification (secure boot = yes) by modifying the boot. In any case, I would need your help to achieve the modified vbmeta
Niick.Ok said:
I think I already found the problem yesterday when trying to install gsi, yesterday wn fastbootd it appeared (secure boot = yes) I flashed the vbmeta of the official rom and I did not deactivate it, I would need you to pass me a modified vbmeta to flash it and deactivate the secure boot, from there I try to flash again, 2- another possible solution I think would be flashing magisk, see if it manages to pass that verification (secure boot = yes) by modifying the boot. In any case, I would need your help to achieve the modified vbmeta
Click to expand...
Click to collapse
I found this tutorial: https://forum.hovatek.com/thread-32719.html
Method 3 is for flash a empty vmeta and disable verification.
You can try with both, the stock vmeta or the empty one.
I tried everything and I could not, I will wait for a developer to find a way, or for a rom to come out for this cell phone, I already tried the three methods that you sent me and more
SaocMc said:
Can you double check that your bootloader is unlocked and you are flashing vía fastbootd?
Some users report that error is caused by the bootloader locked, maybe, somehow your bootloader got locked again.
Click to expand...
Click to collapse
I get the exact same error no matter the GSI I try, bootloader is unlocked, flashing using fastbootd, I already hate this device...