is this normal? - OnePlus 7 Pro Questions & Answers

Hey guys,
I recently decided to go back to OOS and everything went fine except its installed to slot b (slot a just boot loops) is this normal?

The_Keeper86 said:
Hey guys,
I recently decided to go back to OOS and everything went fine except its installed to slot b (slot a just boot loops) is this normal?
Click to expand...
Click to collapse
Nope, both should work fine. flash with EDL mode again.

superac11 said:
Nope, both should work fine. flash with EDL mode again.
Click to expand...
Click to collapse
Thanks I appreciate the reply. I haven't had any issue with it so I may keep it the way it is for now. I was just wondering if it was normal and has happened to others before.

Related

Oneplus One LTE Issue

Dear All,
I don't know if I have posted it at the right place if I have not please guide me.
I tried my best to find a solution but couldn't that's why I am posting this.
So here I begin,
I am using OnePlus One from last 2 years and it is still working fine.
I have spent most of the time on Sultan's Rom which ran without any issues.
Recently I flashed [ROM][OFFICIAL][7.1.1_r9][BACON][OPTIMIZED]RESURRECTION REMIX [5.8.0] Rom and it worked well too.
But all of a sudden I started experiencing LTE signal drop.
I always do Nandroid backups so I restored to Sultan Rom but the problem was still there.
I have tried flashing modems with no luck.
Now I have started experiencing intermittent 3G signal too.
I have even tried restoring old KK backups but that doesn't resolve the problem.
This is so frustrating, Please help.
Let me know if more information is needed.
iamvashisht said:
Dear All,
I don't know if I have posted it at the right place if I have not please guide me.
I tried my best to find a solution but couldn't that's why I am posting this.
So here I begin,
I am using OnePlus One from last 2 years and it is still working fine.
I have spent most of the time on Sultan's Rom which ran without any issues.
Recently I flashed [ROM][OFFICIAL][7.1.1_r9][BACON][OPTIMIZED]RESURRECTION REMIX [5.8.0] Rom and it worked well too.
But all of a sudden I started experiencing LTE signal drop.
I always do Nandroid backups so I restored to Sultan Rom but the problem was still there.
I have tried flashing modems with no luck.
Now I have started experiencing intermittent 3G signal too.
I have even tried restoring old KK backups but that doesn't resolve the problem.
This is so frustrating, Please help.
Let me know if more information is needed.
Click to expand...
Click to collapse
I'd do a complete clean restore of last official stock. If the issue still persists, it must be a hardware issue or an issue with your carrier.
If your device is wiped clean and stock software restored, there's no way it can be a software issue.
Good luck!
iamvashisht said:
Dear All,
I don't know if I have posted it at the right place if I have not please guide me.
I tried my best to find a solution but couldn't that's why I am posting this.
So here I begin,
I am using OnePlus One from last 2 years and it is still working fine.
I have spent most of the time on Sultan's Rom which ran without any issues.
Recently I flashed [ROM][OFFICIAL][7.1.1_r9][BACON][OPTIMIZED]RESURRECTION REMIX [5.8.0] Rom and it worked well too.
But all of a sudden I started experiencing LTE signal drop.
I always do Nandroid backups so I restored to Sultan Rom but the problem was still there.
I have tried flashing modems with no luck.
Now I have started experiencing intermittent 3G signal too.
I have even tried restoring old KK backups but that doesn't resolve the problem.
This is so frustrating, Please help.
Let me know if more information is needed.
Click to expand...
Click to collapse
if clean flash through fastboot don't work out,try changing network antenna.
I don't think it's a carrier issue because it was perfect before.
The problem in network antenna must've been due to sudden drops or heavy impact.
Mr.Ak said:
if clean flash through fastboot don't work out,try changing network antenna.
I don't think it's a carrier issue because it was perfect before.
The problem in network antenna must've been due to sudden drops or heavy impact.
Click to expand...
Click to collapse
Hi, thank you for replying.. Flashing stock ROM from fastboot is different than flashing it from twrp recovery?
Please let me know if it is.
I will certainly give it a try then.
Darth said:
I'd do a complete clean restore of last official stock. If the issue still persists, it must be a hardware issue or an issue with your carrier.
If your device is wiped clean and stock software restored, there's no way it can be a software issue.
Good luck!
Click to expand...
Click to collapse
Hi, thanks for replying... I will do a clean install, does it need to be done via fastboot or just recovery?
And do I need to wipe internal storage too?
Since fresh installs via recovery couldn't resolve the problem..
iamvashisht said:
Hi, thanks for replying... I will do a clean install, does it need to be done via fastboot or just recovery?
And do I need to wipe internal storage too?
Since fresh installs via recovery couldn't resolve the problem..
Click to expand...
Click to collapse
Flash stock Cos13 through fastboot,it will wipe your internal storage so take a backup.
Refer to guide "Bring your device back to stock Cos by Eddy".
Mr.Ak said:
Flash stock Cos13 through fastboot,it will wipe your internal storage so take a backup.
Refer to guide "Bring your device back to stock Cos by Eddy".
Click to expand...
Click to collapse
Thanks man... Gonna give it a try...
iamvashisht said:
Thanks man... Gonna give it a try...
Click to expand...
Click to collapse
I did a clean install via fastboot, that unfortunately didn't resolve the problem.
iamvashisht said:
I did a clean install via fastboot, that unfortunately didn't resolve the problem.
Click to expand...
Click to collapse
Do you have 'unknown' baseband?? I was stuck on 3g due to that..
Issue Resolved
I dont know what happened, I had flashed stock cm13.1 via fastboot.
I checked and that didnt resolve the problem, so I had accepted the way things were and started using my 3g.
All of a sudden the 4g signal came this morning and now I can use LTE well.
I dont know how long it will stay but seems like phone decided to bring back 4g.
iamvashisht said:
I dont know what happened, I had flashed stock cm13.1 via fastboot.
I checked and that didnt resolve the problem, so I had accepted the way things were and started using my 3g.
All of a sudden the 4g signal came this morning and now I can use LTE well.
I dont know how long it will stay but seems like phone decided to bring back 4g.
Click to expand...
Click to collapse
Bro, I am facing the exact same issue man. My LTE still doesn't work. I tried installing various modems. Still no use. I hope it does soon. :/
---------- Post added at 04:58 PM ---------- Previous post was at 04:56 PM ----------
Im facing the excat same issue. Did everything and nothing worked. Somebody please help. :/
Bro try flashing stock cm13 via fastboot... That will wipe your internal storage but eventually bring back 4G
I am also facing network drop issue for last few weeks.at first i thought it may be rom's problem,because generally i try a new rom in every 2/3 weeks,but now i notice that ,i am facing the issue in all roms,i read all the comments in this threads and see that cm13.1 can solve my issue.but can i solve my issue within any nougat rom?
I too am having the issue. Occasionally my 3/4g data just cuts out but it is still enabled in settings. It seems to be when I come off of WiFi most of the time. I'm on CM13.1 by jgcaap.
I'm going to flash back to full stock and then reinstall TWRP, then the ROM. I have a few issues and I figured it was time for a fresh flash.
Sent from my A0001 using XDA-Developers Legacy app
iamvashisht said:
Bro try flashing stock cm13 via fastboot... That will wipe your internal storage but eventually bring back 4G
Click to expand...
Click to collapse
Are you talking about CyanogenMod 13?
I clean installed COS 13.1.2 via fast boot. It even removed TWRP and brought back Cyanogen recovery. The problem didn't resolve.
Can I install CyanogenMod 13 via fastboot now? or should I unlock bootloader, install TWRP and then install CyanogenMod 13 via fastboot? Please help. I'm a beginner.
In my opinion you should unlock bootloader and then reinstall via fastboot...
iamvashisht said:
In my opinion you should unlock bootloader and then reinstall via fastboot...
Click to expand...
Click to collapse
I'm right now on COS 13.1.2.
Lets say I install CM 13 via fastboot and my LTE works. Can I again revert back to COS 13.1.2 using fastboot without affecting LTE again?
Thanks for the help. I will try that this Sunday and Will tell you if it works.
Andy928 said:
I'm right now on COS 13.1.2.
Lets say I install CM 13 via fastboot and my LTE works. Can I again revert back to COS 13.1.2 using fastboot without affecting LTE again?
Thanks for the help. I will try that this Sunday and Will tell you if it works.
Click to expand...
Click to collapse
The latest official build is 13.1.2.
You can flash that via fastboot
iamvashisht said:
The latest official build is 13.1.2.
You can flash that via fastboot
Click to expand...
Click to collapse
Hi Brother. Thank you so much for your help.
My LTE is working now. I unlocked bootloader using fastboot. I installed CM 13 tugapower ROM using TWRP provided by Tugapower. Its all back to normal. I'm so glad. i'm not going to change a damn thing now. ha ha.
Lot of tries and finally its working. Can Push this baby for another year now.
---------- Post added at 07:02 AM ---------- Previous post was at 06:59 AM ----------
donk165 said:
I too am having the issue. Occasionally my 3/4g data just cuts out but it is still enabled in settings. It seems to be when I come off of WiFi most of the time. I'm on CM13.1 by jgcaap.
I'm going to flash back to full stock and then reinstall TWRP, then the ROM. I have a few issues and I figured it was time for a fresh flash.
Sent from my A0001 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Try Installing Tugapower TWRP and his CM13 ROM. My LTE is working and everything's back to normal!
Congrats man..happy for you...
And yeah we can push this phone for another year...
?

