restoring a cloud-backup? - OnePlus 5 Questions & Answers

Hello,
when having installed a custom Rom on Oneplus 5 and in the Initial setup-wizard I want to restroe a cloud-backup, the Screen just goes white.
No matter which gapps I use.
Any help?

Any help?

Not exactly help but that crap never really worked for me except back in Nexus 5x times.
But due to custom ROM it is possible that the corresponding service was disabled so you get a blank screen

Related

Big problems with my Ascend G7-L03

Hello everybody,
I'm relatively new to the world of ROMs and I'm hoping some people smarter than me can help.
A few weeks ago, I started having issues with my phone, on the stock ROM for Wind Canada, restarting continuously. It would sometimes work for up to 10 hours, but sometimes no longer than 10 seconds. There didn't seem any rhyme or reason to it doing so. I figured that it was a good time to play around with a new ROM, and I took a backup (of a faulty operating system). It's been a bit of a ****show since then, and I don't remember exactly everything that I've tried, but here is a sampling:
CM13.1 - the ROM successfully loads, but then I get stuck in a reboot loop.
CM12.1 - I figured that if 13.1 didn't work, I shouldn't try 14.1, so I went down to 12.1. This worked beautifully, until I tried to make a call - and I can't hang up. To hang up, I need to reboot the phone. Annoying, to say the least. Everything else seems to work really well, other than a slightly shortened battery life, but I can live with that, if everything else works.
CM14.1 - I tried loading it, but it says right off the bat that the L03 isn't part of the compatible list and doesn't process. I know I can suppress that message, but I figured that if it was meant to be on that list, it would be.
Resurrection 5.1 - I don't remember what happened here, but I think it ended up in a bootloop.
I can't find the original ROM on Huawei's site, and the one that seem similar for different countries are meant to be done within the OS as an update (Update.app).
So, I'm stuck here - I can't seem to revert back to the original ROM (which was Android 4.4.4, which was fine), and I can't seem to update to any other ROMs. I want to fix this, because as far as I'm concerned, the hardware is pretty good and I can make this phone last. However, my wife is pushing me to replace it...
Does anybody have any advice as to what I should try next? I really don't feel like using CM12.1 in its current state, which is what is installed now, since I need to reboot between phone calls, but it seems to be my only option for now.
Three notes - 1) I am currently on my 5th or so install of CM12.1. I have tried to look for ways to replace the dialer, since that seems to be the problem, but I haven't found a way. Can one replace the stock dialer?
2) I have tried installing multiple GAPPs packages, including ones that supposedly replace the dialer, but this hasn't helped.
3) I don't know if this is relevant, but in CM12.1, under "About phone", my Device model is "unknown". Is that always the case?
Somebody out there must have a better solution and my hair's all gone now, from me pulling it out...
Any help you can give me is appreciated!!!
Thanks,
Steve
UuUuPpPp....
Exactly in the same boat as Steve...... "Cant hang up" is seems to be the only major problem.....i have the exact phone too.....and tried same things too to no help....any help wud be appreciated...

half blue half black screen after flashing a rom

