Related
Hi,
I was trying to install the cyanogenmod 11 on my device. I have successfully unlocked the boot loader and installed the clockworkmod recovery, but I copied the zip files into the sdcard instead of the root folder. When I tied to install the cyanogenmod 11 from the recovery mode, I could not find the zip file in the device, so I powered off my phone thinking I could start again, but when I have turned the phone on the screen was stuck on the HTC logo.
And now I do not know what to do. Can you help?
Thanks in advance !
AndySOS said:
Hi,
I was trying to install the cyanogenmod 11 on my device. I have successfully unlocked the boot loader and installed the clockworkmod recovery, but I copied the zip files into the sdcard instead of the root folder. When I tied to install the cyanogenmod 11 from the recovery mode, I could not find the zip file in the device, so I powered off my phone thinking I could start again, but when I have turned the phone on the screen was stuck on the HTC logo.
And now I do not know what to do. Can you help?
Thanks in advance !
Click to expand...
Click to collapse
Did you wipe the device prior to install? Can you still access bootloader and recovery?
If you can get into bootloader, what version of HBOOT does it say? What version of CWM are you using. BTW, in my limited experience TWRP is better for this device. Version 2.7.1.1 works well for me.
jollywhitefoot said:
Did you wipe the device prior to install? Can you still access bootloader and recovery?
If you can get into bootloader, what version of HBOOT does it say? What version of CWM are you using. BTW, in my limited experience TWRP is better for this device. Version 2.7.1.1 works well for me.
Click to expand...
Click to collapse
Yes I did wipe all the data, but I did not installed the pack. I turned off the device.
I can access the bootloader but if I try to get into Recovery it brings me back to the bootloader menu.
The HBOOT version is 2.22.0000, and I have installed the CMM. 6.0.3.6
I have tried to install the TWRP but it did not work.
AndySOS said:
Yes I did wipe all the data, but I did not installed the pack. I turned off the device.
I can access the bootloader but if I try to get into Recovery it brings me back to the bootloader menu.
The HBOOT version is 2.22.0000, and I have installed the CMM. 6.0.3.6
I have tried to install the TWRP but it did not work.
Click to expand...
Click to collapse
6.0.3.6 is really old and problably not compatible with your current configuration.
what do you mean TWRP didn't work? Does it not flash? What message do you get in command window when you try to flash it? If it does flash, can you enter TWRP?
HBOOT 2.22 means you're likely on a new partition layout, that was released around April of this year. You shouldn't use any recoveries or ROMs that were released before summer. And with ROMs, you should find out if they are for new or old layout before you flash them.
jollywhitefoot said:
6.0.3.6 is really old and problably not compatible with your current configuration.
what do you mean TWRP didn't work? Does it not flash? What message do you get in command window when you try to flash it? If it does flash, can you enter TWRP?
HBOOT 2.22 means you're likely on a new partition layout, that was released around April of this year. You shouldn't use any recoveries or ROMs that were released before summer. And with ROMs, you should find out if they are for new or old layout before you flash them.
Click to expand...
Click to collapse
Yeah TWRP doest flash, and I got something like that: recovery.img cannot/won't start. I believe I had the wrong version.
I was thinking to delete the current custom recovery and to install another one...
AndySOS said:
Yeah TWRP doest flash, and I got something like that: recovery.img cannot/won't start. I believe I had the wrong version.
I was thinking to delete the current custom recovery and to install another one...
Click to expand...
Click to collapse
When you flash a new recovery it will overwrite the existing one.
What message exactly do you get when you try to flash twrp?
Is fastboot working properly? Does it say Fastboot "USB"? When you type Fastboot devices in command window, does it show your device?
jollywhitefoot said:
When you flash a new recovery it will overwrite the existing one.
What message exactly do you get when you try to flash twrp?
Is fastboot working properly? Does it say Fastboot "USB"? When you type Fastboot devices in command window, does it show your device?
Click to expand...
Click to collapse
It says that." fastboot is not working proprely" . And yes it does show my device.
AndySOS said:
It says that." fastboot is not working proprely" . And yes it does show my device.
Click to expand...
Click to collapse
Can you paste the results from the command window when you try to flash twrp?
Can you paste the results from the command window when you type "fastboot devices"?
What is your computer OS?
jollywhitefoot said:
Can you paste the results from the command window when you try to flash twrp?
Can you paste the results from the command window when you type "fastboot devices"?
What is your computer OS?
Click to expand...
Click to collapse
C:\Android\Unlock Folder>fastboot flash recovery twrp-2.7.1.2-m4
error: cannot load 'twrp-2.7.1.2-m4'
and
C:\Android>fastboot devices
HT3ABWA00119 fastboot
And I have Windows 8.1
AndySOS said:
C:\Android\Unlock Folder>fastboot flash recovery twrp-2.7.1.2-m4
error: cannot load 'twrp-2.7.1.2-m4'
and
C:\Android>fastboot devices
HT3ABWA00119 fastboot
And I have Windows 8.1
Click to expand...
Click to collapse
on your flash command, you forgot to include the file extension. it should be "twrp-2.7.1.2-m4.img"
jollywhitefoot said:
on your flash command, you forgot to include the file extension. it should be "twrp-2.7.1.2-m4.img"
Click to expand...
Click to collapse
It still says the same thing.
C:\Android\Unlock Folder>fastboot flash recovery twrp-2.7.1.2-m4.img
error: cannot load 'twrp-2.7.1.2-m4.img'
AndySOS said:
It still says the same thing.
C:\Android\Unlock Folder>fastboot flash recovery twrp-2.7.1.2-m4.img
error: cannot load 'twrp-2.7.1.2-m4.img'
Click to expand...
Click to collapse
Where did you get that file? I don't see 2.7.1.2 as an official version for our device.
Try downloading 2.7.1.1 from here:
http://techerrata.com/browse/twrp2/m4ul
jollywhitefoot said:
Where did you get that file? I don't see 2.7.1.2 as an official version for our device.
Try downloading 2.7.1.1 from here:
http://techerrata.com/browse/twrp2/m4ul
Click to expand...
Click to collapse
Still, the same thing
C:\Android\Unlock Folder>fastboot flash recovery openrecovery-twrp-2.7.1.1-m4.img
error: cannot load 'openrecovery-twrp-2.7.1.1-m4.img'
AndySOS said:
Still, the same thing
C:\Android\Unlock Folder>fastboot flash recovery openrecovery-twrp-2.7.1.1-m4.img
error: cannot load 'openrecovery-twrp-2.7.1.1-m4.img'
Click to expand...
Click to collapse
Fastboot simply isn't finding the file for whatever reason. can you post a dir of the C:\Android\Unlock Folder?
Do you have Windows set to not show file extension in Explorer? You might want to change it to show extensions to make sure the TWRP file is being saved with the .img extension.
Another thing to try would be to rename the twrp recovery file to just "recovery.img" to reduce the number of variables.
jollywhitefoot said:
Fastboot simply isn't finding the file for whatever reason. can you post a dir of the C:\Android\Unlock Folder?
Do you have Windows set to not show file extension in Explorer? You might want to change it to show extensions to make sure the TWRP file is being saved with the .img extension.
Another thing to try would be to rename the twrp recovery file to just "recovery.img" to reduce the number of variables.
Click to expand...
Click to collapse
I did it. I just had to change to show the extensions. XD
C:\Android\Unlock Folder>fastboot flash recovery openrecovery-twrp-2.7.1.1-m4.img
target reported max download size of 800227328 bytes
sending 'recovery' (9432 KB)...
OKAY [ 1.179s]
writing 'recovery'...
OKAY [ 2.302s]
finished. total time: 3.489s
AndySOS said:
I did it. I just had to change to show the extensions. XD
C:\Android\Unlock Folder>fastboot flash recovery openrecovery-twrp-2.7.1.1-m4.img
target reported max download size of 800227328 bytes
sending 'recovery' (9432 KB)...
OKAY [ 1.179s]
writing 'recovery'...
OKAY [ 2.302s]
finished. total time: 3.489s
Click to expand...
Click to collapse
ok. cool. Now...once you enter recovery, you need to see if ADB works, or do you have an OTG device? Either way, you need to download a ROM to your computer then either push it to your device using ADB or OTG. I'd probably start out with this stock ROM (http://forum.xda-developers.com/htc...-official-stock-sense-6-rom-firmware-t2817921) so you can boot back into OS. Once you can boot into OS, you can make a TWRP backup, then flash CM or whatever else you want.
jollywhitefoot said:
ok. cool. Now...once you enter recovery, you need to see if ADB works, or do you have an OTG device? Either way, you need to download a ROM to your computer then either push it to your device using ADB or OTG. I'd probably start out with this stock ROM (http://forum.xda-developers.com/htc...-official-stock-sense-6-rom-firmware-t2817921) so you can boot back into OS. Once you can boot into OS, you can make a TWRP backup, then flash CM or whatever else you want.
Click to expand...
Click to collapse
Yeah about that... i have already done that and I have insatlled the CM 11 and its currently processing.
Thank you for your help ! XD XD
U just saved my phone
AndySOS said:
Yeah about that... i have already done that and I have insatlled the CM 11 and its currently processing.
Thank you for your help ! XD XD
U just saved my phone
Click to expand...
Click to collapse
ok. cool. no problem. glad you got it working.
Hey guys,
I wanted to have the Android 5.1 update so I looked up how I can do this.
I ended up at a youtube video called ''How to Install OFFICIAL Android 5.1 Lollipop GPe on Moto G [XT1033 & XT1032]'' by Samanyou Garg.
I did the first thing he said with the file called 5.x to 4.4.4 gpe. after I did this my phone didn't boot up. Now i'm stuck at th bootloader menu and if i try anything it says ''boot up failed''
Please help me with this problem, im stuck for 4 days right now! and I really need my phone tommorow.
poolta321 said:
Hey guys,
I wanted to have the Android 5.1 update so I looked up how I can do this.
I ended up at a youtube video called ''How to Install OFFICIAL Android 5.1 Lollipop GPe on Moto G [XT1033 & XT1032]'' by Samanyou Garg.
I did the first thing he said with the file called 5.x to 4.4.4 gpe. after I did this my phone didn't boot up. Now i'm stuck at th bootloader menu and if i try anything it says ''boot up failed''
Please help me with this problem, im stuck for 4 days right now! and I really need my phone tommorow.
Click to expand...
Click to collapse
Flash a custom recovery and wipe system ,data,dalvik and cache then flash cm 12.1 nightly
sjandroiddeveloper said:
Flash a custom recovery and wipe system ,data,dalvik and cache then flash cm 12.1 nightly
Click to expand...
Click to collapse
I tried to flash TWRP but when I put ''adb devices'' in cmd it doesn't come up with my device
update: wait It does work now with fastboot devices
poolta321 said:
I tried to flash TWRP but when I put ''adb devices'' in cmd it doesn't come up with my device
update: wait It does work now with fastboot devices
Click to expand...
Click to collapse
Okay I flashed TWRP but when I do recovery It still says Boot up failed
poolta321 said:
Okay I flashed TWRP but when I do recovery It still says Boot up failed
Click to expand...
Click to collapse
First if all don't do things you don't know about, just watching a random YouTube videos and following is a stupid thing
Now try this
In fastboot mode enter following commands
fastboot erase recovery
fastboot flash recovery recovery.img
---------- Post added at 12:24 PM ---------- Previous post was at 12:23 PM ----------
And why did you make 4 threads for the same thing
Dont spam please
sjandroiddeveloper said:
First if all don't do things you don't know about, just watching a random YouTube videos and following is a stupid thing
Now try this
In fastboot mode enter following commands
fastboot erase recovery
fastboot flash recovery recovery.img
---------- Post added at 12:24 PM ---------- Previous post was at 12:23 PM ----------
And why did you make 4 threads for the same thing
Dont spam please
Click to expand...
Click to collapse
sorry for the many threads.
I did what you said and reflashed TWRP but it still says Boot up failed when I go to recovery
poolta321 said:
sorry for the many threads.
I did what you said and reflashed TWRP but it still says Boot up failed when I go to recovery
Click to expand...
Click to collapse
When you flash recovery what does it say on phone's fastboot screen
sjandroiddeveloper said:
When you flash recovery what does it say on phone's fastboot screen
Click to expand...
Click to collapse
cmd: getvarartition-type:recovery
cmd: erase:recovery
cmd: getvarartition-type recovery
cmd: getvar:max-download-size
cmd: download:007b1800
cmd: flash: recovery
Mismatched partition size (recovery)
Boot up failed
poolta321 said:
cmd: getvarartition-type:recovery
cmd: erase:recovery
cmd: getvarartition-type recovery
cmd: getvar:max-download-size
cmd: download:007b1800
cmd: flash: recovery
Mismatched partition size (recovery)
Boot up failed
Click to expand...
Click to collapse
lol didn't mean to put the smileys there
poolta321 said:
lol didn't mean to put the smileys there
Click to expand...
Click to collapse
Try to flash Philz
And if that doesnt work out then flash the stock 5.0.2 Asian firmware for xt1033
That's the only thing you can do
sjandroiddeveloper said:
Try to flash Philz
And if that doesnt work out then flash the stock 5.0.2 Asian firmware for xt1033
That's the only thing you can do
Click to expand...
Click to collapse
tried Philz and it still says Mismatching partition and boot up failed
Tried stock 5.0.2 Asian firmware for xt1033 but it didn't do anything. on cmd I typed the code but nothing came up
poolta321 said:
tried Philz and it still says Mismatching partition and boot up failed
Tried stock 5.0.2 Asian firmware for xt1033 but it didn't do anything. on cmd I typed the code but nothing came up
Click to expand...
Click to collapse
Mismatch partition size will always occur while flashing a custom recovery, no need to worry about it
And what do you mean nothing came up when you typed commands
Some output must have come
sjandroiddeveloper said:
Mismatch partition size will always occur while flashing a custom recovery, no need to worry about it
And what do you mean nothing came up when you typed commands
Some output must have come
Click to expand...
Click to collapse
image is in attachments.
this happens for all the codes i type via mfastboot.exe
poolta321 said:
image is in attachments.
this happens for all the codes i type via mfastboot.exe
Click to expand...
Click to collapse
Wait it works right now.
I didn't knew I needed to paste the mfasboot in the SDK folder
poolta321 said:
Wait it works right now.
I didn't knew I needed to paste the mfasboot in the SDK folder
Click to expand...
Click to collapse
Okay it finished. but still doesn't do anything.....
It still says Boot up failed an when I try to turn it on it says Fastboot Reason: Fall-trough from normal boot mode
poolta321 said:
Okay it finished. but still doesn't do anything.....
It still says Boot up failed an when I try to turn it on it says Fastboot Reason: Fall-trough from normal boot mode
Click to expand...
Click to collapse
I think your bootloader is corrupted or something like that
sjandroiddeveloper said:
I think your bootloader is corrupted or something like that
Click to expand...
Click to collapse
Is there a way to fix it?
poolta321 said:
Is there a way to fix it?
Click to expand...
Click to collapse
There are plenty of people who have killed their phones by doing something the result of which was corrupt bootloader
And sadly there is no way to fix it
sjandroiddeveloper said:
There are plenty of people who have killed their phones by doing something the result of which was corrupt bootloader
And sadly there is no way to fix it
Click to expand...
Click to collapse
So my phone is broke?
poolta321 said:
So my phone is broke?
Click to expand...
Click to collapse
Technically its called hardbricked
I unlocked the bootloader and rooted with Magisk following this guide: https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
Since than my phone is stuck on the Google boot screen.
I'm able to get the phone into fastboot mode and initiate 'fastboot update image' or 'flash-all.bat' unfortunately the restore fails every time on this step: Sending sparse 'vendor_a' 1/2 (262140 KB) FAILED (Error reading sparse file)
I'm out of options and pretty desperate, please help!
I'm using a Pixel 3 64GB (unlocked EU edition), Laptop is on Windows 10. The phone and laptop are connected with the stock USB-C cable.
luzero said:
I unlocked the bootloader and rooted with Magisk following this guide: https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
Since than my phone is stuck on the Google boot screen.
I'm able to get the phone into fastboot mode and initiate 'fastboot update image' or 'flash-all.bat' unfortunately the restore fails every time on this step: Sending sparse 'vendor_a' 1/2 (262140 KB) FAILED (Error reading sparse file)
I'm out of options and pretty desperate, please help!
I'm using a Pixel 3 64GB (unlocked EU edition), Laptop is on Windows 10. The phone and laptop are connected with the stock USB-C cable.
Click to expand...
Click to collapse
Flash the stock boot image to both slots with fastboot. You can extract it from the factory image you downloaded.
Code:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
robocuff said:
Flash the stock boot image to both slots with fastboot. You can extract it from the factory image you downloaded.
Code:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Click to expand...
Click to collapse
Hi Robocuff,
Thank you for your suggestion.
I successfully managed to perform the boot_a and boot_b flash. Afterwards I restarted my device and retried to fastboot the original image and again the process fails with the same error. (Vendor_A FAILED (Error reading sparse file).
Any suggestions how to restore the device? And safe my day ?
luzero said:
Hi Robocuff,
Thank you for your suggestion.
I successfully managed to perform the boot_a and boot_b flash. Afterwards I restarted my device and retried to fastboot the original image and again the process fails with the same error. (Vendor_A FAILED (Error reading sparse file).
Any suggestions how to restore the device? And safe my day [emoji4]
Click to expand...
Click to collapse
Do you have the latest sdk tools, fastboot and adb?
Sent from my [device_name] using XDA-Developers Legacy app
luzero said:
Hi Robocuff,
Thank you for your suggestion.
I successfully managed to perform the boot_a and boot_b flash. Afterwards I restarted my device and retried to fastboot the original image and again the process fails with the same error. (Vendor_A FAILED (Error reading sparse file).
Any suggestions how to restore the device? And safe my day ?
Click to expand...
Click to collapse
Did the boot flashes complete successfully? If so, did you allow the phone to attempt to boot to the OS after you restarted it or did you just reboot directly to fastboot mode? Flashing the stock bootloader should have fixed the issue of the phone not booting. That said, if it still won't boot after flashing the stock bootloader, make sure your fastboot files are up to date. Outdated files can cause issues like you're having while flashing the factory image. You can get the latest files here. If that doesn't do it, try a different usb port. Also cables can sometimes be a problem so you might want to try another cable also.
Flashing the stock boot image to both slots, boot_a and boot_b should solve the problem. I don't think it's a bootloader issue. The boot image includes the stock recovery as well as the kernel.
Sent from my [device_name] using XDA-Developers Legacy app
Yes the boot flashes where performed successfully and I tried to start the device. I just redid the boot flashes and waited longer to double check if I was too impatient.
Yesterday I downloaded the latest files of everything as linked in the above referred to Magisk flash guide on xda developers.
Later tonight I will try to redonwload all the latest files and double check everything.
I only have one usb type c port on my laptop. I will also try the regular USB port to.
Thank you all for your contributions. Really appreciated!
jd1639 said:
Flashing the stock boot image to both slots, boot_a and boot_b should solve the problem. I don't think it's a bootloader issue. The boot image includes the stock recovery as well as the kernel.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
You mean:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
I tried and although successful unfortunately still stuck at the google logo.
luzero said:
You mean:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
I tried and although successful unfortunately still stuck at the google logo.
Click to expand...
Click to collapse
Try flashing the system image. Again, to both slots like you did for the boot image, which you did correctly.
Sent from my [device_name] using XDA-Developers Legacy app
It's working again! Thank you so much guys.
In the end I managed to run flash-all using an USB type a to c cable.
Really appreciated your advise!
luzero said:
It's working again! Thank you so much guys.
In the end I managed to run flash-all using an USB type a to c cable.
Really appreciated your advise!
Click to expand...
Click to collapse
Glad to hear you got it up and running again.
What's "flash all?"
BrickMe?Naw said:
What's "flash all?"
Click to expand...
Click to collapse
flash-all is the batch file included with the full image .zip. Ran from a command prompt it reinstalls the image. Deleting the -w (for wipe) from the text file and saving/running will keep the user files, apps etc. intact while installing.
BrickMe?Naw said:
What's "flash all?"
Click to expand...
Click to collapse
Here you find an easy guide to explain the appropriate steps:
https://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478
luzero said:
It's working again! Thank you so much guys.
In the end I managed to run flash-all using an USB type a to c cable.
Really appreciated your advise!
Click to expand...
Click to collapse
I am experiencing this same issue and unfortunately this did not work for me.
I am using the latest SDK tools, have tried two different cables in two different USB ports and always have a flash-all fail at the exact same step as the OP.
Anyone have any other suggestions I can try?
BluhmJA said:
I am experiencing this same issue and unfortunately this did not work for me.
I am using the latest SDK tools, have tried two different cables in two different USB ports and always have a flash-all fail at the exact same step as the OP.
Anyone have any other suggestions I can try?
Click to expand...
Click to collapse
I had the same problem and fixed it specifically by switching to a slower USB 2 port. I guess the USB 3 was exposing a timing bug?
I am stuck in fastboot. The bootloader is unlocked and I do not have twrp. Everytime I try to install twrp I get this message "FAILED (remote: Failed to load/authenticate boot image: Load Error)" I think it is because my boot image is not there.
When I try to install factory boot image (fastboot flash boot.img) I get this message:
PS C:\platform-tools> fastboot flash C:\Users\Admin\Downloads\boot_stock.img
unknown partition 'C:\Users\Admin\Downloads\boot_stock.img'
error: cannot determine image filename for 'C:\Users\Admin\Downloads\boot_stock.img'
HELP PLEASE
fastboot flash boot boot.img
u missed the boot partition
Bradl79 said:
fastboot flash boot boot.img
u missed the boot partition
Click to expand...
Click to collapse
Just tried and it looks to have flashed, but I am still stuck in bootloader/fastboot menu
here is the output:
PS C:\platform-tools> fastboot devices
efba8ca6 fastboot
PS C:\platform-tools> fastboot flash boot C:\Users\Admin\Downloads\boot_stock.img
target reported max download size of 805306368 bytes
sending 'boot' (98304 KB)...
OKAY [ 2.118s]
writing 'boot'...
OKAY [ 0.393s]
finished. total time: 2.520s
did you flash the correct boot.img for the correct phone model and os version?
you may just want to flash the fastboot rom
Bradl79 said:
did you flash the correct boot.img for the correct phone model and os version?
you may just want to flash the fastboot rom
Click to expand...
Click to collapse
Thank you! That fixed my problem. I flashed 10.0.1-GM21BA-OnePlus7ProOxygen_21.E.21_OTA_021_all_1910071445_8d6a-FASTBOOT
Now I'm back to stock and not rooted. Good thing I backed up my software before flashing.
What's the easiest way to gain root access again? Which specific files do I need?
My phone is GM1917 on Android 10 Oxygen OS 10.01.GM21BA
champstar said:
Now I'm back to stock and not rooted.
Click to expand...
Click to collapse
That is what flashing a stock boot.img does. What were you trying to accomplish by flashing stock boot.img?
champstar said:
Now I'm back to stock and not rooted.
What's the easiest way to gain root access again? Which specific files do I need?
Click to expand...
Click to collapse
Fastboot boot TWRP, then flash Magisk zip.
Use TWRP unofficial version -70 if you are on Android Q.
redpoint73 said:
That is what flashing a stock boot.img does. What were you trying to accomplish by flashing stock boot.img?
Fastboot boot TWRP, then flash Magisk zip.
Use TWRP unofficial version -70 if you are on Android Q.
Click to expand...
Click to collapse
Thank you! I am now rooted again. There's so much information available online, it is hard to nail down exactly what to do once something messes up.
Now my wifi is not working. I flashed the stock boot image so my kernel should be back to stock right?
I am on TWRP 3.3.1-70 and Magisk is up to date.
champstar said:
Now my wifi is not working. I flashed the stock boot image so my kernel should be back to stock right?
I am on TWRP 3.3.1-70 and Magisk is up to date.
Click to expand...
Click to collapse
Broken wifi probably means you flashed the wrong stock boot.img.
redpoint73 said:
Broken wifi probably means you flashed the wrong stock boot.img.
Click to expand...
Click to collapse
That did the trick, I flashed modded magisk for OS 10 and now wifi is working.
Hey , I did EFS backup.
I have my stock modemst1.bin and modemst2.bin.
When i try to flash them over fastboot i get this.
J:\platform-tools>fastboot flash modemst1 modemst1.bin
Sending 'modemst1' (2048 KB) OKAY [ 0.067s]
Writing 'modemst1' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Click to expand...
Click to collapse
I'm running OOS 11.0.1.1.
Did u tried in fastboot or fastbootd ?
Mr.Anderson187 said:
Did u tried in fastboot or fastbootd ?
Click to expand...
Click to collapse
Can you explain what fastbootd is? How is it accessed? How is it used?
To access the critical partitions u need to do "fastboot reboot fastboot" so u boot into fastboot from fastboot. Then u access fastbootd, the demon that life's in it. Here u can flash partitions like system, vendor, product
Mr.Anderson187 said:
To access the critical partitions u need to do "fastboot reboot fastboot" so u boot into fastboot from fastboot. Then u access fastbootd, the demon that life's in it. Here u can flash partitions like system, vendor, product
Click to expand...
Click to collapse
I'm flashing boot.img from fastboot tho
yot2703 said:
I'm flashing boot.img from fastboot tho
Click to expand...
Click to collapse
Yes partitions like boot can easily flashed via fastboot, but "critical" partitions like system, vendor, product can only flashed via fastbootd.
yot2703 said:
Hey , I did EFS backup.
I have my stock modemst1.bin and modemst2.bin.
When i try to flash them over fastboot i get this.
I'm running OOS 11.0.1.1.
Click to expand...
Click to collapse
t-mobile or Verizon
yot2703 said:
Hey , I did EFS backup.
I have my stock modemst1.bin and modemst2.bin.
When i try to flash them over fastboot i get this.
I'm running OOS 11.0.1.1.
Click to expand...
Click to collapse
could you send the files?
L0ckl37r said:
could you send the files?
Click to expand...
Click to collapse
Oh wow, I don't have them anymore.
It's been a few years since I've posted these.
I'd recommend you to msm your device and backup then again.
I don't think anyone is running this version of oxygen os nowadays.