Oreo Recovery Mode Error Messages

I have received the Oreo update on my S8+ and while everything appears to work fine I do get some error messages (shown on the bottom of the picture) when I boot into recovery mode. I'm wondering if everyone else is also getting these or not?
Joshuwahhh said:
Got the same issue, got a fix?
Click to expand...
Click to collapse
It's stuff from being tired at one point in time. If the device boots and works I wouldn't worry about it. Mine had most of those errors when I had my s8. Never caused any trouble
Joshuwahhh said:
Mine is constantly crashing sooo
Click to expand...
Click to collapse
I meant rooted not tried. Have you flashed your latest firmware? Extracted pit from csc and flashed that. And or with the combo file?

Laggy video and audio after clean stock flash

Hei,
I have strange problem.
After clean flash stock rom sometimes I have laggy video and audio. Etc YouTube or some other sources.
Device ringtone and notification working fine.
Already did reflash, cleaned everything but no fix.
No custom stuff installed, fresh boot.
What can cause that?
9.0.2-9.0.2 and every OB versions tried.
It happen sometimes, not always.
Tried fastboot flash, tried recovery flash, tried flash A and B partitions.
I have the same issue
I was on stable 9.03 decided to try new ob10
I've used the fastboot version everything went fine
and now i have choppy videos and no sound even if i flash back stable..
I'm not sure what causing the issue at all.ehat you could try to do is use msm download tool to restore everything and see if it might help. Fastboot ROMs should have done the trick but it seems something is still there.. so I'd go for msm and hope for the best
@whizeguy i will try the msm
But for real that's freaking strange i was sure im the only one :/
Monratis said:
@whizeguy i will try the msm
But for real that's freaking strange i was sure im the only one :/
Click to expand...
Click to collapse
I will try one more time fastboot rom both slot and then will go to restore tool......but if you succeed fix this problem, tell me too.
I can guarantee that it will appear sometimes. Last time I did recovery flash ob10 and problem was gone.
Today I wanted to try havoc and again few houers reflashing with no fix...
taaviu said:
I will try one more time fastboot rom both slot and then will go to restore tool......but if you succeed fix this problem, tell me too.
I can guarantee that it will appear sometimes. Last time I did recovery flash ob10 and problem was gone.
Today I wanted to try havoc and again few houers reflashing with no fix...
Click to expand...
Click to collapse
I've fixed it by flashing fastboot "OnePlus6Oxygen_22_OTA_027_all_1810260000_d46787d2c9" via twrp that i did boot using fastboot boot ...
i've formated whatever i could in twrp flash the room go into oneplus recovery wipe everything that is possilble and that's all
Odd issue indeed never had it.
whizeguy said:
Odd issue indeed never had it.
Click to expand...
Click to collapse
Yea but its still an issue i've tried b10 with everything cleaned out and still had lags only 9.02 works 9.03 lags too
Monratis said:
Yea but its still an issue i've tried b10 with everything cleaned out and still had lags only 9.02 works 9.03 lags too
Click to expand...
Click to collapse
Yeah ofc. I'm just curious how it got there in the first place. What actually triggered it.
Had 9.0.2, ob1 to 10 (all betas) and never had it . With a clean flash it really should work :s so yeah odd indeed. Anyhow I hope you never faces this again
It looks like b10 has some new frimware and it just dosen't work good with 9.03 ? idk rly we need someone with bigger head than us to figure this out
i also had that problem.. i flashed miui port and after that i got that problem.thn i went back to stock pie and problem was there too.. than i solved this problem by flashing oreo using hydrogen os automatic procedure..and its solved now
I also have this problem after unbrick my OP6 with fastboot rom. What is hydrogen os automatic procedure? Please help me.
majidshahab091 said:
i also had that problem.. i flashed miui port and after that i got that problem.thn i went back to stock pie and problem was there too.. than i solved this problem by flashing oreo using hydrogen os automatic procedure..and its solved now
Click to expand...
Click to collapse
Could you give us more info what you did?
Monratis said:
Could you give us more info what you did?
Click to expand...
Click to collapse
Like I said before msm download tool (look in guide section) should also do the trick.
majidshahab091 said:
i also had that problem.. i flashed miui port and after that i got that problem.thn i went back to stock pie and problem was there too.. than i solved this problem by flashing oreo using hydrogen os automatic procedure..and its solved now
Click to expand...
Click to collapse
whizeguy said:
Like I said before msm download tool (look in guide section) should also do the trick.
Click to expand...
Click to collapse
@whizeguy i did that twice it didin't work that's why im asking the @majidshahab091
i don't know if that's something with b10
but i did flash os twice using msm download tool
then went to the b10 to check and issue was still there and again everything fine on 9.0.2 can't understand that
wtf, i have the same problem. What i must do it?
Flash Android 10 Stable using fastboot, boot to system and then flash downgrade package from OnePlus site (OnePlus forum, Open Beta thread), for me it fixes this problem.