hi everyone.
i am having this wierd issue for a month or so, when i try to update RR rom.
after i flash the rom, i get the screen attached. screen seems for like 2 seconds, and goes this half black / half blue screen. screen is still responsive, i can receive calls and if i double tap anywhere, screen locks. there is no problem with screen on twrp or anything ( because sometimes after flashing the rom i dont get this screen, so i don't do anything else, except use it normally.) but today it happened without a reason, the phone was in my pocket when i took it out and saw the screen in this state.
i always flash by following the steps given. i know it is not hardware related. where is the problem? what do i need to do?
p.s. : when charging, blue part goes yellow.
thank you all, waiting for a solution
rukenau said:
hi everyone.
i am having this wierd issue for a month or so, when i try to update RR rom.
after i flash the rom, i get the screen attached. screen seems for like 2 seconds, and goes this half black / half blue screen. screen is still responsive, i can receive calls and if i double tap anywhere, screen locks. there is no problem with screen on twrp or anything ( because sometimes after flashing the rom i dont get this screen, so i don't do anything else, except use it normally.) but today it happened without a reason, the phone was in my pocket when i took it out and saw the screen in this state.
i always flash by following the steps given. i know it is not hardware related. where is the problem? what do i need to do?
p.s. : when charging, blue part goes yellow.
thank you all, waiting for a solution
Click to expand...
Click to collapse
First go to recovery and check that display problem present or not if not then flash any other custom rom or reflash rr
if you are unable to go to recovery then flash stock rom via odin it will fix every software related issue
and if flashing stock rom doesn't work then it may be hardware issue
You confirmed the model # in download mode? Tried using different version of TWRP?
I am facing same problem recently, did you find any solution ?
still no solution. this problem is not hardware related since i can use it perfectly now. i tried to flash (via twrp) RR-N-v5.8.5 exactly as described in op. rom boots, i can see the home screen for a brief moment but screen goes immediately black and blue. i can receive calls, lock and wake screen, that's all. then i have to restore everything. i am currently on hexagon rom v2.5 and no issues but i like RR.
again, this problem is not hw related. i follow all the steps again and again checking everything..
any ideas?
blue screen
rukenau said:
still no solution. this problem is not hardware related since i can use it perfectly now. i tried to flash (via twrp) RR-N-v5.8.5 exactly as described in op. rom boots, i can see the home screen for a brief moment but screen goes immediately black and blue. i can receive calls, lock and wake screen, that's all. then i have to restore everything. i am currently on hexagon rom v2.5 and no issues but i like RR.
again, this problem is not hw related. i follow all the steps again and again checking everything..
any ideas?
Click to expand...
Click to collapse
make a clean install and try a different kernel than pre installed one
maniwaraich said:
make a clean install and try a different kernel than pre installed one
Click to expand...
Click to collapse
clean install worked for a day or so, until i turned off ambient dislpay and restart. then it went blue&black again.
i tried a few kernels, some bootloaders and modems (including nordic) but problem persists.
i will try to get a logcat :/
In case anyone has the same problem: reboot to safe mode, go to settings, flip cover and turn off S-View flip cover.
Same issue un lineage og 15.0 and 15.1 on samsung galaxy S 5 mini G800F someone find a solution?
pierpa2 said:
Same issue un lineage og 15.0 and 15.1 on samsung galaxy S 5 mini G800F someone find a solution?
Click to expand...
Click to collapse
Read thread .
Flash stock rom and test .
But this is the Note 3 forum not your phones forum .
JJEgan said:
Read thread .
Flash stock rom and test .
But this is the Note 3 forum not your phones forum .
Click to expand...
Click to collapse
lareay flashed lots of time differents ROM sorry for the wrong forum but i can't find a solution.
Stock rom with oreo does not exist.
Solved turning off smart cover

AGM phone with Lineage OS 14.1 issues

hi there,
I got a new AGM phone model A1Q some weeks ago, and I am manage to install LOS (unofficial) found on a China website, because the phone go wrong after trying to install Gapps, making none apps work.
After several trials, LOS install to the phone with working Gapps, however I got 2 issues right now.
1. the screen never come back after screen is off, I have to reboot the phone to get it back.
2. notification bar is not updating, I am using Nova Launcher right now, I tried disabled the notification bar and reboot, nothing happen.
For the moment, I am not able to get back TWRP recovery after installing LOS, I have to figure out other way to redo the LOS installation.
Please someone throw me some suggestions.
Sorry for my bad English.
algebrathebard said:
hi there,
I got a new AGM phone model A1Q some weeks ago, and I am manage to install LOS (unofficial) found on a China website, because the phone go wrong after trying to install Gapps, making none apps work.
After several trials, LOS install to the phone with working Gapps, however I got 2 issues right now.
1. the screen never come back after screen is off, I have to reboot the phone to get it back.
2. notification bar is not updating, I am using Nova Launcher right now, I tried disabled the notification bar and reboot, nothing happen.
For the moment, I am not able to get back TWRP recovery after installing LOS, I have to figure out other way to redo the LOS installation.
Please someone throw me some suggestions.
Sorry for my bad English.
Click to expand...
Click to collapse
Update:
Notification bar issue fixed after several reboot, but screen issue still exist.

Custom ROMs result in black screen

Hi all,
I'm new to the device so I'm maybe doing something wrong but I don't think so. I got the device with a terribly cracked, I flashed Pixel Experience (Android 10) as it's what I've had on my Nexus 5x, everything was working fine so I proceeded to replace the screen. I replaced it with one from Aliexpress which seems legit.
The phone then wouldn't boot, or seemed not to boot. I saw the splash screen then a black screen. The system did boot as I could see the capacative keys light up and sounds working, I just couldn't see any image on the screen. After a while trying to flash other ROMs and other TWRP versions (at this point TWRP showed up as a black screen too) I found that the following solution solved my problem.
https://forum.xda-developers.com/mi-a1/how-to/solved-mi-a1-bootloop-t3973131
This is fine, I can use the stock ROM and update it to the latest version but cannot use any AOSP based ROMS and still cannot use any other recovery apart from the one used to solve the "bootloop".
Does anyone have any idea how I can solve this? I thought the screen was maybe a weird version that needed some additional drivers but the strange thing is that it works for the stock ROM.
Regards,
Simon
Hi:
simonkerr said:
Hi all,
I'm new to the device so I'm maybe doing something wrong but I don't think so. I got the device with a terribly cracked, I flashed Pixel Experience (Android 10) as it's what I've had on my Nexus 5x, everything was working fine so I proceeded to replace the screen. I replaced it with one from Aliexpress which seems legit.
The phone then wouldn't boot, or seemed not to boot. I saw the splash screen then a black screen. The system did boot as I could see the capacative keys light up and sounds working, I just couldn't see any image on the screen. After a while trying to flash other ROMs and other TWRP versions (at this point TWRP showed up as a black screen too) I found that the following solution solved my problem.
https://forum.xda-developers.com/mi-a1/how-to/solved-mi-a1-bootloop-t3973131
This is fine, I can use the stock ROM and update it to the latest version but cannot use any AOSP based ROMS and still cannot use any other recovery apart from the one used to solve the "bootloop".
Does anyone have any idea how I can solve this? I thought the screen was maybe a weird version that needed some additional drivers but the strange thing is that it works for the stock ROM.
Regards,
Simon
Click to expand...
Click to collapse
I'm in the same situation. I think these screens are not 100% compatible so it seems a hardware issue.
Maybe using vendor partition but i'm so stucked as you.
My phone can't hotboot any official recovery although i can boot flashed recovery only if i boot slot a not slot b.
Stock roms boot always using slot a but tried Lineage (thats uses slot b) and got always black screen.
I'll keep reading and trying to solve it.
Regards.
simonkerr said:
Hi all,
I'm new to the device so I'm maybe doing something wrong but I don't think so. I got the device with a terribly cracked, I flashed Pixel Experience (Android 10) as it's what I've had on my Nexus 5x, everything was working fine so I proceeded to replace the screen. I replaced it with one from Aliexpress which seems legit.
The phone then wouldn't boot, or seemed not to boot. I saw the splash screen then a black screen. The system did boot as I could see the capacative keys light up and sounds working, I just couldn't see any image on the screen. After a while trying to flash other ROMs and other TWRP versions (at this point TWRP showed up as a black screen too) I found that the following solution solved my problem.
https://forum.xda-developers.com/mi-a1/how-to/solved-mi-a1-bootloop-t3973131
This is fine, I can use the stock ROM and update it to the latest version but cannot use any AOSP based ROMS and still cannot use any other recovery apart from the one used to solve the "bootloop".
Does anyone have any idea how I can solve this? I thought the screen was maybe a weird version that needed some additional drivers but the strange thing is that it works for the stock ROM.
Regards,
Simon
Click to expand...
Click to collapse
Have you made any progress?
gsausalito said:
Have you made any progress?
Click to expand...
Click to collapse
Thanks for your interest but I've made no progress and actually given up on it. I'm sure the issue could be resolved by buying a new, more compatible screen but I'm not going to put any more money into the phone.
As far as the software solution goes, I've tried almost every combination of ROM + Kernel i can think of but the only thing that works is the stock ROM.
I'm going to close this thread as I don't think it's much use to anyone.
Regards
Sorry for posting here, but i am in the same and i noticed that flashing canting 4.9 kernel gives display for like 8 seconds after screen turns off. May it be a kernel config issue? if anyone in this forum could answer this i could try and change it. Also flashing stock kernel on custom rom solves the problem but makes other thing fail
Hello, I've got the same issue. Is there any solution ? Or, at least, any clue to work on it ?
EDIT: I finally done it!
with this kernel (OC) : https://forum.xda-developers.com/t/...rkernel-v3-1-nonoc-and-oc-12-11-2020.4186317/
And this rom : https://forum.xda-developers.com/t/rom-11-0-official-crdroid-7-1-tissot-13-11-2020.4195351/
I installed this kernel, cause you was saying it is probably a kernel issue, so I tried to look for most recent kernel.
And then, it worked, so I think you was right.
I can't be sure it will work with all ROM, but I think.
Hello Mi A1 friends.
So yesterday I decided to change my crack LCD screen and to my surprise the phone boots into Xiaomi Logo and then after that its just a black screen. Message and other notifcation sounds still come in which means that the phone mange to boot into home screen, just with nothing to display. At the time of changing screen, I am on stock kernel and Pixel Experience 10.
Gonna flash back to stock pie(9) rom and see how it goes from there.
Deezio said:
Hello, I've got the same issue. Is there any solution ? Or, at least, any clue to work on it ?
EDIT: I finally done it!
with this kernel (OC) : https://forum.xda-developers.com/t/...rkernel-v3-1-nonoc-and-oc-12-11-2020.4186317/
And this rom : https://forum.xda-developers.com/t/rom-11-0-official-crdroid-7-1-tissot-13-11-2020.4195351/
I installed this kernel, cause you was saying it is probably a kernel issue, so I tried to look for most recent kernel.
And then, it worked, so I think you was right.
I can't be sure it will work with all ROM, but I think.
Click to expand...
Click to collapse
Sry for reply to an old post, but how did you do it? How did you flash kernel when you can't enter twrp because of screen issues? I have exact the same problem, where stock rom works but everything else cause blank screen. Also can't boot to twrp - probably the same reason.

My device keeps shutting down.

Hey!
It's my first time to customize my redmi note 7.
Before I unlock the bootloader and install pixel rom, I had once an experience that it shutted down when I was playing a video.
Then I unlock the bootloader and install the pixel experience plus based on android 12 rom, at first I was hesitant to do it but then I was amazed when I installed it. I notice that my battery isn't accurate at all because it's too fast to drain. Then another day, I'm planning to play music or video in my device but it shutted down, then keep restarting but isn't booting at all because it was stock on "Redmi based on android" then restart again. I was thinking that it was because of the rom I installed, so I installed another pixel rom which has the same problem occurs. So after searching for the solution, I read one statement that it could be on the rom I installed so I change on the Havoc OS (I tried going back to miui rom but it was sucks, it keeps crashing).
At first it was ok (Havoc OS) but then when I reboot my device it wasn't booting up at all unless I connect it to my charger. (The restarting problem and sound problem still occurs)
P.s. I followed all the instructions and watched how to install it, the clean flashing of roms.
It was my first time, so, I was thinking if it happens in your device too and could possibly give me some troubleshoot to fix it.
Thank you in advance! I hope you'll notice this thread!
Omyzerber said:
Hey!
It's my first time to customize my redmi note 7.
Before I unlock the bootloader and install pixel rom, I had once an experience that it shutted down when I was playing a video.
Then I unlock the bootloader and install the pixel experience plus based on android 12 rom, at first I was hesitant to do it but then I was amazed when I installed it. I notice that my battery isn't accurate at all because it's too fast to drain. Then another day, I'm planning to play music or video in my device but it shutted down, then keep restarting but isn't booting at all because it was stock on "Redmi based on android" then restart again. I was thinking that it was because of the rom I installed, so I installed another pixel rom which has the same problem occurs. So after searching for the solution, I read one statement that it could be on the rom I installed so I change on the Havoc OS (I tried going back to miui rom but it was sucks, it keeps crashing).
At first it was ok (Havoc OS) but then when I reboot my device it wasn't booting up at all unless I connect it to my charger. (The restarting problem and sound problem still occurs)
P.s. I followed all the instructions and watched how to install it, the clean flashing of roms.
It was my first time, so, I was thinking if it happens in your device too and could possibly give me some troubleshoot to fix it.
Thank you in advance! I hope you'll notice this thread!
Click to expand...
Click to collapse
you probably having same problem as me, your battery already die, just change it to the new one, problem fix
screenagers said:
you probably having same problem as me, your battery already die, just change it to the new one, problem fix
Click to expand...
Click to collapse
Omg! Thank you so much! I'll better do it.
Anyone know any legit fix?
Joaquin_Phoenix said:
Anyone know any legit fix?
Click to expand...
Click to collapse
Do you have the same issue? First time in customizing rom? Did you follow all steps in clean flash?

Categories

Resources