Somehow I have lost my OS. Phone will not boot. Can get into Recovery but that's it. Have tried installing factory image and Pixel experience nothing works. Please, I need help.
https://developers.google.com/android/images
Thanks. This doesn't help. Flash-all command doesn't work.
StormCell said:
Thanks. This doesn't help. Flash-all command doesn't work.
Click to expand...
Click to collapse
Flash it separately
fastboot flash system (drag the system image)
fastboot flash recovery (drag the recovery image)
fastboot flash vendor (drag the vendor image)
fastboot flash boot (drag the boot image)
xmxrtyx said:
Flash it separately
fastboot flash system (drag the system image)
fastboot flash recovery (drag the recovery image)
fastboot flash vendor (drag the vendor image)
fastboot flash boot (drag the boot image)
Click to expand...
Click to collapse
What about cache.img and radio.img?
A4Alpha said:
What about cache.img and radio.img?
Click to expand...
Click to collapse
there's no cache.img I think
yeah flash radio
Related
I have downloaded all the files from Google but I want to know if I can flash them all except the recovery. Is this possible?
chrb1985 said:
I have downloaded all the files from Google but I want to know if I can flash them all except the recovery. Is this possible?
Click to expand...
Click to collapse
If you are doing a full installation and not over the air that should not be a problem
Sent from my Nexus 6P using Tapatalk
So I should just flash system boot and vendor then?
chrb1985 said:
So I should just flash system boot and vendor then?
Click to expand...
Click to collapse
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
Exodusche said:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
Click to expand...
Click to collapse
Thanks guys
Exodusche said:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
Click to expand...
Click to collapse
is it nessesary to do a factory reset after?
chrb1985 said:
is it nessesary to do a factory reset after?
Click to expand...
Click to collapse
I wouldn't think so unless your having issues.
Exodusche said:
I wouldn't think so unless your having issues.
Click to expand...
Click to collapse
It bootlooped.. so I had to do a flashall
Yesterday after I was finished I flashed TWRP and it worked . And today I was going to flash a custom kernel and I could not boot In to recovery. It just says: no command. And the tini tiny Android man is in the background.. I tried to flash TWRP again and it says successfull. But no luck on booting to recovery.. please help me
I flashed 3.3.1-2 twrp and then installed a couple different roms to compare. Then I'm not quite sure what happened, I know I formatted and tried to install another, then I lost access to twrp. Even though it says I'm successful at flashing it, it won't boot into twrp or any recovery for that matter. What should I do? I've tried two different twrp's and neither will boot up. I've tried the .bat and volume+ and power, and I even tried with the fastboot boot twrp.img command.
willineedhelp said:
I flashed 3.3.1-2 twrp and then installed a couple different roms to compare. Then I'm not quite sure what happened, I know I formatted and tried to install another, then I lost access to twrp. Even though it says I'm successful at flashing it, it won't boot into twrp or any recovery for that matter. What should I do? I've tried two different twrp's and neither will boot up. I've tried the .bat and volume+ and power, and I even tried with the fastboot boot twrp.img command.
Click to expand...
Click to collapse
What do you see exactly when you try to enter recovery mode? Stock recovery? Or fastboot? Which recovery have you tried? (provide links)
willineedhelp said:
I flashed 3.3.1-2 twrp and then installed a couple different roms to compare. Then I'm not quite sure what happened, I know I formatted and tried to install another, then I lost access to twrp. Even though it says I'm successful at flashing it, it won't boot into twrp or any recovery for that matter. What should I do? I've tried two different twrp's and neither will boot up. I've tried the .bat and volume+ and power, and I even tried with the fastboot boot twrp.img command.
Click to expand...
Click to collapse
Hello, download fastboot rom and flash this files
fastboot flash dtbo dtbo.img
fastboot flash logo logo.img
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash misc misc.img (u can get on fastboot rom not .zip)
fastboot flash recovery recovery.img (recommend used twrp-3.3.1-2-davinci-fix)
For twrp use bat file to install for u don't do it manually..
SomethingWentWrong said:
What do you see exactly when you try to enter recovery mode? Stock recovery? Or fastboot? Which recovery have you tried? (provide links)
Click to expand...
Click to collapse
Fastboot mode
farhan20 said:
Hello, download fastboot rom and flash this files
fastboot flash dtbo dtbo.img
fastboot flash logo logo.img
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash misc misc.img (u can get on fastboot rom not .zip)
fastboot flash recovery recovery.img (recommend used twrp-3.3.1-2-davinci-fix)
For twrp use bat file to install for u don't do it manually..
Click to expand...
Click to collapse
I'll give that a shot, thanks!
farhan20 said:
Hello, download fastboot rom and flash this files
fastboot flash dtbo dtbo.img
fastboot flash logo logo.img
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash misc misc.img (u can get on fastboot rom not .zip)
fastboot flash recovery recovery.img (recommend used twrp-3.3.1-2-davinci-fix)
For twrp use bat file to install for u don't do it manually..
Click to expand...
Click to collapse
Oh man you're a life saver! Worked perfectly! Thanks so much!
willineedhelp said:
Oh man you're a life saver! Worked perfectly! Thanks so much!
Click to expand...
Click to collapse
Glad to know I was able to help, it happens with me and this is how I fixed ?
Hello! Had the same problem and the procedure let me access recovery, yet everytime I reboot to system, the phone opens recovery instead.
I tried restoring a backup but rom is unstable and stuff keeps crashing. Any ideas?
EDIT: did a fastboot flash of .9 ROM and at got it back to work.
farhan20 said:
Hello, download fastboot rom and flash this files
fastboot flash dtbo dtbo.img
fastboot flash logo logo.img
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash misc misc.img (u can get on fastboot rom not .zip)
fastboot flash recovery recovery.img (recommend used twrp-3.3.1-2-davinci-fix)
For twrp use bat file to install for u don't do it manually..
Click to expand...
Click to collapse
So I tried to go back to MIUI and it did it again, I did the default wipe and tried to install it. It got stuck in a bootloop and wouldn't go into TWRP again. Tried what you prescribed again, but that didn't work. I tried using the command (fastboot boot recovery.img) and it just shut off. It's clearly not flashing TWRP, but I have no idea why. I tried both 3.3.1-2 and 3.3.1-3, neither worked. I tried flashing more of the fastboot ROM images, but that did nothing either. Any suggestions? I'm having to use my old moto g5 until I get this fixed, so help ASAP would be amazing. Thanks in advance!
willineedhelp said:
So I tried to go back to MIUI and it did it again, I did the default wipe and tried to install it. It got stuck in a bootloop and wouldn't go into TWRP again. Tried what you prescribed again, but that didn't work. I tried using the command (fastboot boot recovery.img) and it just shut off. It's clearly not flashing TWRP, but I have no idea why. I tried both 3.3.1-2 and 3.3.1-3, neither worked. I tried flashing more of the fastboot ROM images, but that did nothing either. Any suggestions? I'm having to use my old moto g5 until I get this fixed, so help ASAP would be amazing. Thanks in advance!
Click to expand...
Click to collapse
Nvm, I just had a junk TWRP version.
willineedhelp said:
So I tried to go back to MIUI and it did it again, I did the default wipe and tried to install it. It got stuck in a bootloop and wouldn't go into TWRP again. Tried what you prescribed again, but that didn't work. I tried using the command (fastboot boot recovery.img) and it just shut off. It's clearly not flashing TWRP, but I have no idea why. I tried both 3.3.1-2 and 3.3.1-3, neither worked. I tried flashing more of the fastboot ROM images, but that did nothing either. Any suggestions? I'm having to use my old moto g5 until I get this fixed, so help ASAP would be amazing. Thanks in advance!
Click to expand...
Click to collapse
What MIUI version you have tried to go back?
Hi
I have a Ticwatch pro 2020 version with 1gb ram and stuck in a bootloop. I did not do a backup hence it is my fault. Does anyone have a stock image of the watch or have the ticwatch pro 2020 and can extract the stock image for me please? I really need it please. Thank you.
Nchls said:
Hi
I have a Ticwatch pro 2020 version with 1gb ram and stuck in a bootloop. I did not do a backup hence it is my fault. Does anyone have a stock image of the watch or have the ticwatch pro 2020 and can extract the stock image for me please? I really need it please. Thank you.
Click to expand...
Click to collapse
https://mega.nz/#F!cVVBRaxL
[DECRYPTION KEY]
iZbWXMs8vabDW1szJz1hgg
- fastboot flash aboot aboot.img
- fastboot flash boot boot.img
- fastboot flash vendor vendor.img
- fastboot flash system system.img
- fastboot format userdata
- fastboot format cache
- fastboot flash recovery recovery.img
- fastboot reboot
sonnettie said:
https://mega.nz/#F!cVVBRaxL
[DECRYPTION KEY]
iZbWXMs8vabDW1szJz1hgg
- fastboot flash aboot aboot.img
- fastboot flash boot boot.img
- fastboot flash vendor vendor.img
- fastboot flash system system.img
- fastboot format userdata
- fastboot format cache
- fastboot flash recovery recovery.img
- fastboot reboot
Click to expand...
Click to collapse
Cheers mate. You're a legend.
sonnettie said:
https://mega.nz/#F!cVVBRaxL
[DECRYPTION KEY]
iZbWXMs8vabDW1szJz1hgg
- fastboot flash aboot aboot.img
- fastboot flash boot boot.img
- fastboot flash vendor vendor.img
- fastboot flash system system.img
- fastboot format userdata
- fastboot format cache
- fastboot flash recovery recovery.img
- fastboot reboot
Click to expand...
Click to collapse
Hi,
I was wondering if it is it okay to use the ticwatch pro aboot.img with the pro 2020 as there is not an aboot.img in the pro 2020 folder?
Regards
Got this working with Lineage ok but decided to go back to stock. I downloaded the stock recovery rom from NV and set everything up. Inside the recovery bundle is a bat file. Usually I would flash all files manually but this time I used the bat file. It manged the first 3 or 4 commands then came up with error. The box is now stuck in a boot loop and I am unable to access over adb.
Can anyone please suggest a way around this.
Thanks
Here is the bat file
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash dtb mdarcy.dtb.img
fastboot flash vbmeta vbmeta.img
fastboot oem lock (optional step: required for certain functionality)
fastboot reboot
EDIT:
Eventually managed to flash lineage zip again. Used USB keyboard to access recovery
may i ask, what kind of keyboard did u use?
thanks in advance
I've MSM'ed about 8 times today. Every single time I attempt to flash recovery, no matter which recovery, it overwrites the system and upon rebooting to recovery through fastboot, it permanently stays in fastboot. I can MSM out of it. I've tried conversion MSM, temporarily booting recovery, flashing firmwares, resetting, wiping. I cannot fix this. I have spent over 11 hours trying to troubleshoot this. Google comes up with useless results. This is the first time I've not been able to recover from a situation with this phone. Please, if you have any ideas, shoot. The model is kb2007.
Reserved.
try a fastboot boot twrp ( https://github.com/ApexLegend007/twrp_device_oneplus_lemonades/releases ) and try factory resetting it then see if you can switch your partition from a to be or b to a then try msm flashing ( https://androidfilehost.com/?fid=17248734326145733797 )
Nimiskiv said:
try a fastboot boot twrp ( https://github.com/ApexLegend007/twrp_device_oneplus_lemonades/releases ) and try factory resetting it then see if you can switch your partition from a to be or b to a then try msm flashing ( https://androidfilehost.com/?fid=17248734326145733797 )
Click to expand...
Click to collapse
I can't even boot TWRP, it just shows the Oneplus logo and the"fastboot mode" thing forever. It's been 10 minutes now.
If you've used MSM then you're on OOS 11.
I assume the phone boots properly after MSM.
On OOS 11 you can only use TWRP 11 from https://dl.twrp.me/kebab/
And you can only use TWRP 12 on OOS 12 from https://forum.xda-developers.com/t/...in-recovery-project-8t-9r-2022-07-27.4473983/
PS: and you should have posted this in the 8T Q&A forum.
BillGoss said:
If you've used MSM then you're on OOS 11.
I assume the phone boots properly after MSM.
On OOS 11 you can only use TWRP 11 from https://dl.twrp.me/kebab/
And you can only use TWRP 12 on OOS 12 from https://forum.xda-developers.com/t/...in-recovery-project-8t-9r-2022-07-27.4473983/
PS: and you should have posted this in the 8T Q&A forum.
Click to expand...
Click to collapse
nope, still cant boot into twrp
Version of OOS?
Version of TWRP?
Does OOS boot cleanly?
What's your phone?
BillGoss said:
Version of OOS?
Version of TWRP?
Does OOS boot cleanly?
What's your phone?
Click to expand...
Click to collapse
OOS is 11.1.0.2.KB09CB
I've tried TWRP 3.6.1, 3.6.0, and 3.6.2
OOS does boot cleanly.
Phone is KB2007.
The bootloader is unlocked.
I've truly never had this problem before.
You'll probably have to upgrade to the latest version of OOS 11 (or 12) before TWRP will boot.
I have an idea, if you are in fast boot mode then you can flash everything manually. ( https://forum.xda-developers.com/t/oneplus-8t-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4193183/ ) there's only international version (kb2005) it can work with that. Just use payload dumper to extract all the .img by dragging and dropping the payload.bin unto payload dumper after extracting them all into a folder then use the commands to flash them all with adb. Then reboot to recovery, factory reset, and MSM tool back to TMO.
do these commands one by one replacing the .img with the location of the .img. actually, just drag and drop the file after. ( ex: fastboot flash logo C:\Users\???\Desktop\???.img )
Just an extra recommendation to wipe the device
( Fastboot -w )BEFORE THE OTHER COMMANDS but you don't need to if it works without wiping.
fastboot flash logo logo.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash modem modem.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash qupfw qupfw.img
fastboot flash recovery recovery.img
fastboot flash spunvm spunvm.img
fastboot flash storsec storsec.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot flash vendor vendor.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
I'm way too inexperienced with this but if anything goes wrong you can MSM tool back to fastboot.
honest recommendation, just use TMO to International MSM tool after. unless you want to keep it TMO (kb2007)
Nimiskiv said:
I have an idea, if you are in fast boot mode then you can flash everything manually. ( https://forum.xda-developers.com/t/oneplus-8t-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4193183/ ) there's only international version so we got to work with that. Just use payload dumper to extract all the .img by dragging and dropping the payload.bin then use the .bat to flash them all onto the phone. Then reboot to recovery, factory reset and MSM tool it back to tmo. do these commands one by one replacing the .img with the location of the .img. actually just drag and drop the file after. ex: fastboot flash app (file)
fastboot flash logo logo.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash modem modem.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash qupfw qupfw.img
fastboot flash recovery recovery.img
fastboot flash spunvm spunvm.img
fastboot flash storsec storsec.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot flash vendor vendor.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
Ex: fastboot flash app ( c:/????/desktop/payload_dumper/extracted/app.img ) idk
Just an extra recommended to wipe the device
Fastboot -w but you don't need to if it works without.
I'm way to inexperienced with this but if anything goes wrong you can MSM tool back to fastboot.
Click to expand...
Click to collapse
MirageSteezyBoi said:
I've MSM'ed about 8 times today. Every single time I attempt to flash recovery, no matter which recovery, it overwrites the system and upon rebooting to recovery through fastboot, it permanently stays in fastboot. I can MSM out of it. I've tried conversion MSM, temporarily booting recovery, flashing firmwares, resetting, wiping. I cannot fix this. I have spent over 11 hours trying to troubleshoot this. Google comes up with useless results. This is the first time I've not been able to recover from a situation with this phone. Please, if you have any ideas, shoot. The model is kb2007.
Click to expand...
Click to collapse
Sorry I'm very bad at this. I was thinking you didn't even boot properly.... just update to the latest using oxygen updater or the systems bultin update... Im a moron and ill be leaving that up there.