I just got my Find 7a today and it said there is an OTA availible. I downloaded and flased it and now I am stuck in a boot loop. I tried clearing Cache and Data in Oppo's Recovery but still no success - no boot. Always the black Oppo logo. What can I do to get my phone working again?
[EDIT]
Ok - I found 2 solutions.
1) A link to the stock ColorOS 1.2 was posted on Oppos forum (haven't tried this one yet) http://www.oppoforums.com/threads/how-can-i-get-international-coloros-1-2-rom-for-find-7a.12660/
2) I flashed the Beta for ColorOS 2. It works, but is clearly still in beta. Download also on Oppo forum http://www.oppoforums.com/threads/find-7-coloros-2-0-0i-beta.11926/
Gamingmayr said:
I just got my Find 7a today and it said there is an OTA availible. I downloaded and flased it and now I am stuck in a boot loop. I tried clearing Cache and Data in Oppo's Recovery but still no success - no boot. Always the black Oppo logo. What can I do to get my phone working again?
Click to expand...
Click to collapse
I feel for ya! I guess I'm happy now that the OTA won't flash on my device. I'm new to Oppo, so I'm not sure what you could do besides pushing the entire factory image via adb and flashing in stock recovery. But, I'm not sure where to get the entire image... How about color OS 2.0 beta?
Did you try factory reset? You are likely aware that all your data will be gone after that.
Problem solved
farfromovin said:
I feel for ya! I guess I'm happy now that the OTA won't flash on my device. I'm new to Oppo, so I'm not sure what you could do besides pushing the entire factory image via adb and flashing in stock recovery. But, I'm not sure where to get the entire image... How about color OS 2.0 beta?
Click to expand...
Click to collapse
I finally tried the Color OS 2 beta and it worked. The system boots now but since it is a beta it still needs some work... It's not perfect but at least better than a phone in bootloop.
Thanks
farfromovin said:
But, I'm not sure where to get the entire image... How about color OS 2.0 beta?
Click to expand...
Click to collapse
If you go to the Oppo Forums under the ColorOS section there is a thread called "Download ColorOS." Right now the only two downloads are the ones the OP posted but I thought I'd throw that out there in case they add an updated ColorOS 2.0.
-Sent from my Sega CD
Related
Hey guys,
I think I'm a little bit in trouble: I just got a OP3 and wanted to root it as I'm used to it from the OPO.
But there were problems because of Force Encyption... After a few trys and flashs, I flashed Stock OOS (
OnePlus3Oxygen_16_OTA_013_all_1608061823_765c081a5c8e4dad.zip
) from TWRP and after rebooting...
THE SCREEN IS YELLOW AND FULL OF PIXELS (like an olt TV).
You can feel it works from vibrations but you can't see what's going on... I tried this for unbricking but no success.
I think my phone's display drivers might be broken but idk.
Does anyone maybe know what to do here?
Peybro said:
Hey guys,
I think I'm a little bit in trouble: I just got a OP3 and wanted to root it as I'm used to it from the OPO.
But there were problems because of Force Encyption... After a few trys and flashs, I flashed Stock OOS (
OnePlus3Oxygen_16_OTA_013_all_1608061823_765c081a5c8e4dad.zip
) from TWRP and after rebooting...
THE SCREEN IS YELLOW AND FULL OF PIXELS (like an olt TV).
You can feel it works from vibrations but you can't see what's going on... I tried this for unbricking but no success.
I think my phone's display drivers might be broken but idk.
Does anyone maybe know what to do here?
Click to expand...
Click to collapse
Unbrick guide method 2 should fix it, otherwise ask Oneplus support.
Peybro said:
Hey guys,
I think I'm a little bit in trouble: I just got a OP3 and wanted to root it as I'm used to it from the OPO.
But there were problems because of Force Encyption... After a few trys and flashs, I flashed Stock OOS (
OnePlus3Oxygen_16_OTA_013_all_1608061823_765c081a5c8e4dad.zip
) from TWRP and after rebooting...
THE SCREEN IS YELLOW AND FULL OF PIXELS (like an olt TV).
You can feel it works from vibrations but you can't see what's going on... I tried this for unbricking but no success.
I think my phone's display drivers might be broken but idk.
Does anyone maybe know what to do here?
Click to expand...
Click to collapse
Which TWRP are you using? Try using the latest from eng.stk's (Blue Spark).
If you want MM, the more stable and improved version is 3.2.8. What you downloaded is 3.2.4. So, download 3.2.8 and boot into recovery, wipe system, dalvik cache, cache and data including internal storage (you will lose all your files including photos, videos etc). Boot the phone into the bootloader mode and push the ROM to the phone and flash it from recovery or flash the ROM from PC using adb commands. Flash TWRP again and boot into recovery and if ok, boot into system. If everything is ok, you can flash SuperSU/Magisk, if you need root. A couple of wipes of both the caches in between may also be done.
If this doesn't sort out the issue, use Method 2 from the Mega Unbrick Guide in XDA and follow every instruction scrupulously, especially relating to drivers.
If even this fails, it is a hardware issue.
EDIT: I see that Puddi Puddin beat me to it.
Puddi_Puddin said:
Unbrick guide method 2 should fix it, otherwise ask Oneplus support.
Click to expand...
Click to collapse
tnsmani said:
If this doesn't sort out the issue, use Method 2 from the Mega Unbrick Guide in XDA and follow every instruction scrupulously, especially relating to drivers.
If even this fails, it is a hardware issue.
Click to expand...
Click to collapse
Step 8 doesn't work for me...
I guess the phone goes back to the repair company then
tnsmani said:
Which TWRP are you using? Try using the latest from eng.stk's (Blue Spark).
If you want MM, the more stable and improved version is 3.2.8. What you downloaded is 3.2.4. So, download 3.2.8 and boot into recovery, wipe system, dalvik cache, cache and data including internal storage (you will lose all your files including photos, videos etc). Boot the phone into the bootloader mode and push the ROM to the phone and flash it from recovery or flash the ROM from PC using adb commands. Flash TWRP again and boot into recovery and if ok, boot into system. If everything is ok, you can flash SuperSU/Magisk, if you need root. A couple of wipes of both the caches in between may also be done.
Click to expand...
Click to collapse
I am using the newest (twrp-3.1.1-2-oneplus3.img) but the problem is that I can't see anything in recovery or elsewhere :/
Peybro said:
Step 8 doesn't work for me...
I guess the phone goes back to the repair company then
Click to expand...
Click to collapse
Well you have really messed up something it seems.. This shouldnt be happening by rooting and stuff, I think it is pure coincidence
Peybro said:
Hey guys,
I think I'm a little bit in trouble: I just got a OP3 and wanted to root it as I'm used to it from the OPO.
But there were problems because of Force Encyption... After a few trys and flashs, I flashed Stock OOS (
OnePlus3Oxygen_16_OTA_013_all_1608061823_765c081a5c8e4dad.zip
) from TWRP and after rebooting...
THE SCREEN IS YELLOW AND FULL OF PIXELS (like an olt TV).
You can feel it works from vibrations but you can't see what's going on... I tried this for unbricking but no success.
I think my phone's display drivers might be broken but idk.
Does anyone maybe know what to do here?
Click to expand...
Click to collapse
What exactly did you flash other than OOS and recovery? Why did you need a few flashes? You flashed SuperSU or Magisk? Root still works on an encrypted system so not understanding some things from your post
Puddi_Puddin said:
Well you have really messed up something it seems.. This shouldnt be happening by rooting and stuff, I think it is pure coincidence
Click to expand...
Click to collapse
I hope so - maybe the repair company messed the screen connection up and they fix it for free... :angel:
Renosh said:
What exactly did you flash other than OOS and recovery? Why did you need a few flashes? You flashed SuperSU or Magisk? Root still works on an encrypted system so not understanding some things from your post
Click to expand...
Click to collapse
First I flashed newest TWRP and Paranoid Android but it wasn't as good as expected and so I flashed back to OOS (_008 I think) and everything worked but when I wanted to flash Magisk (because SafetyNet) via TWRP I couldn't because the phone wanted a pattern to unlock encryption.
I read that it would be the same as I used to unlock my phone (btw the only 1 I use) but it didn't work...
Before I found a guide with the right order to remove the encryption I tried different ways by myself (that's because I flashed a few times) (Toolkit, "Fastboot format userdata", TWRP format) but nothing removed it.
Then I wanted to follow that guide but meanwhile there was no OS at all and img Install via fastboot didn't work but I managed to get the newest stable OOS (_16 I think) on the phone, installed it with TWRP aaaaaand...
YELLOW-ORANGEish PIXEL SCREEN
fastboot and everything works - I just can't see what's going on
Peybro said:
I hope so - maybe the repair company messed the screen connection up and they fix it for free... :angel:
First I flashed newest TWRP and Paranoid Android but it wasn't as good as expected and so I flashed back to OOS (_008 I think) and everything worked but when I wanted to flash Magisk (because SafetyNet) via TWRP I couldn't because the phone wanted a pattern to unlock encryption.
I read that it would be the same as I used to unlock my phone (btw the only 1 I use) but it didn't work...
Before I found a guide with the right order to remove the encryption I tried different ways by myself (that's because I flashed a few times) (Toolkit, "Fastboot format userdata", TWRP format) but nothing removed it.
Then I wanted to follow that guide but meanwhile there was no OS at all and img Install via fastboot didn't work but I managed to get the newest stable OOS (_16 I think) on the phone, installed it with TWRP aaaaaand...
YELLOW-ORANGEish PIXEL SCREEN
fastboot and everything works - I just can't see what's going on
Click to expand...
Click to collapse
I already asked you to use the TWRP from eng.stk
The official 3.1.1-2 works well with OOS but is cranky with custom ROMS. eng.stk's works both with OOS and custom ROMs.
tnsmani said:
I already asked you to use the TWRP from eng.stk
The official 3.1.1-2 works well with OOS but is cranky with custom ROMS. eng.stk's works both with OOS and custom ROMs.
Click to expand...
Click to collapse
I can give it a try later (and in the future when everything works again) but I do not think (at least I can't imagine) that the problem I have comes from recovery.
I know the reason!
I found other people who also had a static screen and they said they could fix it by pressing the screen back on its contacts...
I did so and it worked!... A bit... For a few minutes...
So the static definitely wasn't the result of rooting and stuff but the repair company's fault.
I hope they accept their mistake and fix it. Thx for everyone here trying to hel me!
P.S.
tnsmani said:
I already asked you to use the TWRP from eng.stk
The official 3.1.1-2 works well with OOS but is cranky with custom ROMS. eng.stk's works both with OOS and custom ROMs.
Click to expand...
Click to collapse
And as soon as I can I will try this TWRP
-------------------------------- Edit: --------------------------------
(Just in case people get same problem)
[after Mega Unbrick Method 2 finally worked (I put the stock zip in the tool's folder)]
This morning I restarted the phone just because and I could see what was going on on the phone - but the display was still crazy with yellow tint and colorful stripes etc.). After setup it asked me to download & install newest stock rom; I did and after reboot everything was fine again....
Don't know what happened here but it seems to work again.
Hello,
I've ran into an issue after installing the latest Oxygen OS coming from a custom rom, im stuck at the welcome/setup screen. I can get past the language screen, font selection, all terms/condition screens but once i get to select whether to copy apps & data, i get pushed back to the wifi-selection screen. I do not get it?? Why does it do that?
What i've tried so far:
1. Reinstalling Oxygen OS via recovery(sideload option) and TWRP didn't work.
2. I have tried flashing an older version of Oxygen OS, but i still have the same issue..
3. I have tried wiping everything both via the standard recovery and TWRP, didnt work.
4. I've also tried changing language, and removing the sim card, didnt work.
What other options are there? I really like the stock version for OnePlus 5T as i've noticed it got the best battery performance, and also being smooth. Thanks in advance!
Solved By using the Oneplus unbrick tool i got this fixed, and i can now get past all the screen during the setup of the phone!
Try this unbrick tool (ROM is oxygenos 4.7.x, will wipe everything including personal files)
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
FRP?
nguyenlucky said:
Try this unbrick tool (ROM is oxygenos 4.7.x, will wipe everything including personal files)
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
Click to expand...
Click to collapse
Ok, i haven't tried that yet, so it might work. Let me check and get back to you on this! Thanks for the suggestion!
nguyenlucky said:
Try this unbrick tool (ROM is oxygenos 4.7.x, will wipe everything including personal files)
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
Click to expand...
Click to collapse
Wow! That actually worked! Thank you so much for this suggestion!
Just saw this; in case anyone else has a problem getting past it or can't find a solution, there's an amazingly simply way to pass setup wizard. Tap the 4 corners of the screen starting in the top left and go clockwise. Apparently this has been a feature since 2.2 ? and I hadn't heard of it until a few months ago.
ONe plus one cyanogen is stuck on welcome screen after language selection NEXT is non responsive thanks
I messed up big time trying to update my march build of nos to the newest june build. i was using the recommend things for the rom of course but when trying to flash gapps i got a error 20 despite having the correct version (ive been doing this for years). So when i noticed i wasnt going to be able to make it work i tried to go back to an older gapps, then an older nos. every time i was getting error 20 even with the march rom and gapps i used originally. so i tried to go to a new rom, switched to their recommended twrp, firmware etc. but no matter what i keep getting a no os installed error now despite not getting any errors from twrp during install. cant figure out how to fix it and i cant find a fashboot rom for the mix 2 anywhere and ive downloaded about 3 sketchy files that were on the mix forum but miflash didnt recognize anything. The only thing here i have never done a thousand times already is the fastboot rom and miflash. If anyone can help it would be great. I think i just need a compatible fastboot rom and whatever it requires to install, and i should be goog to go but i cant find anything and im on day 2 now.
also for the record ive already tried manually mounting system, repairing system within twrp and doing a full wipe of everything. it seems system isnt actually getting written over despite twrp not saying anything.
also my phone was encrypted originally but i did format data multiple times
So it got rekt
Goodluck mate :cyclops:
alphamode said:
I messed up .. times
Click to expand...
Click to collapse
http://en.miui.com/a-234.html
I recently bought a P4XL and was going to use my P2XL as a stay-at-home bridge between Google Home and P4XL Tasker. The P2XL was running CarbonRom 8.0 so I decided to upgrade to A9 and that's when all hell broke loose.
Here's the relevant steps I took after the initial update stopped responding:
1. Factory reset to A9, A10 & A8 all failed. In that order. Unresponsive.
2. Extracted the boot image from factory and flashed it. Unresponsive.
3. TWRP won't launch (I assume it was wiped out somewhere during #1's hang).
4. TWRP won't boot from fastboot. Somewhere around #2, I started receiving unknown variable errors for the slot.
5. I've also tried Deus (forgive spelling if incorrect) package for boot loops. No dice.
6. I've switched USB cables (A&C) and rebooted 32⁴³⁶ times to no avail.
That's it. Thanks, all, for listening. She's been a great phone. Hoping I can get a bit more out of her. Anyone have any ideas because I'm fresh out.
You know you have to flash factory images for different android version to BOTH slots right? You can't go from A9 to A10/11 and vice versa without flashing the images to both slots or you won't be able to boot.
Flash the official Factory images first
GohanBurner said:
You know you have to flash factory images for different android version to BOTH slots right? You can't go from A9 to A10/11 and vice versa without flashing the images to both slots or you won't be able to boot.
Click to expand...
Click to collapse
Yeah, I never flashed to A because, like I said in the initial post, I never made it past B. That was something I considered early on but I wasn't able to change slots. Got the unknown var error.
ahm_usa said:
Flash the official Factory images first
Click to expand...
Click to collapse
Dude. Seriously?
Moto G Stylus Metro PCS brand:
I'm brand new to this subject so please forgive any ignorance. I'm decent with linux but new to android stuff.
Tried flashing the latest weekly build of OmniROM - now seems to be stuck at boot screen and won't go past. I am coming from latest OTA update from Motorola.
Phone was not rooted prior to starting this.
I also accidentally wiped slot A with my factory image on it (oops).
TWRP did not ask for any decryption key so I ran:
fastboot erase userdata
and this seemed to fix errors that I was getting while flashing with respect to denying access.
What I've done:
-Unlocked bootloader
-Installed TWRP 3.5.0-10 from the g-stylus forum.
-wiped and formatted via TWRP
-flashed 5/23 weekly build of OmniROM
Now no matter what I do or what slot I flash to it will not get past the Omni boot load animated screen. I've run this for almost 2 hours and nothing happens.
Any ideas?
Thanks!
nutsnax said:
Moto G Stylus Metro PCS brand:
I'm brand new to this subject so please forgive any ignorance. I'm decent with linux but new to android stuff.
Tried flashing the latest weekly build of OmniROM - now seems to be stuck at boot screen and won't go past. I am coming from latest OTA update from Motorola.
Phone was not rooted prior to starting this.
I also accidentally wiped slot A with my factory image on it (oops).
TWRP did not ask for any decryption key so I ran:
fastboot erase userdata
and this seemed to fix errors that I was getting while flashing with respect to denying access.
What I've done:
-Unlocked bootloader
-Installed TWRP 3.5.0-10 from the g-stylus forum.
-wiped and formatted via TWRP
-flashed 5/23 weekly build of OmniROM
Now no matter what I do or what slot I flash to it will not get past the Omni boot load animated screen. I've run this for almost 2 hours and nothing happens.
Any ideas?
Thanks!
Click to expand...
Click to collapse
Weekly builds may be unstable. I'm actually curious on how you got a hold of such build for the this device. Most, if not all ROMs are unofficial for the stylus and updates for each rom varies by contributed developers.....
However, you say you're decent with Linux. I'm sure there's some developers here that would help you with various tools to learn on how to make your own version of any type of OS.
As for OmniRom, I'd probably ask @vache for some help, for he has his own unofficial version.
Also, I recommend that you have the latest platform tools and the moto software tool if you don't have these yet...
nevermind I got it working. I was flashing p2pstate.bin directly (somehow this works?) when instead I was supposed to extract the image files and flash the respective files.
Seems to boot up now. Thanks!
nutsnax said:
nevermind I got it working. I was flashing p2pstate.bin directly (somehow this works?) when instead I was supposed to extract the image files and flash the respective files.
Seems to boot up now. Thanks!
Click to expand...
Click to collapse
That's good you got it to work. One developer once told me, when all else fails, think outside of the box. You'll eventually get it to work somehow
I have your solution cuz I went through the same thing.. you have to start out with stock Android 10 so you have to be bootloader unlocked and rooted that way you can downgrade your software and it's only the super images that you have to downgrade.. so just flash your supers and you'll be fine but they have to be stock Android 10 it doesn't matter what firmware version because you're keeping the same modem file