Bootloader is unlocked. When I try to run fastboot erase modemst1 it returns failed because it can't erase critical partitions.
You need to boot into fastbootd. Try in adb type "adb reboot fastboot", it will reboot to fastbootd. Then should be able erase modemst1.
Thanks
Related
Please help.:crying:
I did the below fastboot commands
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot reboot-bootloader
All gave me success.
But I am not able to do any of the below commands
fastboot flash bootloader bootloader-crespo-i9020xxlc2.img
fastboot flash radio radio-crespo-i9020xxki1.img
fastboot flash recovery recovery-clockwork-touch-6.0.3.1-crespo.img
fastboot -w update image-soju-jzo54k.zip
all i get is "error: cannot load 'bootloader-crespo-i9020xxkl1.img': Unknown error"
Wheareas in the mobile, i get an error:
FASTBOOT STATUS - FAILInvalid Argument
Try to use correct radio
Sent from my Nexus S using xda premium
I manually unlocked my bootloader and began the process of installing TWRP and then Cyanogenmod. After playing with Cyanogenmod I realized I wasn't missing much, so I tried to go back to Lollipop / Marshmallow only to discover that now every time I boot up my phone it immediately goes to the bootloader, requiring me to manually start my phone. If I try to factory reset it does the same thing. I can reinstall TWRP, but the resulting flash will not allow me to flash custom roms or do much more than click buttons that won't do anything. I cannot get TWRP to export my log to the SD card so I can share the issues. Here is what I have noticed:
1. I have no cache directory according to TWRP.
2. If I try to flash a custom rom, IE Cyanogenmod, it reboots recovery and I don't see an error until I attempt to go back and reflash. Again, I cannot export a log file that will open or allow me to copy it to a different directory.
3. No matter what operation I try to perform, rebooting the device always puts it back to the bootloader. I have to manually start my phone from the menu.
Is there something I should be doing differently? Should I try and flash down to Cyanogenmod 12.1 and then go back to Lollipop? Is the previous upgrade to Marshmallow screwing things up?
Hmm... can you try to flash firmware again? For now skip factory reset in recovery. You can do it later. Flash the latest Marshmallow firmware in bootloader mode:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
If you want to flash lollipop you must skip partition and bootloader. It might cause bootloop which you will not be able to fix:
fastboot oem fb_mode_set
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
If your phone goes to the bootloader mode every boot, then you didn't close fb_oem mode, when in the bootloader send the command "fastboot oem fb_mode_clear", you should get an OK. Reboot and you should be good to go.
Your phone reboot to system but every reboot it goes first to bootloader or only bootloader is loaded and you can't boot to system? If first then do what @acejavelin said. If system is not loaded then flash firmware again.
<bootloader/ has-slot:system: not found?
I can flash firmware again, but from there it's still acting up. I also cannot do fastboot oem lock.
Now I'm told the storage is in RAW format?
So here's what I did
Code:
sudo fastboot erase modem
sudo fastboot erase sbl1
sudo fastboot erase dbi
sudo fastboot erase aboot
sudo fastboot erase rpm
sudo fastboot erase tz
sudo fastboot erase LOGO
sudo fastboot erase oppostanvbk
sudo fastboot erase boot
sudo fastboot erase cache
sudo fastboot erase recovery
sudo fastboot erase system
sudo fastboot erase userdata
Now I can't even manage to boot the phone in fastboot mode... I guess I truly fracked it up.
Is there a way to recover it or it's truly bricked?
Can Oneplus Service center help?
dipakmdhrm said:
So here's what I did
Code:
sudo fastboot erase modem
sudo fastboot erase sbl1
sudo fastboot erase dbi
sudo fastboot erase aboot
sudo fastboot erase rpm
sudo fastboot erase tz
sudo fastboot erase LOGO
sudo fastboot erase oppostanvbk
sudo fastboot erase boot
sudo fastboot erase cache
sudo fastboot erase recovery
sudo fastboot erase system
sudo fastboot erase userdata
Now I can't even manage to boot the phone in fastboot mode... I guess I truly fracked it up.
Is there a way to recover it or it's truly bricked?
Can Oneplus Service center help?
Click to expand...
Click to collapse
Can OnePlus's service center help?
-No.
Can I help?
-Yes.
But any reason why you did that? :/
Anyways,follow this: https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
I know that feel. I also hard bricked my opo once. But i managed to recover it using the color os method.
i used this method a while ago:
https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
After that you will have an chinese opo. But most importantly is that fastboot will work. From there i flashed all the official stuff(fastboot,recovery, android 4.4). after that my phone was in the 2014 out of the box state. From there on i started again(unlocking bootloader, flash twrp, flash lineageOS,).
The unbricking process worked for me, hop it will work for you! Good luck!
digitalcoffee said:
I know that feel. I also hard bricked my opo once. But i managed to recover it using the color os method.
i used this method a while ago:
https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
After that you will have an chinese opo. But most importantly is that fastboot will work. From there i flashed all the official stuff(fastboot,recovery, android 4.4). after that my phone was in the 2014 out of the box state. From there on i started again(unlocking bootloader, flash twrp, flash lineageOS,).
The unbricking process worked for me, hop it will work for you! Good luck!
Click to expand...
Click to collapse
No need to re-unlock bootloader.
Also,cm11s restore tool is much better because it is not in chinese and flashes cm11s instead of color os.
When i try to erase modem st1/2, I get :
platform-tools> fastboot erase modemst1
FAILED (remote: 'Not allowed
My pixel 3:
Bootloader is unlocked, no custom recovery,rooted.
Any idea?
Actually took all night to figure out how to do this.... this has only been tested on XT1944-2_NORA but it should work for any non64bit builds....
Download MY ZIP FILE and extract.
Install MotorolaDeviceManager_2.5.4.exe
Dowload stock rom FROM HERE and extract and combine MY ZIP FILE and this one.
Open cmd prompt
Code:
cd "C:\ADDRESS of combined folders"
flash stock rom using these commands:
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash vendor vendor.img
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot-bootloader
now boot twrp_james.img using:
Code:
fastboot boot twrp_james.img
it will take 30-60secs to load cos of the encryption, when it asks for a password just press cancel
while in TWRP, run the following in your ADB terminal
Code:
adb shell mount -o,rw /dev/block/bootdevice/by-name/vendor /vendor
adb push fstab.qcom /vendor/etc/fstab.qcom
then hit wipe > format data > yes
now push magisk with
Code:
adb push Magisk-v19.4.zip /sdcard
install the zip reboot to bootloader
flash twrp with
Code:
fastboot flash recovery twrp-3.3.1-0-nora.img
FIX BAD KEY LOGO BY CHOOSING WHAT YOU WANT FROM HERE
when ur phone loads just open magisk and update it direct install after updating magisk manager