Help: Stuck on “Phone is starting”

Can anyone help me guys? I’m on OB14 then Installed New 10.3.3 Stable using TWRP, everything went well during installation but after rebooting, my phone is stuck in “Phone is starting”. I can still access TWRP without any issues and tried reinstalling 10.3.3 Stable but the same problem after rebooting, still stuck in “Phone is starting”. What could be the issue here? Any help is much appreciated.Thank you!
Try to flash rom on both slots A/B it may help.
Illuminatus_ said:
Try to flash rom on both slots A/B it may help.
Click to expand...
Click to collapse
I will try that Buddy. Thank you so much for the suggestion.
edong23 said:
Can anyone help me guys? I’m on OB14 then Installed New 10.3.3 Stable using TWRP, everything went well during installation but after rebooting, my phone is stuck in “Phone is starting”. I can still access TWRP without any issues and tried reinstalling 10.3.3 Stable but the same problem after rebooting, still stuck in “Phone is starting”. What could be the issue here? Any help is much appreciated.Thank you!
Click to expand...
Click to collapse
I had trouble booting after updating as well. It would just stay on the boot animation forever. I had to clear dalvik and then it boot. Maybe give that a try?
Thank you for suggestions guys, finally solved my problem. Phone is working now. This thread fixed my problem,
https://forum.xda-developers.com/one...lus-7-t3937478
Credits to the Dev

