I have the Oneplus 7t. Been using the global fastboot zips to bring the phone back to stock after experimenting with custom ROMS/kernels.
This time, after flashing the msm xr rom I went back to stock using 10.0.6 global fastboot rom. everything looks good while the flash all script is running and then it reboot and sits at the bootloader screen. I cannot get past the bootloader screen. Someone please help.
I can access recovery mode and fastboot. When in fastboot I run fastboot devices and everything checks out. I run the flash all script and everything runs fine. I reboot and its stuck at the bootloader screen. What gives?
EDIT: Figured it out. I used the wrong flash script for the wrong ROM. So the incorrect rom was only flashed to one slot. I used the Resurrection Remix ROM and used the flash script for it and the ROM flash to both slots. Then I downloaded the global 10.0.6 fastboot stock rom and when I start the flash all script, it identified my filesystem instead of saying "Unknown File system type, RAW".
Now I am successfully booted back into stock ROM.
Related
Hi
While flashing CM13 on my redmi 1s, I did a clean install, meaning wiping everything, and then when I went to flash CM13, TWRP just reboots the moment I swipe to install. This happens with any .zip file.
I installed CWM using fastboot, and that gives me the same problem. The moment I try to flash/install anything using a recovery, that recovery reboots and doesn't flash anything. My device is now useless since it doesn't have an OS installed and no way of doing so..
From what I can tell the system partition is bad because when I boot into recovery it isnt mounted
When I take out the battery now it just goes straight to the fastboot screen. I can take it into recovery but it goes to fastboot by default
Please help
Hi dude,
i guess you have checked the integrity of your cm13 ROM file and (winrar>test archive) , your best bet would be flashing a fastbootrom and then come back to cm. Head over to miui and download latest fastboot rom applicable to you.
And its usual booting into fastboot when there is no OS installed atleast for our device so chill dont loose hopes..!
vbvn said:
Hi dude,
i guess you have checked the integrity of your cm13 ROM file and (winrar>test archive) , your best bet would be flashing a fastbootrom and then come back to cm. Head over to miui and download latest fastboot rom applicable to you.
And its usual booting into fastboot when there is no OS installed atleast for our device so chill dont loose hopes..!
Click to expand...
Click to collapse
Flashing the fastboot rom doesn't work.. My recovery is broken too, because I can't flash anything.. In either MiRecovery 2.0.1, CWM or twrp.. When I flash the MIUI rom via fastboot it just boots into recovery..
EDIT, I just got it into MIUI but the 4.3 version from china, without Google, and I can't download google via the MI market. So i'm downloading an international version now and will try to flash using MiFlash.
Does anyone know how I can fix the recovery? It still won't flash anything and reboots the moment I try to.
Hello all!
I recently flashed the 4.16.xx firmware to my device. I am now stuck on the Bliss Rom bootscreen for some reason. Booting into recovery takes me to stock recovery and the phone isn't being recognized through ADB on several different PC's.
Am I screwed here? Any options?
Thanks for any input.
Try going into the fastboot option from the hboot (or called bootloader to many people. To get to hboot, do power and volume down when the phone is booting up. ) and try flashing your TWRP recovery from there. Also make sure your drivers are working.
If you don't know how to flash recovery just Google it, you should be fine.
Dw, dont panic, it'll be fine xD
Zomb!e said:
I recently flashed the 4.16.xx firmware to my device. I am now stuck on the Bliss Rom bootscreen for some reason. Booting into recovery takes me to stock recovery and the phone isn't being recognized through ADB on several different PC's.
Click to expand...
Click to collapse
Stock recovery is the logical result for flashing firmware, unless the firmware was hacked to remove stock recovery.
adb not working, is also normal. You need to be in OS or recovery to use adb commands (and I don't know whether you can with stock recovery). adb does not work in bootloader.
If you flashed an official firmware with s-on, then not boot is also the expected result.
You need to unlock the bootloader again, flash TWRP back onto the phone, and flash a ROM.
redpoint73 said:
Stock recovery is the logical result for flashing firmware, unless the firmware was hacked to remove stock recovery.
adb not working, is also normal. You need to be in OS or recovery to use adb commands (and I don't know whether you can with stock recovery). adb does not work in bootloader.
If you flashed an official firmware with s-on, then not boot is also the expected result.
You need to unlock the bootloader again, flash TWRP back onto the phone, and flash a ROM.
Click to expand...
Click to collapse
Hey thanks for the reply!
I figured it out finally and forgot to update the post. I ended up finding and flashing a Lollipop RUU from the SDcard and that got me booted up. Then I just had to re-flash TWRP, re-root and flash a new rom.
All is well now. Thanks for trying to help out.
I was switching back to stock ROM from Resurrection Remix M on my ZE550ML because I wanted to update the firmware so that I can install Cyanogenmod 14.1. After I downloaded the firmware zip file from Asus, I copied the recovery.img, boot.img, and droidboot.img files. I rebooted my phone into the bootloader and flashed each file using fastboot flash. After this was done, I rebooted into recovery, but it never got to that point. Now my phone's stuck on the Asus Logo screen. I tried the key combination to boot into bootloader or recovery, but that didn't work. Neither adb nor fastboot can detect my phone. I don't know what to do. I looked at tons of posts, but nothing can help me. Any ideas that can help are appreciated. I'm in a pickle right now.
Hi so I was using resurrection remix but after finding my stock phone software NPP25.137-15 online I erased everything and flashed through fastboot it went perfectly and I re-locked my bootloader
but I decided to unlock my bootloader again so I could use magisk on stock firmware
my bootloader unlocked and phone still booted but my problem is with twrp
I powered off my phone
held power and volume down
connected my phone to pc while in bootloader
typed fastboot devices
typed fastboot flash recovery twrp.img
pressed power button on phone to reboot phone ( I didn't boot into recovery )
my Moto G5 XT1675 halts at phone can't be trusted ( bootloader is unlocked screen )
any idea why I can't flash twrp?
Because you haven't disabled dm verity on your device, you can't boot stock firmware with twrp while verity is still enabled, flash this: https://androidfilehost.com/?fid=673368273298927206
If it still doesn't boot, flash stock firmware again via fastboot, then flash twrp and boot DIRECTLY into twrp after it is finished installing, then trying flashing no-verity-opt-encrypt again.
Exanneon said:
Because you haven't disabled dm verity on your device, you can't boot stock firmware with twrp while verity is still enabled, flash this: https://androidfilehost.com/?fid=673368273298927206
If it still doesn't boot, flash stock firmware again via fastboot, then flash twrp and boot DIRECTLY into twrp after it is finished installing, then trying flashing no-verity-opt-encrypt again.
Click to expand...
Click to collapse
What exactly does this file do?
Also I flashed magisk which I knew modifies the boot image and the device booted perfectly with TWRP using the magisk modified boot image if that's anything interesting?
Pretty much I was working on a way to install stock firmware through twrp a few weeks ago so people would not have to use fastboot ( I know how to convert a phone backup to a flashable zip )
The flashable zip worked fine but it only booted using a modified boot file, could this be because it needs DM verity disabled?
Although twrp can restore the system image and what is on the internal storage, it will never be a fully functioning substitute for restoring stock firmware via fastboot, twrp can not run scripts that fastboot can, such as 'fastboot oem lock', I also believe that although it can restore bootloader.img and oem.img via a flashable zip, it would most likely cause the device to brick, so simply put; do not try to use twrp for what it's not meant for, twrp is a recovery for flashing zips, restoring only the system image and storage, flashing recoveries and reformatting partitions (which can be risky), just use fastboot for restoring stock firmware.
And yes, your device will boot with magisk installed as it serves the same purpose as no verity opt 5.1 and later versions, though it is usually recommended to disable dm verity before flashing magisk to stay on the safe side.
The flashable zip you installed on your device only booted with a modified boot file as it is not fully stock firmware, twrp is only capable of flashing some elements of stock firmware, this is why you can boot with dm verity still active after restoring with fastboot, again do not use twrp for restoring stock, use fastboot.
Exanneon said:
Although twrp can restore the system image and what is on the internal storage, it will never be a fully functioning substitute for restoring stock firmware via fastboot, twrp can not run scripts that fastboot can, such as 'fastboot oem lock', I also believe that although it can restore bootloader.img and oem.img via a flashable zip, it would most likely cause the device to brick, so simply put; do not try to use twrp for what it's not meant for, twrp is a recovery for flashing zips, restoring only the system image and storage, flashing recoveries and reformatting partitions (which can be risky), just use fastboot for restoring stock firmware.
And yes, your device will boot with magisk installed as it serves the same purpose as no verity opt 5.1 and later versions, though it is usually recommended to disable dm verity before flashing magisk to stay on the safe side.
The flashable zip you installed on your device only booted with a modified boot file as it is not fully stock firmware, twrp is only capable of flashing some elements of stock firmware, this is why you can boot with dm verity still active after restoring with fastboot, again do not use twrp for restoring stock, use fastboot.
Click to expand...
Click to collapse
it's not meant to be a substitute, and I know only fastboot can do OEM lock, flash partition files, modem files,etc, I've been testing my TWRP version for a while, the oem.img partition is not needed in the TWRP versionas the majority of custom roms for Moto G5 don't touch the oem partition and the oem.img file hasn't changed between the stock updates, the TWRP version is for people who want stock firmware but still want to keep twrp, flash magisk, etc, also because TWRP is a portable method and much faster flashing the system back than through fastboot flashing the system back, my twrp version is only meant to restore the system partition and a dm-verity disabled boot.img I wouldn't even think of flashing a bootloader through anything other than fastboot, I've tested a lot and have not bumped into any problems using TWRP that has caused me to use a computer, actually there has been no problems + I'm also testing on 3 other moto G5's all 3 which are also XT1675 models and same there no problems
Then your query has been resolved.
Exanneon said:
Then your query has been resolved.
Click to expand...
Click to collapse
yes, how do I go about closing this discussion well if you know how to?
Rename it to [closed], that's what many do.
So my phone has been lagging a whole lot using the stock rom and I have decided that I'll try a custom rom to see if that changes anything. So I came here and saw this forum:
"https://forum.xda-developers.com/xa1/development/half-gsi-oreo-8-1-t3902259"
I thought I'll try and so I unlocked my bootloader, only to have my phone be reset (not a problem, everything was backed up). It also boots with a warning "Device unlocked and can't be trusted".
Then I went on to download TWRP using this link in that post: "https://mega.nz/#!FQFXCYSY!DgxQRkaY1Eqq3B0fZLEQBNzUs0Zj80L6IzSHxdorQ3A" which is the TWRP 3.3.0.0 V2 IS FOR ALL USERS.
I didn't want to flash in the event it was the wrong recovery so I tried booting into it, fastboot boot recovery.img
It flashed, everything was ok and now the phone doesn't boot. It stayed in a boot loop. I went ahead and flashed recovery this time, no luck. Downloaded a recovery.img from another website and it didn't allow me to boot to android or recovery.
Is there a way to save my phone, I can't get another phone until August due to contract. It can still boot to fastboot and gets stuck when trying to boot to android. It being able to boot to fastboot makes me think theres a chance to flash a stock rom or any custom recovery and rom to get the phone working again. Any help? Thanks!
Darth343 said:
So my phone has been lagging a whole lot using the stock rom and I have decided that I'll try a custom rom to see if that changes anything. So I came here and saw this forum:
"https://forum.xda-developers.com/xa1/development/half-gsi-oreo-8-1-t3902259"
I thought I'll try and so I unlocked my bootloader, only to have my phone be reset (not a problem, everything was backed up). It also boots with a warning "Device unlocked and can't be trusted".
Then I went on to download TWRP using this link in that post: "https://mega.nz/#!FQFXCYSY!DgxQRkaY1Eqq3B0fZLEQBNzUs0Zj80L6IzSHxdorQ3A" which is the TWRP 3.3.0.0 V2 IS FOR ALL USERS.
I didn't want to flash in the event it was the wrong recovery so I tried booting into it, fastboot boot recovery.img
It flashed, everything was ok and now the phone doesn't boot. It stayed in a boot loop. I went ahead and flashed recovery this time, no luck. Downloaded a recovery.img from another website and it didn't allow me to boot to android or recovery.
Is there a way to save my phone, I can't get another phone until August due to contract. It can still boot to fastboot and gets stuck when trying to boot to android. It being able to boot to fastboot makes me think theres a chance to flash a stock rom or any custom recovery and rom to get the phone working again. Any help? Thanks!
Click to expand...
Click to collapse
OK use the boot.img and recovery.img made by @janjan HERE. Under the heading ¨Downloads¨ see ¨Xperia XA1¨ and download the KERNEL + RECOVERY the boot.img and recovery.img are compatible with the G3121-G3112-G3125-G3116-G3123 devices on the applicable firmware.
Flash BOTH using fastboot. The boot.img is patched to allow TWRP to boot which it will never do using the stock boot.
If you wish to go back to stock then simply use FlashTool to flash the stock fotakernel.sin and boot.sin contained in the firmware for your device.
Does it works becouse I boot my g3116 from flashtool camand was
Fastboot boot boot.img and then also it's stuck into bootloader