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
Related
Hello, guys! I've a strange problem on my OP2 (A2001).
The new update seems impossible to install on my phone, i've tried all the guides that i've found online, but nothing, everytime is a bootloop. I've tried installing the full rom 2.1.1 in twrp, after that i've tried the full rom 2.1.0 with the ota package, so i've tried the same two things unrooting my phone and with stock recovery. The only way to boot my phone is to install the version 2.1.0.
The last solution that i've not tried is to wipe even data partition instead only system, cache and dalvik.
Someone has the same problem? Have you found a solution?
Thank you
Vatumb said:
Click to expand...
Click to collapse
This tutorial works only for 2.1.0 on my phone, if i try to install 2.1.1 i have a bootloop.
massimoce said:
Hello, guys! I've a strange problem on my OP2 (A2001).
The new update seems impossible to install on my phone, i've tried all the guides that i've found online, but nothing, everytime is a bootloop. I've tried installing the full rom 2.1.1 in twrp, after that i've tried the full rom 2.1.0 with the ota package, so i've tried the same two things unrooting my phone and with stock recovery. The only way to boot my phone is to install the version 2.1.0.
The last solution that i've not tried is to wipe even data partition instead only system, cache and dalvik.
Someone has the same problem? Have you found a solution?
Thank you
Click to expand...
Click to collapse
My upgrade sequence
1) copy 2.1.0 full file (1.1 gb) and the ota update file 44mb file to device
2) like always, take a nandroid backup
3) Dont wipe anything. Add 2.1.0 zip + 2.1.1 ota zip + supersu 2.49 zip to flash queue and flash them all together.
4) wipe caches. Reboot.
It worked for me and retained all my data.
All the best. :good:
Hetalk said:
My upgrade sequence
1) copy 2.1.0 full file (1.1 gb) and the ota update file 44mb file to device
2) like always, take a nandroid backup
3) Dont wipe anything. Add 2.1.0 zip + 2.1.1 ota zip + supersu 2.49 zip to flash queue and flash them all together.
4) wipe caches. Reboot.
It worked for me and retained all my data.
All the best. :good:
Click to expand...
Click to collapse
I've followed your sequence nothing (again bootloop)... is there any difference between supersu 2.46 and 2.49?
Thank you!
massimoce said:
I've followed your sequence nothing (again bootloop)... is there any difference between supersu 2.46 and 2.49?
Thank you!
Click to expand...
Click to collapse
I guess both should work
Hetalk said:
I guess both should work
Click to expand...
Click to collapse
updated with wipe data. Wipe data is the only way to make it work... i don't know why...
massimoce said:
updated with wipe data. Wipe data is the only way to make it work... i don't know why...
Click to expand...
Click to collapse
That sux.
But, good that you got it to work.:good:
Unzip the file https://mega.nz/#!GIgwXKIL!fnuIUY7ETilk-758lv8qguUe3QxC7UwJ4rkRmXk0kMs and put the folder to the TWRP backup then restore.This is the clean sistem,no rooted!For root use and flash this zip : SuperSU-v2.52 http://forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105
Download the zip once, shows its corrupted. Downloading again.
Sent from my XT1095 using Tapatalk
Thnx. Is this only system and boot? Or something more in it?
Cheers
Only system and boot,nothing more!
likurik said:
Only system and boot,nothing more!
Click to expand...
Click to collapse
When looking in the zip i also saw efs and data backed up?
Boot
System
Data
Cache
Efs
ALL this!
Do you get future OTA's with this?
Yes of course! For the future update just i will be flash stock recovery image and update via OTA,.This is the stock marsmallow backup ,nothing touch it
It this a soak test backup or the final one?
Sent from my XT1092 using Tapatalk
Using this method, I get an RPC error once Google Play updates to 6.0.2 that prevents me from downloading any more apps at all. It's quite annoying. Even the 'fix' for it (uninstalling updates, clearing cache, rebooting to recovery & clearing dalvik/cache from there) doesn't fix it permanently
For RPC error the fix is easy!
Go to settings >application > Play Store >storage>Clear Data & Clear Cache.
Go to accounts >Google >Remove account.
Reboot device.
Again Settings>Account >Google >Log In
likurik said:
For RPC error the fix is easy!
Go to settings >application > Play Store >storage>Clear Data & Clear Cache.
Go to accounts >Google >Remove account.
Reboot device.
Again Settings>Account >Google >Log In
Click to expand...
Click to collapse
unfnknblvbl said:
Even the 'fix' for it (uninstalling updates, clearing cache, rebooting to recovery & clearing dalvik/cache from there) doesn't fix it permanently
Click to expand...
Click to collapse
Anyway, I managed to fix it (and very nearly bricked my phone in the process). I originally restored System only, in an attempt to keep my existing data. It didn't work (kept getting an Unknown Play Services error). Then I restored Data in a separate session, and I kept getting the RPC error which would not go away once Play Store updated to 6.0.2 or whatever.
I then did some things which nearly bricked my phone, and just restored the whole archive in one session, which seems to have fixed the issue. Touch wood.
likurik said:
Unzip the file https://mega.nz/#!GIgwXKIL!fnuIUY7ETilk-758lv8qguUe3QxC7UwJ4rkRmXk0kMs and put the folder to the TWRP backup then restore.This is the clean sistem,no rooted!For root use and flash this zip : SuperSU-v2.62-3-20151211162651.zip
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Click to expand...
Click to collapse
is it factory image?
unfnknblvbl said:
Anyway, I managed to fix it
Click to expand...
Click to collapse
No such luck. This is quite annoying, since you can't just go ahead and downgrade back to 5.1 once you've done this
---------- Post added at 10:09 PM ---------- Previous post was at 09:56 PM ----------
reyon6 said:
is it factory image?
Click to expand...
Click to collapse
No it's not. It's a recovery image that somebody (I assume the OP) made of their own install.
[dupe]
Can I flash this? I have an xt1092 and chnaged it to the brazilian model so that I could have the 6.0 update. If I flash this via twrp, will it brick my phone?
Download Link is Broken pls Reupp
Sleeperxr said:
Download Link is Broken pls Reupp
Click to expand...
Click to collapse
https://mega.nz/#!HN4QjJSK!fnuIUY7ETilk-758lv8qguUe3QxC7UwJ4rkRmXk0kMs
likurik said:
https://mega.nz/#!HN4QjJSK!fnuIUY7ETilk-758lv8qguUe3QxC7UwJ4rkRmXk0kMs
Click to expand...
Click to collapse
UK XT1092, flashed this by just
Code:
fastboot boot twrp
and phone signal. Probably caused by me having the US XT1095 modem installed so I flash an old UK modem and after rebooting I have 4G signal.
Booted twrp again and flashed BETA-SuperSU-v2.67-20160121175247.zip and got stuck on bootloader.
Booted twrp again and flash BETA-SuperSU-v2.52.zip and root-boot-6.0-xt1092.zip from http://forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105
Seems to be working.
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.
Hello, I have my phone rooted and would like to update to NMJ51B, but I'm not exactly sure how to go about it and don't want to risk bricking my phone again! What would be the exact process to go about this? I'd like to do it without wiping my phone if possible. While I love having root, OTA updates seem to be a real headache. Any help would be appreciated!
You have to re-flash the stock boot.img from your current build via fastboot, then you should be good to go. Check for an update in the settings and update. Shouldn't have to wipe anything
You can get the boot image from the essential site or from the firmware dumps in the rom section of the essential forum. I hope this helps!
sirdicholas said:
You have to re-flash the stock boot.img from your current build via fastboot, then you should be good to go. Check for an update in the settings and update. Shouldn't have to wipe anything
You can get the boot image from the essential site or from the firmware dumps in the rom section of the essential forum. I hope this helps!
Click to expand...
Click to collapse
Ok, I was thinking I'd have to wipe the phone to flash a stock image. Thanks for the info!
Uh, the very first thing it says when flashing the stock rom is "erasing userdata." Are you saying it's NOT going to wipe my phone?
Annnnd, it wiped everything, including the backup I created with TWRP. For future reference, does anyone have a step by step that does NOT wipe data?
sublimejhn said:
Uh, the very first thing it says when flashing the stock rom is "erasing userdata." Are you saying it's NOT going to wipe my phone?
Annnnd, it wiped everything, including the backup I created with TWRP. For future reference, does anyone have a step by step that does NOT wipe data?
Click to expand...
Click to collapse
You don't have to flash the whole package just the boot.img. But it sounds as if you already wiped. I should have clarified. In the guide to how to root your essential, if you read through, others have explained how to unroot without wiping.
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.