i have a few questions, and it's stumping me bad. i got a pixel sailfish on ebay and its in a bootloop. i have tried flashing factory images, ota's, fastbooting twrp and factory resetting and still...loop. sometimes in twrp it will flash the rom, but will freeze and random reboot. i have tried formatting system, vendor and then flashing factory images and to no avail...bootloop. one time i was able to flash nougat factory, and it actually booted. i went ahead and fastbooted twrp...then bam...bootloop again. i need some help. even when i boot into each slot, there is different baseband versions and bootlooder version on each slot. is this normal? should not both slots have same bootloader and baseband version? could this be my bootloop issue?
to reiterate, when i was able to boot the nougat factory, i had fastboot -w, format system and vendor then flashed the nougat fw and it stuck. now i have nothing. can anyone help?
Here are some pics of bl screens. this is result after formatting userdata and flashing latest stock firmware. android 10.
also noted that sometimes when trying to format system, it says no dtbo img. i notice on fw flash that it says no dtbo.img on the flash.
now when i flash nougat, i get "ramdump writing to ext4 file"
it didnt do this when the same nougat fw was successful
Rootmaster906 said:
now when i flash nougat, i get "ramdump writing to ext4 file"
it didnt do this when the same nougat fw was successful
Click to expand...
Click to collapse
You flashed your firmware to both slots and still show different bootloader on each?
Rootmaster906 said:
Here are some pics of bl screens. this is result after formatting userdata and flashing latest stock firmware. android 10.
also noted that sometimes when trying to format system, it says no dtbo img. i notice on fw flash that it says no dtbo.img on the flash.
Click to expand...
Click to collapse
Sailfish doesn't have a dtbo.img. Just system, system_other, boot, and vendor so don't worry about that.
Related
Hello, after unsuccesfull flashing elementalx my device went to bootloop, so i did flash-all, but i noticed that i flashed B partition, so i changed to a and did flash-all again. Is it normal to flash both partition with same default Google image?
WhiteBirdER said:
Hello, after unsuccesfull flashing elementalx my device went to bootloop, so i did flash-all, but i noticed that i flashed B partition, so i changed to a and did flash-all again. Is it normal to flash both partition with same default Google image?
Click to expand...
Click to collapse
Its not really necessary, unless you're locking your boatloader. If you're relocking your bootloader then you should just to be sure.
hi, somehow wiped the 'system' through TWRP by mistake while installing Elemental ROM (I was on EMUI8). And since then I am trying to flash TWRP to boot, but I am getting nothing. I had EMUI 8
Tried flashing stock nougat through Multi Tool but no use, it succeeds but does not boot into anything, just the stock recovery whenever I turn it on. (boot.img didn't install while flashing)
Whenever I flash TWRP and try to boot into recovery (Vol-up+power), it would always boot into stock recovery.
Tried booting into eRecovery, but same thing.
Tried command 'fastboot boot RECOVERY-V2.img' but got the problem saying 'command not allowed'
what to do.
[EDIT]: Can't use 'dload' method because I had EMUI 8 and if i try to flash nougat firmware, it will show an error after 5%.
aryaban2011 said:
hi, somehow wiped the 'system' through TWRP by mistake while installing Elemental ROM (I was on EMUI8). And since then I am trying to flash TWRP to boot, but I am getting nothing. I had EMUI 8
Tried flashing stock nougat through Multi Tool but no use, it succeeds but does not boot into anything, just the stock recovery whenever I turn it on. (boot.img didn't install while flashing)
Whenever I flash TWRP and try to boot into recovery (Vol-up+power), it would always boot into stock recovery.
Tried booting into eRecovery, but same thing.
Tried command 'fastboot boot RECOVERY-V2.img' but got the problem saying 'command not allowed'
what to do.
Click to expand...
Click to collapse
What command are you using to boot into TWRP. Can you access Bootloader. What's the FRP and Phone status. Since you tried to flash Nougat I recommend you try fastboot flash recovery and then any Nougat Compatible TWRP. Yo boot into TWRP after flashing hold Power and Volume Up. If it boots into stock, try factory reset. Either it will boot into TWRP or try to reset. If by some miracle you boot into TWRP don't turn off your phone. Plug it on charging and don't let it Power Off no matter what. After that download Hurupdater and stock Nougat Update files i.e update.zip, update_data_public.zip & uodate_all_hw.zip. Now place these three files as well as Hurupdater in the same folder and transfer them to phone through Micro SD or something. Then go to wipe Format Data and then Advanced Wipe and Mark Dalvik Cache, Cache Data Internal and System. Now flash only the Hurupdater.zip in recovery. Once it completes reboot system and while phone is booting hold Volume up yo enter stock recovery and factory reset. Then format Cache and Reboot. First boot can take up to 10 mins. Don't panic. Good Luck.
Mannan Qamar said:
What command are you using to boot into TWRP. Can you access Bootloader. What's the FRP and Phone status. Since you tried to flash Nougat I recommend you try fastboot flash recovery and then any Nougat Compatible TWRP. Yo boot into TWRP after flashing hold Power and Volume Up. If it boots into stock, try factory reset. Either it will boot into TWRP or try to reset. If by some miracle you boot into TWRP don't turn off your phone. Plug it on charging and don't let it Power Off no matter what. After that download Hurupdater and stock Nougat Update files i.e update.zip, update_data_public.zip & uodate_all_hw.zip. Now place these three files as well as Hurupdater in the same folder and transfer them to phone through Micro SD or something. Then go to wipe Format Data and then Advanced Wipe and Mark Dalvik Cache, Cache Data Internal and System. Now flash only the Hurupdater.zip in recovery. Once it completes reboot system and while phone is booting hold Volume up yo enter stock recovery and factory reset. Then format Cache and Reboot. First boot can take up to 10 mins. Don't panic. Good Luck.
Click to expand...
Click to collapse
When factory resetting from stock recovery, shows that reset failed.
PHONE Unlocked
FRP Unlock
aryaban2011 said:
When factory resetting from stock recovery, shows that reset failed.
PHONE Unlocked
FRP Unlock
Click to expand...
Click to collapse
Try flashing TWRP. I have detailed it above. Don't just try to factory reset.
Mannan Qamar said:
Try flashing TWRP. I have detailed it above. Don't just try to factory reset.
Click to expand...
Click to collapse
Tried Flashing twrp-3.1.1-0-berlin for Honor 6X countless times, no success, still booting into stock recovery.
Try with commands for Oreo as well as Nougat.
Mannan Qamar said:
Try with commands for Oreo as well as Nougat.
Click to expand...
Click to collapse
the only difference in command i know is while flashing recovery, it's changed to 'flash fastboot recovery_ramdisk' from just 'flash fastboot recovery'
can't use dload method because last firmware is Nougat or Marshmellow I think, but I am updated to EMUI 8, so it will crash after 5%.
Dude. What command are you using to flash recovery. The command is
fastboot flash recovery nameofrecovery.img for Nougat
fastboot flash recovery_ramdisk nameof recovery.img for Oreo.
Try dload of EMUI 5. If you maybe try to flash system through fastboot. You can get system.img but extracting the update.app of main update.zip
is there a tool for flashing from your computer? like Multi Tool or something.
if there is, i might try with that.
the command i am using to flash recovery is : 'fastboot flash recovery_ramdisk RECOVERY-V2.img'
Try flashing system through fastboot. There isn't a flashing tool that I know of
Hi, earlier, I wanted to change the rom of my mi 5s. I've got an error 7 follow by "Failed to update system image" on twrp during the flash. I tried many things: edit the installation script, format all the data, update and downgrade TWRP, lock and unlock bootlander and finally perform a fastboot flash using mi flash and the last one worked. But I am not longer able to flash a custom rom without getting error 7 after the "Patching system image unconditionally" message. I've tested lineage, pixel experience, miui, even 8.1 rom but same result. I'm stuck with fastboot global miui 10 (oreo )
Btw, I think that after the error the partition are corrupted since I can't repair them with TWRP.
I don't know what I can do more.I think that i figured out that I am able to flash system.img file using fastboot but I can't flash zip rom using recovery.
As anyone encounter this ?
bob_bricoleur said:
Hi, earlier, I wanted to change the rom of my mi 5s. I've got an error 7 follow by "Failed to update system image" on twrp during the flash. I tried many things: edit the installation script, format all the data, update and downgrade TWRP, lock and unlock bootlander and finally perform a fastboot flash using mi flash and the last one worked. But I am not longer able to flash a custom rom without getting error 7 after the "Patching system image unconditionally" message. I've tested lineage, pixel experience, miui, even 8.1 rom but same result. I'm stuck with fastboot global miui 10 (oreo )
Btw, I think that after the error the partition are corrupted since I can't repair them with TWRP.
I don't know what I can do more.I think that i figured out that I am able to flash system.img file using fastboot but I can't flash zip rom using recovery.
As anyone encounter this ?
Click to expand...
Click to collapse
This usually happens when a partition is missed the way that TWRP doesn´t recognice the exact model and this error 7 is a kind of protection to avoid further mistake.
Some TWRP has in-built the option to fix system issue in advanced settings or then of try to flash a system image this option could appear.
Can you upload from any of the roms the updater script that is inside?
Also sometime you did a repartition? Or flashed some GSI?
SubwayChamp said:
This usually happens when a partition is missed the way that TWRP doesn´t recognice the exact model and this error 7 is a kind of protection to avoid further mistake.
Some TWRP has in-built the option to fix system issue in advanced settings or then of try to flash a system image this option could appear.
Can you upload from any of the roms the updater script that is inside?
Also sometime you did a repartition? Or flashed some GSI?
Click to expand...
Click to collapse
Here is a script from pixel experience:
https://pastebin.com/DXgKrB8Z
I have the error "E1001: Failed to update system image" or "E2001: Failed to update vendor image" or just error 7 if I remove all the abort and assert.
I never did a repartition or flashed a GSI.
bob_bricoleur said:
Here is a script from pixel experience:
https://pastebin.com/DXgKrB8Z
I have the error "E1001: Failed to update system image" or "E2001: Failed to update vendor image" or just error 7 if I remove all the abort and assert.
I never did a repartition or flashed a GSI.
Click to expand...
Click to collapse
Just to be sure I guess you removed all the lines with getprop and not only the words.
Try first flashing persist image through fastboot.
If not flash the rom not through fastboot but using EDL mode and MiFlash tool, if you have unlocked bootloader you can send device through adb with: adb reboot edl or through fastboot with: fastboot oem edl
SubwayChamp said:
Just to be sure I guess you removed all the lines with getprop and not only the words.
Try first flashing persist image through fastboot.
If not flash the rom not through fastboot but using EDL mode and MiFlash tool, if you have unlocked bootloader you can send device through adb with: adb reboot edl or through fastboot with: fastboot oem edl
Click to expand...
Click to collapse
Yep I removed all the line
I managed to flash a full fastboot rom with mi flash and I think that during the process, a persist image was flashed. So i'm runing a stock miui. I even managed to flash Twrp and magisk. But I can't flash a rom through TWRP even after that :crying:
bob_bricoleur said:
Yep I removed all the line
I managed to flash a full fastboot rom with mi flash and I think that during the process, a persist image was flashed. So i'm runing a stock miui. I even managed to flash Twrp and magisk. But I can't flash a rom through TWRP even after that :crying:
Click to expand...
Click to collapse
Some times causes different results flashing the fastboot full image through EDL mode (download mode) instead of through fastboot mode.
It could be the issue the TWRP version if there is other available.
And you could try deleting the recovery partition with fastboot erase recovery, then boot (don´t flash yet) to recovery using fastboot boot whateveriscalled.img, then in TWRP flash the TWRP image or the installer zip, then reboot for first time to TWRP and try again.
I was hoping someone could share the newest patched boot image if not that the stock one. For the international version. I updated to the newest firmware and I forgot to switch slots flash TWRP and magic on the other slot. So I'm hoping I can flash a patch boot image and get back without wiping everything. Thanks
mac796 said:
I was hoping someone could share the newest patched boot image if not that the stock one. For the international version. I updated to the newest firmware and I forgot to switch slots flash TWRP and magic on the other slot. So I'm hoping I can flash a patch boot image and get back without wiping everything. Thanks
Click to expand...
Click to collapse
Is booting to bootloader then fastboot boot twrp. Img that hard to do?
MrSteelX said:
Is booting to bootloader then fastboot boot twrp. Img that hard to do?
Click to expand...
Click to collapse
I think he's trying to revert to stock and forgot to grab the stock image.
Otherwise, yeah, just "fastboot boot the_twrp.img" and move on.
tech_head said:
I think he's trying to revert to stock and forgot to grab the stock image.
Otherwise, yeah, just "fastboot boot the_twrp.img" and move on.
Click to expand...
Click to collapse
I was updating to newest firmware. I forgot to change slots and flash magisk. I run decrypted, but this encrypted me again, I could still boot TWRP but it was encrypted, I was thinking if I had the patched boot IMG I could have brought myself back. I ended up just formatting in TWRP and starting over.
Can someone pls provide OnePlus 7pro 10.3.3 model GM1911
stock boot.img
I been trying to flash some system images I find on the treble forum and nothing is flashing.
My bootloader is unlocked and I'm rooted with magisk
Whenever I run "fastboot erase system" I get a permission denied error and doing "fastboot format system" I get an error about a raw filesystem
Trying to flash an image without wiping I get an error about resizing the system partition.
Am I doing something wrong? It's been years since I've tinkered with Android so I'm out of the loop on Android's dynamic partitioning etc etc
Edit: Figured it out
https://forum.xda-developers.com/mo...de-how-to-flash-generic-image-moto-g-t4131199
for anyone wondering, i just figured it out, the moto g stylus has 2 fastboot modes? one is the bootloader (adb reboot bootloader) and the other is fastbootd (adb reboot fastboot)
booting into fastbootd solved my flashing and wiping issues
Yes. The Android 10 has a new fastbootd mode.
You can enter it with a command
Code:
adb reboot fastboot
You can try to install the Treble image through it. Because in Android 10 there is a new physical partition super.img, which contains three logical partitions - vendor.img, system.img and product.img.
ilia3367 said:
Yes. The Android 10 has a new fastbootd mode.
You can enter it with a command
You can try to install the Treble image through it. Because in Android 10 there is a new physical partition super.img, which contains three logical partitions - vendor.img, system.img and product.img.
Click to expand...
Click to collapse
Yeah I just figured this out although I'm still having issues flashing any gsi ROM, nothing boots after a factory reset, even if I just flash a boot.img patched by magisk with dm verity and encryption disabled
DMedina559 said:
Yeah I just figured this out although I'm still having issues flashing any gsi ROM, nothing boots after a factory reset, even if I just flash a boot.img patched by magisk with dm verity and encryption disabled
Click to expand...
Click to collapse
Same boat. Bootloop if I try to get it to start unencrypted. Booting at least once into a clean boot, then flashing without formatting first let me patch magisk. Have a suspicion the phone isn't too happy about being unecrypted.