Question Weird Brick after OOS 12 Update

After updating my phone to OOS 12 my screen became totally unresponsive. I tried to revert back to a older version by flashing TWRP but after booting into it the phone goes straight to CrashDump Mode. I tried using T-Mobile and Global MSM but they both give a "Unsupported Target IN" error or "Param Preload"
Nothing is working to revive this device, it turns on just fine but again no touchscreen , any help is greatly welcomed
DeathCite said:
After updating my phone to OOS 12 my screen became totally unresponsive. I tried to revert back to a older version by flashing TWRP but after booting into it the phone goes straight to CrashDump Mode. I tried using T-Mobile and Global MSM but they both give a "Unsupported Target IN" error or "Param Preload"
Nothing is working to revive this device, it turns on just fine but again no touchscreen , any help is greatly welcomed
Click to expand...
Click to collapse
If you only took one A12 update you still have A11 opposite slot. Boot fastboot "fastboot --set-active=other" wipe date and boot into A11. And don't update again.
mattie_49 said:
If you only took one A12 update you still have A11 opposite slot. Boot fastboot "fastboot --set-active=other" wipe date and boot into A11. And don't update again.
Click to expand...
Click to collapse
Oh yeah I forgot I could do that thanks !
DeathCite said:
Oh yeah I forgot I could do that thanks !
Click to expand...
Click to collapse
As long as you only took C36 this will work. Just returns you where you came from. If you updated to C39 C40 you have A12 on both slots. Won't work
mattie_49 said:
As long as you only took C36 this will work. Just returns you where you came from. If you updated to C39 C40 you have A12 on both slots. Won't work
Click to expand...
Click to collapse
Got it working again, but what causes OOS 12 not to work ?
DeathCite said:
Got it working again, but what causes OOS 12 not to work ?
Click to expand...
Click to collapse
I've read a lot about devices reacting like this. Mainly pros. OnePlus rushed the build . It's awful in all ways. Wrecking devices. Glad you got it working. Take full backup through twrp to have one.
I used msm tool oneplus 9 pro indian version for my 9 it works but should use oxygen updater to change model
DeathCite said:
Got it working again, but what causes OOS 12 not to work ?
Click to expand...
Click to collapse
DeathCite said:
After updating my phone to OOS 12 my screen became totally unresponsive. I tried to revert back to a older version by flashing TWRP but after booting into it the phone goes straight to CrashDump Mode. I tried using T-Mobile and Global MSM but they both give a "Unsupported Target IN" error or "Param Preload"
Nothing is working to revive this device, it turns on just fine but again no touchscreen , any help is greatly welcomed
Click to expand...
Click to collapse
Only way I was able to avoid this is MSM back to stock completely. Then update all the way to Android 12 from within the System Update settings. Then I unlocked my bootloader again, for some reason having an unlocked bootloader caused the unresponsive screen issue for me everytime.
Also I was able to get the Global MSM to work but had to uncheck the "SHA256 check" and the "Auto Reboot" options and also select "O2" as the target from the dropdown and its been working ever since.
jshinn1 said:
Only way I was able to avoid this is MSM back to stock completely. Then update all the way to Android 12 from within the System Update settings. Then I unlocked my bootloader again, for some reason having an unlocked bootloader caused the unresponsive screen issue for me everytime.
Also I was able to get the Global MSM to work but had to uncheck the "SHA256 check" and the "Auto Reboot" options and also select "O2" as the target from the dropdown and its been working ever since.
Click to expand...
Click to collapse
Is OOS 12 even worth it for the trouble ?
DeathCite said:
Is OOS 12 even worth it for the trouble ?
Click to expand...
Click to collapse
Gotta try it out to know for sure. Some people say it's much better on battery, and others are saying it still has bugs. I just started using it and so far no issues.
DeathCite said:
Is OOS 12 even worth it for the trouble ?
Click to expand...
Click to collapse
They fixed most issues in the debug builds. Yes I see it being a decent os
TikiThePug said:
Gotta try it out to know for sure. Some people say it's much better on battery, and others are saying it still has bugs. I just started using it and so far no issues.
Click to expand...
Click to collapse
It's actually nice after 39-40 updates/bug fixes.
OK fortunately for you I have already gone through this issue and solved it after a ****load of trying different things.
The issue is that when your flashing you've switched from the slot you were on to the other available slot on your device. If you were on slot_A for the time you've had your phone rooted until now, make sure before you flash that you set your phone back to slot A. I suggest you set it to slot A and if the problem persists without change switch to slot B. I guarantee 100% this will fix the issue.
Commands to cure issue:
fastboot set_active a
Reboot. Voila. If issue persists then:
fastboot set_active b then restart.
Positive vibes brother
71NnX said:
OK fortunately for you I have already gone through this issue and solved it after a ****load of trying different things.
The issue is that when your flashing you've switched from the slot you were on to the other available slot on your device. If you were on slot_A for the time you've had your phone rooted until now, make sure before you flash that you set your phone back to slot A. I suggest you set it to slot A and if the problem persists without change switch to slot B. I guarantee 100% this will fix the issue.
Commands to cure issue:
fastboot set_active a
Reboot. Voila. If issue persists then:
fastboot set_active b then restart.
Positive vibes brother
Click to expand...
Click to collapse
Great response but it's actually fastboot --set-active =other

Categories

Resources