Related
I used Flashfire to flash a radio.img without checking flash bootloader.
I can get into the bootloader and twrp.
When wiping the device and flashing another rom or restoring a backup my 6p does not get passed the custom rom splash screen.
I was thinking of trying to fastboot flash system/data/cache of the March update and see if it boots.
I know I messed up. don't even know if it was because I didn't check the bootloader option in Flashfire. Just my guess because everything was working fine beforehand.
Any help or ideas would be welcome.
dirtyreturn said:
I used Flashfire to flash a radio.img without checking flash bootloader.
I can get into the bootloader and twrp.
When wiping the device and flashing another rom or restoring a backup my 6p does not get passed the custom rom splash screen.
I was thinking of trying to fastboot flash system/data/cache of the March update and see if it boots.
I know I messed up. don't even know if it was because I didn't check the bootloader option in Flashfire. Just my guess because everything was working fine beforehand.
Any help or ideas would be welcome.
Click to expand...
Click to collapse
Hey... You said you wiped your device? What did you wipe in TWRP?
Try to install a ROM from TWRP. Once it's over go in wipe and do a factory reset. Reboot. It should likely fix your issue.
Good luck...
5.1 said:
Hey... You said you wiped your device? What did you wipe in TWRP?
Try to install a ROM from TWRP. Once it's over go in wipe and do a factory reset. Reboot. It should likely fix your issue.
Good luck...
Click to expand...
Click to collapse
Hey thanks for the reply.
Yeah, I wiped data, system, cache. Just the standard - I still have internal storage intact.
Its just strange, I've used Flashfire before but not for flashing a radio and it worked out fine.
I am on 3.79 and used Flashfire to flash 3.78. Went to the bootloader just to check and it still shows 3.79. Just my fault . I didn't check flash bootloader in the Flashfire settings. Atleast that's what I am guessing. Things were just fine before
Sent from my LG-E980 using Tapatalk
dirtyreturn said:
Hey thanks for the reply.
Yeah, I wiped data, system, cache. Just the standard - I still have internal storage intact.
Its just strange, I've used Flashfire before but not for flashing a radio and it worked out fine.
I am on 3.79 and used Flashfire to flash 3.78. Went to the bootloader just to check and it still shows 3.79. Just my fault . I didn't check flash bootloader in the Flashfire settings. Atleast that's what I am guessing. Things were just fine before
Click to expand...
Click to collapse
Well, if nothing work, maybe backup your internal storage and flash a factory image... Then in recovery do a factory reset afterward. Who knows. Going back to stock shouldn't hurt anyway.
Good luck...
@dirtyreturn
I've used FF to flash only radio files to the modem partition many times without issue. You untick all but modem, and you untick inject SU and preserve recovery. Not sure what went wrong for you. As mentioned , you should be able to manually flash stock and if you're careful, you'll still have your data. All your settings will be reset, but the userdata will be there. You can even use flash-all.bat, but open it in a text editor and remove the "-w" flag so it will not wipe your userdata. The Google page where you get the full factory image will have instructions.
v12xke said:
@dirtyreturn
I've used FF to flash only radio files to the modem partition many times without issue. You untick all but modem, and you untick inject SU and preserve recovery. Not sure what went wrong for you. As mentioned , you should be able to manually flash stock and if you're careful, you'll still have your data. All your settings will be reset, but the userdata will be there. You can even use flash-all.bat, but open it in a text editor and remove the "-w" flag so it will not wipe your userdata. The Google page where you get the full factory image will have instructions.
Click to expand...
Click to collapse
Thanks. It was obviously my fault somehow.
I do remember there being only one option to tick.
Using fastboot back to stock did the trick and made me realize maybe I should hold off on using Flashfire for a bit.
Sent from my Nexus+6P using Tapatalk
dirtyreturn said:
Thanks. It was obviously my fault somehow.
I do remember there being only one option to tick.
Using fastboot back to stock did the trick and made me realize maybe I should hold off on using Flashfire for a bit.
Click to expand...
Click to collapse
Nah, FF is awesome and a major time-saver. Just read up on the documentation here and become familiar with it.
Can you/has anyone flashed 8.0 using FlashFire? Full image and just flashing Boot, System, and Vendor from 7.1.2? The reason I ask, I have never had luck doing just downloading the OTA, and flashing that with FlashFire
Thanks
idbl_fanatic said:
Can you/has anyone flashed 8.0 using FlashFire? Full image and just flashing Boot, System, and Vendor from 7.1.2? The reason I ask, I have never had luck doing just downloading the OTA, and flashing that with FlashFire
Thanks
Click to expand...
Click to collapse
Update, flashing the OTA zip file does not work, I ended up flashing the full system and only selecting Boot, System, and Vendor, so fare so good
Did you grab the factory image? I noticed that it reads Not for TMO/USCC/Fi
Bangincrazy said:
Did you grab the factory image? I noticed that it reads Not for TMO/USCC/Fi
Click to expand...
Click to collapse
Yes, Factory image, I am on AT&T
idbl_fanatic said:
Yes, Factory image, I am on AT&T
Click to expand...
Click to collapse
Now all you need to do is manually flash the bootloader and modem via fastboot.
v12xke said:
Now all you need to do is manually flash the bootloader and modem via fastboot.
Click to expand...
Click to collapse
you can always ran the flash-all.bat file after editing the file and removing the -w from it.
If you want to keep your system decrypted simply boot to bootloader/recoery and flash any moded kernel. either way, using flashboot is simple enough so you don't have to use flashfire.
idbl_fanatic said:
Update, flashing the OTA zip file does not work, I ended up flashing the full system and only selecting Boot, System, and Vendor, so fare so good
Click to expand...
Click to collapse
This worked for me, except that it erased TWRP even when I selected to option to back up recovery. At the end it wouldn't boot up and had to perform a factory reset, so in the end, I got a clean, stock 8.0, unrooted.
patriot76 said:
This worked for me, except that it erased TWRP even when I selected to option to back up recovery. At the end it wouldn't boot up and had to perform a factory reset, so in the end, I got a clean, stock 8.0, unrooted.
Click to expand...
Click to collapse
I wonder why it did that, I had no issues, I have had it do that before on 7.1.2 however.
I downloaded the full ota file from Google site, and flashed it like a normal ota + root afterwards with flashfire.
Been 3 days since, Android o works like a charm!
ixayman said:
I downloaded the full ota file from Google site, and flashed it like a normal ota + root afterwards with flashfire.
Been 3 days since, Android o works like a charm!
Click to expand...
Click to collapse
Wow that's good news, what phone & What carrier are you using? Did FlashFire read it the way it does with a Nougat OTA update
fiverings said:
Wow that's good news, what phone & What carrier are you using? Did FlashFire read it the way it does with a Nougat OTA update
Click to expand...
Click to collapse
my phone is 6p 64g, for my carrier I'm using a local one here in israel so idk if it's relevant to the issues you guys get :C.
in terms of flashing i flashed it like any normal monthly security patch lol, just went on google ota page, downloaded the ~1gb file.. then on flashfire i chose ota, selected said file + inject superSu afterwards, for wiping i chose cache and dalvik only. and done.
ixayman said:
my phone is 6p 64g, for my carrier I'm using a local one here in israel so idk if it's relevant to the issues you guys get :C.
in terms of flashing i flashed it like any normal monthly security patch lol, just went on google ota page, downloaded the ~1gb file.. then on flashfire i chose ota, selected said file + inject superSu afterwards, for wiping i chose cache and dalvik only. and done.
Click to expand...
Click to collapse
I have 6p 64gb also. We're you on the August build 7.1.2. and you only wiped dalvik and Cache and did you uncheck Data & 3rd party apps.so you just wiped dalvik & cache and nothing else. I usually flash the factory image to get monthly update because my bootloader is unlocked. So I don't get OTA updates thru my phone.
fiverings said:
I have 6p 64gb also. We're you on the August build 7.1.2. and you only wiped dalvik and Cache and did you uncheck Data & 3rd party apps.so you just wiped dalvik & cache and nothing else. I usually flash the factory image to get monthly update because my bootloader is unlocked. So I don't get OTA updates thru my phone.
Click to expand...
Click to collapse
i think i was on may or June's build i don't remember correctly. I also have bootloader unlocked but i never allow automatic OTA updates threw my phone, I just download the file manually (from here https://developers.google.com/android/ota) and flash it with flashfire, that way i continue where i left off without loosing any data (+root ). you should try it. and yeah on wipe options i untick everything except cache and dalvik.
ixayman said:
i think i was on may or June's build i don't remember correctly. I also have bootloader unlocked but i never allow automatic OTA updates threw my phone, I just download the file manually (from here https://developers.google.com/android/ota) and flash it with flashfire, that way i continue where i left off without loosing any data (+root ). you should try it. and yeah on wipe options i untick everything except cache and dalvik.
Click to expand...
Click to collapse
Thanks ixayman, going to wait a few days, because the OTA says it's not compatible with T-Mobile, us Cellular, Fi. All those are in my fi that I use. And I read that people who down loaded either Factory image or OTA are not working with Fi . When they fix this I try it then.
Thanks, you've been a big help
Hello! I just updated to the latest OTA of OOS 5.0 and now the phone is just stuck on the screen where the white dots spin around I tried clearing cache, wiped "System settings" via Oxygen Recovery and no luck. I sideloaded the zip to my device and flashed it over the one I had on it previously. I followed this guide https://forum.xda-developers.com/oneplus-5/how-to/guide-restore-data-stuck-bootloop-n-o-t3724515 without any results! This is ridiculous. I just wanted to update to Oreo. Here are my phone details: https://imgur.com/a/n4rtR I am unsure what to try next. Should I wipe /system and flash the previous ROM zip file and try that? I can see my files but they are completely encrypted thanks to OOS, but only can I see them in Oxygen Recovery; TWRP shows nothing. Suggestions would be appreciated, thank you.
Had the same problem, had to format Data partition to get it working. Lost all data though
I was on OOS 4.5.15 with Magisk root and TWRP. Last night, uninstalled Magisk and I flashed stock recovery to update my phone. Even though I cleared cache and Dalvik, boot loop happened.
Only after a full reset, the phone boot normally. Since I had all important files backed up, I did not loose anything but it still bothers me. There should have been a more streamlined update process.
I completely bricked my device with the update, so i used this tutorial : https://www.androidexplained.com/oneplus-5-unbrick-return-stock/
I lost all my data but now it work like a charm and i was able to update properly to Oreo
hknisl said:
I was on OOS 4.5.15 with Magisk root and TWRP. Last night, uninstalled Magisk and I flashed stock recovery to updated my phone. Even though I cleared cache and Dalvik boot loop happened.
Only after a full reset, the phone boot normally. Since I had all important files backed up, I did not loose anything but it still bothers me. There should have been a more streamlined update process.
Click to expand...
Click to collapse
You have to do a full wipe (system, data, internal storage, and both cache) when going from Nougat to Oreo. That is the only way.
azeem40 said:
You have to do a full wipe (system, data, internal storage, and both cache) when going from Nougat to Oreo. That is the only way.
Click to expand...
Click to collapse
If so, how could they offer an OTA for customers? Don't get me wrong, I am just wondering.
hknisl said:
If so, how could they offer an OTA for customers? Don't get me wrong, I am just wondering.
Click to expand...
Click to collapse
From what I know, you have to be unrooted and on stock recovery for that to work.
azeem40 said:
From what I know, you have to be unrooted and on stock recovery for that to work.
Click to expand...
Click to collapse
I had unrooted my phone using magisk uninstaller and flashed stock recovery. It has something to do with encryption, but I am not quite sure.
hknisl said:
If so, how could they offer an OTA for customers? Don't get me wrong, I am just wondering.
Click to expand...
Click to collapse
Very good question. Even I wanna know how it is working technically.
azeem40 said:
From what I know, you have to be unrooted and on stock recovery for that to work.
Click to expand...
Click to collapse
I was unrooted and having stock recovery, still got bootloop. OnePlus basically messed up.
Today i got an OTA update Oxygen 5.0.1
I'm currently on 5.0
How can i flash this update? Twrp won't let me, something about the unlocked bootloader.
Never had this issue with Nougat......
Change for this, its work fine
https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
Same thing happening here.
Unlocked Bootloader Error 7,
Tried with codeworx 8.0 and bluspark recoveries, same error, even wiping caches multiple times
Regards
Heeter said:
Same thing happening here.
Unlocked Bootloader Error 7,
Tried with codeworx 8.0 and bluspark recoveries, same error, even wiping caches multiple times
Regards
Click to expand...
Click to collapse
Try wiping dalvik cache, system and data, before proceeding with the rom.
Still couldn't make it with the patch file,
So I used the full file, and it worked fine.
Regards
I tried to flash PE-CAF at first, but it appears Error 7.
I look up at the thread, and error 7 means require firmware update
So I proceed to update the firmware to 339 and flash the ROM.
Well, PE-CAF is successfully flashed, but it stuck at the Google Logo screen forever.
I tried to flash other ROM as well, and all of them successfully flashed but also cannot boot at all.
Anyone can help with my issue?
SleepingAran said:
I tried to flash PE-CAF at first, but it appears Error 7.
I look up at the thread, and error 7 means require firmware update
So I proceed to update the firmware to 339 and flash the ROM.
Well, PE-CAF is successfully flashed, but it stuck at the Google Logo screen forever.
I tried to flash other ROM as well, and all of them successfully flashed but also cannot boot at all.
Anyone can help with my issue?
Click to expand...
Click to collapse
Wipe all
sagardhiman007 said:
Wipe all
Click to expand...
Click to collapse
wipe all as in? I wiped data cache and dalvik tho
SleepingAran said:
wipe all as in? I wiped data cache and dalvik tho
Click to expand...
Click to collapse
Wipe system data vendor except only internal storage
sagardhiman007 said:
Wipe system data vendor except only internal storage
Click to expand...
Click to collapse
Thanks, it worked.
SleepingAran said:
Thanks, it worked.
Click to expand...
Click to collapse
Welcome bro