Related
Hi everyone,
I have some advanced questions so I'm reaching out to the geeky people out there for help.
Just a bit of backgroud, I have the OPPO find 7 and so far I managed to root it using guides online and to add Cyanogenmod on it and I'm comfortable so far installing CM 11 nightly build updates and doing things like backup/restore.
Recently during an update the phone was bricked and I managed to unbrick it myself following some guides online. After I unbricked it, I noticed that it was running Lollipop and that few things had changed. After I installed CM 11 I have been having problems so here's my questions:
a) I noticed the Logo during startup has changed and also the "fastboot" icon is different too. This seems to have nothing to do with the OS. Did I somehow manage to change the Kernel? Could all the problems I am having be caused by the change of Kernel?
b) How do we update the Kernel? Can I put it back to how it was when everything with was working?
c) If the startup logo and the fastboot is not related tot he Kernel, then what is it that I have accidentally changed?
d) A lot of people in forums make recommendations such as to "install COS model version blah", or use Nameless Rom version blah, or to do a full wipe first and then blah. I am extremely confused about all of these recommendations because I have hundreds of apps that are very specifically configured and if I have to do a full wipe it'll take me weeks to bring the phone to a state where it's useful to me.
Do all these people have a way of backing up all their apps and data? It sounds like a cosmic joke that I wasn't let it on.
I know how to do an image backup/restore but that changed the OS too. I am using TWRP, can that do a different type of backup that only backs up all the data/apps/cache but leaves OS independent?
nkomp18 said:
Hi everyone,
I have some advanced questions so I'm reaching out to the geeky people out there for help.
Just a bit of backgroud, I have the OPPO find 7 and so far I managed to root it using guides online and to add Cyanogenmod on it and I'm comfortable so far installing CM 11 nightly build updates and doing things like backup/restore.
Recently during an update the phone was bricked and I managed to unbrick it myself following some guides online. After I unbricked it, I noticed that it was running Lollipop and that few things had changed. After I installed CM 11 I have been having problems so here's my questions:
a) I noticed the Logo during startup has changed and also the "fastboot" icon is different too. This seems to have nothing to do with the OS. Did I somehow manage to change the Kernel? Could all the problems I am having be caused by the change of Kernel?
b) How do we update the Kernel? Can I put it back to how it was when everything with was working?
c) If the startup logo and the fastboot is not related tot he Kernel, then what is it that I have accidentally changed?
d) A lot of people in forums make recommendations such as to "install COS model version blah", or use Nameless Rom version blah, or to do a full wipe first and then blah. I am extremely confused about all of these recommendations because I have hundreds of apps that are very specifically configured and if I have to do a full wipe it'll take me weeks to bring the phone to a state where it's useful to me.
Do all these people have a way of backing up all their apps and data? It sounds like a cosmic joke that I wasn't let it on.
I know how to do an image backup/restore but that changed the OS too. I am using TWRP, can that do a different type of backup that only backs up all the data/apps/cache but leaves OS independent?
Click to expand...
Click to collapse
I will attempt to answer your questions. Forgive me if I didn't answer everything to your satisfaction.
A) How is your fastboot icon different? Any elaboration? Startup animation should (by right) be different every time you flash a custom ROM. For example, if you flash CM, you'll have the CM boot animation and not the Oppo boot animation. This issue shouldn't be caused by a change in kernel. Your boot animation is stored in system/media/bootanimation.zip. Not sure about fastboot though.
B) Kernels are updated when you flash a ROM. You will get the CM kernel when you flash a CM ROM, etc. If you want the stock kernel back, you'll need to flash COS (1.2.5i recommended)
C) Look at A), again, not sure about fastboot, need a pic or explanation.
D) Normally for me, when I run into a major issue, I simply download the ROM+GApps, boot into recovery, wipe system, cache and Dalvik cache then flash the ROM before GApps. This should solve most issues. If you run into radio/GPS issues, you'll have to back up your apps via TB or Helium, then copy your whole internal storage onto a computer (for backup purposes), then flash COS. Boot into COS, run a few apps, then flash your custom ROM. (Custom recovery first of course.)
P.S. how did you unbrick your device? I don't know any tool that flashes Lollipop when unbricking.
---------- Post added at 08:22 PM ---------- Previous post was at 08:21 PM ----------
If you have any questions feel free to ask.
This is still quite confusing then, because I still don't understand why the logo and the fastbook icon changed and also I don't understand why the phone loaded Lollipop. Before the logo was a gray "OPPO" but now it's a white one, with different font and it says Android at the bottom. The fastboot icon used to be a green android robot with a blue text saying "fastboot" if I remember correctly but now it shows chinese text with the OPPO emoticon.
I downloaded CM 11 latest nightly (which bricked my phone) and then I followed your guide to unbrick it. But instead of flashing COS as you recommended, I followed this recommendation here and used a unbrick_cm.zip which should, in theory, load CM 11, but instead it booted to Lollipop:
A problem was identified in the find7 nightlies for the 14th and they were pulled; unfortunately you and possibly a few others already installed it. The problem has been identified and a fix has been found:
http://www.oppoforums.com/threads/gu...nd-7-7a.23067/ provides a tool and instructions on how to return a bricked find7 to stock. The linked download includes the entire stock ColorOS rom, which isn't needed to fix this problem(and is over 1gb in download size!); an edited version can be found at https://mega.co.nz/#!SQNh2ShY!UlHUE8...fTuaP_CPYr9yfQ will fix the specific issue caused by this nightly without replacing the OS or wiping your data.
Use the unbrick_cm.zip with the instructions in the oppoforums post (I also had this problem but it wouldn't work on win7 but did on xp, so there may be some compatibility issues) and you should be good to go.
Click to expand...
Click to collapse
I am still quite confused about what happened to be honest. After the phone was unbricked I used an earlier image I had from a backup and restored the phone to that point, so If the kernel and OS are in the image then the logo and the fastboot menu should go back to exactly as they were before, but they didn't!
nkomp18 said:
This is still quite confusing then, because I still don't understand why the logo and the fastbook icon changed and also I don't understand why the phone loaded Lollipop. Before the logo was a gray "OPPO" but now it's a white one, with different font and it says Android at the bottom. The fastboot icon used to be a green android robot with a blue text saying "fastboot" if I remember correctly but now it shows chinese text with the OPPO emoticon.
I downloaded CM 11 latest nightly (which bricked my phone) and then I followed your guide to unbrick it. But instead of flashing COS as you recommended, I followed this recommendation here and used a unbrick_cm.zip which should, in theory, load CM 11, but instead it booted to Lollipop:
I am still quite confused about what happened to be honest. After the phone was unbricked I used an earlier image I had from a backup and restored the phone to that point, so If the kernel and OS are in the image then the logo and the fastboot menu should go back to exactly as they were before, but they didn't!
Click to expand...
Click to collapse
You should have used the tool I linked in my thread. It's by Addel (Oppo employee if I'm not wrong) so nothing should go wrong. I never heard if the unbrick_cm.zip before so... Yea, not recommended. You should use the tool I linked to install COS 1.2.5i then mess around with it. Nothing should go wrong.
P.S. never use third party tools for unbricking unless dev is recognised or well-known.
Using TWRP you can restore apps/data/cache independently from system - just check/uncheck the boxes.
Lord Childe said:
Using TWRP you can restore apps/data/cache independently from system - just check/uncheck the boxes.
Click to expand...
Click to collapse
I don't think it'll work if you restore apps/data from a COS while on CM. Learnt this the hard way by bricking my old Note 2
Irwenzhao said:
I don't think it'll work if you restore apps/data from a COS while on CM. Learnt this the hard way by bricking my old Note 2
Click to expand...
Click to collapse
I flashed Nightly on my 7a, restored app+data (TWRP) without a problem. But I had issues with the 'screen of death' on CM every time the phone was put in sleep mode, so I went back to stable color 1.2.7 and restored everything with TWRP. So my experience of it is OK.
You could always use Titanium to restore apps/data if you don't want to risk bricking again, although I can't see how restoring non-system apps/data can brick your phone.
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.
SOLVED
We have a Oneplus3 with root and LineageOS 14.1. Downloaded the LineageOS 15.1 and Googleapps and placed them on the root of the SD card. Turned off the phone, rebooted into TWRP, performed a backup and tried to Install the 15.1. It said something to the effect that we didn't have a Oneplus3 and didn't install. The error which is shown when trying to install the 15.1 is "E3004. This package is for device: OnePlus3, oneplus3, OnePlus3T, oneplus3t; this device is ."
Tried installing the backup but when it finishes "installing" and we reboot all we get is the "Your device is unlocked..." screen and then the "POWERED BY android" screen. It doesn't go beyond this screen.
What to do?
Have a great afternoon!
Well, don't know if we have success or not... i applied a solution from this forum to "boot into recovery and select 'fix contents' and reboot".
https://forum.xda-developers.com/oneplus-3/help/stuck-logo-flashing-rom-t3422304
i now have advanced to the blue curve with the moving circle, but it's been like this for some 10 minutes... - lol.
Have a great evening!
frazelle09 said:
Well, don't know if we have success or not... i applied a solution from this forum to "boot into recovery and select 'fix contents' and reboot".
https://forum.xda-developers.com/oneplus-3/help/stuck-logo-flashing-rom-t3422304
i now have advanced to the blue curve with the moving circle, but it's been like this for some 10 minutes... - lol.
Have a great evening!
Click to expand...
Click to collapse
Which version of TWRP do you have? Try eng.stk's (blu_spark)
tnsmani - i really appreciate your posting! i was under the impression that these threads were a little more "active" - lol. i'm at TWRP 9.8 and it's already the Blue spark...
i finally decided to bite the bullet and reinstall 14.1 from scratch since i couldn't get my backup to reinstall - grrr. So, with the help of ADB and my trusty PCLinuxOS the phone's back and running. Very disappointed my backup didn't work i have used it before - with a different backup - and didn't have any problems at all. i wonder what secret, unknown, black magic, undocumented step(s) i missed when i created it. It's not like it comes with a button you get to press after you create it which says: To Test Your Backup.
Again, thanks for offering to help. It seems like there are fewer of you around these days. And
have a wonderful day!
frazelle09 said:
tnsmani - i really appreciate your posting! i was under the impression that these threads were a little more "active" - lol. i'm at TWRP 9.8 and it's already the Blue spark...
i finally decided to bite the bullet and reinstall 14.1 from scratch since i couldn't get my backup to reinstall - grrr. So, with the help of ADB and my trusty PCLinuxOS the phone's back and running. Very disappointed my backup didn't work i have used it before - with a different backup - and didn't have any problems at all. i wonder what secret, unknown, black magic, undocumented step(s) i missed when i created it. It's not like it comes with a button you get to press after you create it which says: To Test Your Backup.
Again, thanks for offering to help. It seems like there are fewer of you around these days. And
have a wonderful day!
Click to expand...
Click to collapse
If your phone doesn't boot. Just wipe boot and system and flash the rom again or your old rom and it should work 90% of the time. These two partitions get overwrited when flashing a rom.
i tried doing that several times, but those must have been the other 10%...
Have a super evening!
frazelle09 said:
i tried doing that several times, but those must have been the other 10%...Have a super evening!
Click to expand...
Click to collapse
Please, tell us how did you solved your issue.
(You wrote"solve" in thé OP)
I extract the ROM and go to meta-inf/com/Google/android/ updater script and delete from first line start as assert to before ui print and save and compress and flash with out any problem.
Because all the roms had this problem even my Redmi note 4x, mi max2 had this same "E3004. This package is for device
problem in custom roms for past few months.
drmuruga said:
I extract the ROM and go to meta-inf/com/Google/android/ updater script and delete from first line start as assert to before ui print and save and compress and flash with out any problem.
Because all the roms had this problem even my Redmi note 4x, mi max2 had this same "E3004. This package is for device
problem in custom roms for past few months.
Click to expand...
Click to collapse
I have been using Vertex and PureFusion Nougat before without any issues. So all the ROMs (if at all any) don't have this issue. Plus everyone is not tech savvy and extracting, deleting and repacking are all a little above the average user.
---------- Post added at 05:16 PM ---------- Previous post was at 05:14 PM ----------
frazelle09 said:
tnsmani - i really appreciate your posting! i was under the impression that these threads were a little more "active" - lol. i'm at TWRP 9.8 and it's already the Blue spark...
i finally decided to bite the bullet and reinstall 14.1 from scratch since i couldn't get my backup to reinstall - grrr. So, with the help of ADB and my trusty PCLinuxOS the phone's back and running. Very disappointed my backup didn't work i have used it before - with a different backup - and didn't have any problems at all. i wonder what secret, unknown, black magic, undocumented step(s) i missed when i created it. It's not like it comes with a button you get to press after you create it which says: To Test Your Backup.
Again, thanks for offering to help. It seems like there are fewer of you around these days. And
have a wonderful day!
Click to expand...
Click to collapse
eng.stk's TWRP latest version is 8.61. I don't know where you got 9.8 and it is probably the culprit.
Donglip said:
Please, tell us how did you solved your issue.
(You wrote"solve" in thé OP)
Click to expand...
Click to collapse
Please see the fourth post of this thread.
Have a great morning and a beautiful day in Paris!
eng.stk's TWRP latest version is 8.61. I don't know where you got 9.8 and it is probably the culprit.
Click to expand...
Click to collapse
You are correct. My version is 9.8 - my bad. Who knows why it didn't work. Maybe it would be a good idea for me to wait till the next version before i try again. i don't know if you saw it or not, but i also mentioned that my Backup (that i made through TWRP) before trying to upgrade did not work, either. i wouldn't have been so freaked out if it had since i've had to use them before, but this time it wouldn't reinstall. i'm wondering if i missed some vital, hidden, secret sign or step before making the backup - deleting the /temp folder, upgrading to Windoze 11 - something. There seems like there's always - something - lol.
Have a super day! It looks like threads get more love after the issue has been solved than when the OP is in the process of trying to figure out what's happening... but it could just be me and my sample methodology - lol.
Hi!
Since the official OxygenOS Android 10 update left me less than happy, I decided to try and give a custom ROM a chance again. Had RR on my OPO a few years back so that felt like a good thing to default back to, but for OP5t. Unlocked the bootloader, got TWRP 3.3.1 installed. All good. Got RR8.1.0 for dumpling downloaded, also downloaded gApps and magisk. Transferred them over, installed the .zip's. So far so good. Booting into RR seems fine at first, but when I get to the point of backing up my data from a previous device/or skipping it, the installer freezes/loops/fails.
I assume I have the correct firmware since OxygenOS 10 works "just fine". When I try to recover stuff from an old device, I choose my old backup from yesterday, then it goes into a screen where it says "Wait a few secs..." or something of that nature. The circle around it just keeps looping. This takes only a few seconds to find the data if I'm installing OOS. So this is a dead end. If I try to pass through without anything, accounts, face unlock and all that, I get to a point of where I am supposed to setup the assistant. Whether I choose "Skip" or "Next" (as in set it up) I keep looping back 2 steps to enter pin, then set up the assistant again.
I have re-installed RR a bunch of times as it didn't work, first I had problems with "Enter device pin" which I had no clue what it was in the android setup. Cleaned it all up, installed OOS10, that worked to setup and install just fine. Cleared it all out again, tried to install RR, got past the "Enter device pin", but then it failed as mentioned above.
TL;DR: RR8.1.0 Dumpling Android setup fails when backing up from account/can't get past assistant. OOS10 works as it should.
Any clue on what the problem might be? Tried installing at least 10 times, but it didn't work. Any help is appreciated If there's just some general flaw in RR for this device/version, any other custom ROM that is to be recommended?
/Wahlmat
wahlmat said:
Hi!
Since the official OxygenOS Android 10 update left me less than happy, I decided to try and give a custom ROM a chance again. Had RR on my OPO a few years back so that felt like a good thing to default back to, but for OP5t. Unlocked the bootloader, got TWRP 3.3.1 installed. All good. Got RR8.1.0 for dumpling downloaded, also downloaded gApps and magisk. Transferred them over, installed the .zip's. So far so good. Booting into RR seems fine at first, but when I get to the point of backing up my data from a previous device/or skipping it, the installer freezes/loops/fails.
I assume I have the correct firmware since OxygenOS 10 works "just fine". When I try to recover stuff from an old device, I choose my old backup from yesterday, then it goes into a screen where it says "Wait a few secs..." or something of that nature. The circle around it just keeps looping. This takes only a few seconds to find the data if I'm installing OOS. So this is a dead end. If I try to pass through without anything, accounts, face unlock and all that, I get to a point of where I am supposed to setup the assistant. Whether I choose "Skip" or "Next" (as in set it up) I keep looping back 2 steps to enter pin, then set up the assistant again.
I have re-installed RR a bunch of times as it didn't work, first I had problems with "Enter device pin" which I had no clue what it was in the android setup. Cleaned it all up, installed OOS10, that worked to setup and install just fine. Cleared it all out again, tried to install RR, got past the "Enter device pin", but then it failed as mentioned above.
TL;DR: RR8.1.0 Dumpling Android setup fails when backing up from account/can't get past assistant. OOS10 works as it should.
Any clue on what the problem might be? Tried installing at least 10 times, but it didn't work. Any help is appreciated If there's just some general flaw in RR for this device/version, any other custom ROM that is to be recommended?
/Wahlmat
Click to expand...
Click to collapse
Maybe it's because u trying to install 8.1 ROM on pie firmware just a thought?
ireaper4592 said:
Maybe it's because u trying to install 8.1 ROM on pie firmware just a thought?
Click to expand...
Click to collapse
Could be. Tried to search for A10 firmware, but came up short (had this issue with my OPO and firmware for A7). Got AICP installed now and that seems to work.
Out of curiosity, does OnePlus release the firmware openly, or do you have to find some guy's "homemade" firmware in a future case like this?
wahlmat said:
Could be. Tried to search for A10 firmware, but came up short (had this issue with my OPO and firmware for A7). Got AICP installed now and that seems to work.
Out of curiosity, does OnePlus release the firmware openly, or do you have to find some guy's "homemade" firmware in a future case like this?
Click to expand...
Click to collapse
They have all firmwares on there sight go there and click three lines,go to support,look for device and find latest firmware download that's it
ireaper4592 said:
They have all firmwares on there sight go there and click three lines,go to support,look for device and find latest firmware download that's it
Click to expand...
Click to collapse
I actually can't seem to find it on their site.
wahlmat said:
I actually can't seem to find it on their site.
Click to expand...
Click to collapse
https://www.oneplus.com/uk/support/softwareupgrade
Hey guys, if you're a noob or you haven't flashed a custom ROM to an android device since the likes of the Galaxy S2 like me, this guide is made for you!
Disclaimer: I am by no means taking credit for any links posted, credits to the creators of anything mentioned! And a special thank you to the creators of the TWRP and the ROM, hopefully development will grow for such an awesome device! I am not responsible if you brick your device (by not following my tutorial :/)
The only complaints I have about this ROM is the camera quality but install the GCAM port for the Mi10T Lite, it may help!
You will need:
A Mi10T Lite (duh) or any other supported device with MIUI Installed (Android 10)
A SD card
A laptop with fastboot installed ( [OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 | XDA Developers Forums (xda-developers.com) )
A Mi account
TWRP (https://www.mediafire.com/file/qaea...0I_3.5.A10_05-01-2021_BL-L-fixsdcard.img/file)
The ROM (https://forum.xda-developers.com/t/rom-unofficial-10-0-gauguin-lineageos-17-1.4224633/)
GApps (I used this one: Download NikGapps from SourceForge.net)
B*lls
First (Ignore this if you already unlocked your bootloader):
Download MiFlash_Unlock (http://miuirom.xiaomi.com/rom/u1106245679/4.5.813.51/miflash_unlock-en-4.5.813.51.zip)
Make sure you have a Mi account and a SIM
Go to settings, enable developer options
Once you have done this, go to developer options (additional settings, scroll down)
Enable OEM Unlocking
Enable USB Debugging (not sure if this is necessary but I like to have it enabled anyway)
Click on Mi Unlock status and add your account, remember your details! (You may need to sign out and sign back in again)
It should say account linked to device successfully or something along those lines
Grab a cable (the included cable worked for me but other cables didn't)
OPTIONAL: YOU MAY WANT TO BACK UP ALL OF YOUR DATA
Open MiFlash_Unlock which you previously downloaded and connect your phone in fastboot mode (if it doesn't show up follow this tutorial: Fixed: Fastboot not detecting your Android device (qasimtricks.com) )
Click on unlock device! It should automatically reboot when it's done
Complete the set-up process, input your Mi account details and you should be good to go!
Enable developer options again and enable USB debugging
Installing TWRP (Ignore this if you already have TWRP installed!):
Turn off your device and boot into fastboot, connect and verify that it is connected by opening command prompt then typing "fastboot devices", it should show up
Point command prompt to the folder where your TWRP is downloaded (if it is located in downloads, type cd c:/users/(your username)/downloads
Then type fastboot flash recovery "twrp".img (replace "twrp" with the name of the recovery installed)
It should say successful, then type fastboot reboot and hold volume up + power
You've booted into TWRP! Hooray!
If it asks for the password to decrypt put it in, if it doesn't then no worries
You will notice that your internal storage is encrypted, not to worry!
Installing the ROM:
Connect your phone to your laptop (it can be in TWRP) and move the ROM to your SD card
Boot into TWRP if you haven't already, click wipe, advanced wipe and wipe Dalvik Cache/ART, Data and Cache
Once this has completed, go to install, then change the storage to SD Card
Locate the ROM file and swipe to flash!
Once the flash has completed, DO NOT REBOOT
Go to wipe and click format data, then type yes
Reboot to system! Done!
Installing GApps (Optional):
Move the GApps file provided to your phone
Boot to TWRP
It will prompt you to enter your passcode, this will decrypt the internal storage!
Click on install and locate GApps, swipe and flash!
Reboot
Congratulations! You have installed the first custom ROM made specifically for the device You can install Magisk if you want, I'm in the UK and my metro bank app didn't work but by using Magisk hide and changing the name of the Magisk manager everything worked (hide every Google app)
Enjoy! I hope you found this useful
thanks, after installing it can i go back to stock with locked bootloader?
jeuxtype said:
thanks, after installing it can i go back to stock with locked bootloader?
Click to expand...
Click to collapse
yes you can using xiaomi flash tool
Might want to confirm when to install gapps as if it's done after a boot it's not going to work!
Chari69 said:
yes you can using xiaomi flash tool
Click to expand...
Click to collapse
so it's safe to flash lineage, i want to use it but i need to get back to stock to watch netflix and for google pay?
jeuxtype said:
so it's safe to flash lineage, i want to use it but i need to get back to stock to watch netflix and for google pay?
Click to expand...
Click to collapse
Yes its safe, download the stock fastboot ROM online and use miFlash as mentioned, before you start flashing make sure the setting at the bottom right of the app is set to wipe + lock, I've already done it once and it worked fine
benfleet5 said:
Might want to confirm when to install gapps as if it's done after a boot it's not going to work!
Click to expand...
Click to collapse
Hey, that's awfully weird. When I tried flashing alongside the ROM I kept getting an error, but after I booted and done initial set up and tried installing it worked fine
Good guide a++++
deanlee121 said:
Good guide a++++
Click to expand...
Click to collapse
Thanks Dean!
Google pay works on this?
Xts7 said:
Google pay works on this?
Click to expand...
Click to collapse
Yeah just changed the magisk package name, enabled magisk hide and used gpay sqlite fix and it was all working. Metro Bank worked too
The only thing I'd say is that Open GApps Micro is the package you want to install; anything larger won't fit in the system partition - you get an Error 70! JT
jdtanner said:
The only thing I'd say is that Open GApps Micro is the package you want to install; anything larger won't fit in the system partition - you get an Error 70! JT
Click to expand...
Click to collapse
Hey, I've just been made aware that that works too, but NikkGapps also works! Also, ArrowOS comes pre-built with GApps and it's better imo, only thing is bluetooth audio doesn't work and the speaker crackles occasionally.
fizzy900 said:
Hey, I've just been made aware that that works too, but NikkGapps also works! Also, ArrowOS comes pre-built with GApps and it's better imo, only thing is bluetooth audio doesn't work and the speaker crackles occasionally.
Click to expand...
Click to collapse
Waiting until these bugs are sorted before trying that ROM. Bluetooth and general audio are fairly important to me
jdtanner said:
Waiting until these bugs are sorted before trying that ROM. Bluetooth and general audio are fairly important to me
Click to expand...
Click to collapse
Same somewhat lol, its annoying but thank God my headphones have a 3.5mm jack too!
Thanks for the guide, I recently got a redmi note 9 pro 5g from chinaland shipped to the uk then followed this guide pretty much, but instead of going twrp and lineage I went Orangefox and Arrow OS
I wasn't sure how all would go so was grateful of the guide as my first flashing on the new beasty..
I used this guide + info from the arrow thread before I jumped in..
just for info's it worked flawlessly
Steps I did
1. Unlocked bootloader ofcourse
2. installed Orangefox via fastboot
3. flashed latest version of china android 10 from sdcard (no reboot)
4. flashed arrow OS android 11 from sdcard
5. wiped data
To my amazement it booted first go and real fast like in under 5min!
can somebody explain why we need to wipe data after flashing ? surely wiping data means wiping ? but I guess it is not somehow wiping the good flash data..?
Where does all the data go when I flashed the first chinarom and why is it required to flash chinarom first ?
I have one bug bar the odd crackle, has anyone else noticed keyboard issues ? When i type sometimes it shows up backwards
ie google will appear as elgoog ?
I tried swiftkey keyboard + changing languages still the issue persists..
Thanks again @ Fizzy900
Jonny5isalivetm said:
Thanks for the guide, I recently got a redmi note 9 pro 5g from chinaland shipped to the uk then followed this guide pretty much, but instead of going twrp and lineage I went Orangefox and Arrow OS
I wasn't sure how all would go so was grateful of the guide as my first flashing on the new beasty..
I used this guide + info from the arrow thread before I jumped in..
just for info's it worked flawlessly
Steps I did
1. Unlocked bootloader ofcourse
2. installed Orangefox via fastboot
3. flashed latest version of china android 10 from sdcard (no reboot)
4. flashed arrow OS android 11 from sdcard
5. wiped data
To my amazement it booted first go and real fast like in under 5min!
can somebody explain why we need to wipe data after flashing ? surely wiping data means wiping ? but I guess it is not somehow wiping the good flash data..?
Where does all the data go when I flashed the first chinarom and why is it required to flash chinarom first ?
I have one bug bar the odd crackle, has anyone else noticed keyboard issues ? When i type sometimes it shows up backwards
ie google will appear as elgoog ?
I tried swiftkey keyboard + changing languages still the issue persists..
Thanks again @ Fizzy900
Click to expand...
Click to collapse
Hey bro, nice glad you enjoyed! So you have to format data after flashing a custom ROM from what I know in order to remove encryption, if you don't it'll show your internal files in a strange way and if you further tinker with it and do something it might stop you from installing apps full stop (happened to me cause I was being a tw*t lol). You need to flash the latest stock firmware (if the ROM requires you to) so you get the latest vendors which work with the custom ROM, although I believe there is a method to just flash vendor images themselves (fastboot flash vendor nameofvendorfile.img).
Yeah so arrowOS has notification crackles for some reason, most of the bugs are audio related (BT audio doesn't work either).
My typing was backwards too sometimes, it's because you're touching the fingerprint slightly which goes to the first element on a page or something (when you're typing it goes to the start of the box where you enter text). To understand what I mean go onto your launcher and tap the fingerprint scanner, it should highlight something.
I just flashed dotOS from arrow, works a charm! No audio related bugs afaik and BT audio works (lifesaver, phew).
Any other questions feel free to drop me a message on Telegram, @stillw0rking.
Take care! Also how in the world did you import the device from China hahahaha
epic fast reply!
<3
ahha the fingerprint!! I was wondering why I got random white box appearing on my home screen (and at random times) can it be disabled ?
So we got another rom already lol how excellent, I would like a rom that is stripped to the bone so we can install what we like, aka the least amount of crap running in the backround the merrier I am
Yea I just ordered from one of the china phone shops, got a note 9 pro 5g for £ 211 including postage, when I saw the price I just had to buy even tho my trusty oneplus 3t is still fine but but had the upgrade bug hehe, was from giztop, risked the custom charge and succeeded haha
Finally thanks for explaining the Encryption bit, yes I did read that but it seemed to go in one ear...
Guessing you are on the mainland somewhere, Greetings from across the pond
Jonny5isalivetm said:
epic fast reply!
<3
ahha the fingerprint!! I was wondering why I got random white box appearing on my home screen (and at random times) can it be disabled ?
So we got another rom already lol how excellent, I would like a rom that is stripped to the bone so we can install what we like, aka the least amount of crap running in the backround the merrier I am
Yea I just ordered from one of the china phone shops, got a note 9 pro 5g for £ 211 including postage, when I saw the price I just had to buy even tho my trusty oneplus 3t is still fine but but had the upgrade bug hehe, was from giztop, risked the custom charge and succeeded haha
Finally thanks for explaining the Encryption bit, yes I did read that but it seemed to go in one ear...
Guessing you are on the mainland somewhere, Greetings from across the pond
Click to expand...
Click to collapse
Haha yes I'm from near London! You must be the first English person I've actually bumped across on XDA ever lol. Aah yes, as far as I know it can't be disabled, it'll be stuck w that until the dev fixes it... ROMs have started to release quite quickly for the phone ever since the mi10i got dropped thank God, hopefully this is a good sign!
DotOS seems to be pretty light, heavy on the customizing side but when I started from fresh I had the basic google apps but gmail wasn't even installed lol. Dot is giving me the same sort of sot as Arrow, so really its up to you, but if the BT audio bug is a major thing for you (thank God one of my headphones can be used with a 3.5mm jack too lol) then I'd recommend Dot, but otherwise they're both extremely similar in terms of performance
And I was gna try and order the mi9T Pro like that but didn't bother, read some bad stories lol.
And no worries But yeah I'm pretty sure that is all it is, when you modify /system or something, the internal storage encrypts so you can't access it on stock ROM with TWRP but with custom you can decrypt easily
Take care mate!
Does lineage for mi 10t lite support 120 hz on screen ? Is it adaptive or locked?