Hi to everyone!
I have a problem to share because I hope anyone can help me to fix it.
My OnePlus 2 with the stock ROM of OxygenOS 3.1.0 (never unlocked bootloader or installed custom roms... always with the original system) has a problem: since 2 weeks he started rebooting randomly... it may happen from 1 up to 3 times a day (in my situation). These reboots are not caused by apps I think because a lot of them happens when the phone is with screen looked and it is in my poket or on the table (on charge and withoutcharge also, is indifferent). Sometimes happened also while using it (it could be a browsing session, a photo.... it's random!).
I also noticed that before the restart the phone freezes, expecially when its screen is turned off, you can't turn it on and all gestures or phisical key (also the fingerprint) doesn't work.
I noticed the first time that the phone rebooted exactly for the fingerprint sensor, because I tryed to unlock it and it said that after reboot I need to first insert the unlock sequence.
I tried (in this oreder):
- to make a cache and data wipe from recovery (with no result);
- to make an hard reset from the recory installed into the phone (with no result);
- to make another FULL wipe and reinstall the OxygenOS from the zip installer on the official download section of the oneplus website (with no result).
Now, I beg to all of you to help me if you have any suggestion or know a fix for this problem.
Thanks in advance to all people that will help me
Hi...
U will need to upgrade to the latest oxygen os 3.5.6/3.5.6 or flash a custom ROM like cm.
In order to do that u will need to unlock bootloader and install twrp and then flash zip.
Ensure u take a nandroid backup in twrp before flashing roms
Everything can be found on google. [emoji4]
Hope it solve the problem
Sent from my ONE A2005 using Tapatalk
But the phone worked well for months... why now there is this problem? And anyway there is no update by OTA and I don't want to unlock the bootloader for an update that I have to recive by official way...
claudio.94 said:
But the phone worked well for months... why now there is this problem? And anyway there is no update by OTA and I don't want to unlock the bootloader for an update that I have to recive by official way...
Click to expand...
Click to collapse
It's probably caused by a google app running in the background.
If u can get a logcat of the the device before reboot without root would have an idea.
Sent from my ONE A2005 using Tapatalk
How can I take a logcat? and anyway I don't know when the phone will reboot... and when I discover it is too late because like I said it freezes for 10-15 seconds and I can't make anything...
Well if u are looking for ota, check out this: https://forum.xda-developers.com/oneplus-2/general/hot-fix-3-5-6-oneplus-2-official-update-t3528911
since u don't want to unlock bootloader n stuff.
Sent from my ONE A2005 using Tapatalk
Oh thanks... but why I didn't recived it by OTA?
Well idk but I think it is released in some country or not quite official yet.
Tbh I'm using custom Roms so I never checked it.
As they say, it fixed random boots and use a VPN and select Germany or Canada to download the zip via ota or can manually flash in stock recovery.
I recommend the ota it's more safe.[emoji2]
Sent from my ONE A2005 using Tapatalk
Ok... I will try it
Related
I've been struggling with this for about a week and I am not able to figure this one out. I hope someone here can give me a hand.
I've unlocked my phone using HTCDEV and rooted using TWRP 2.4.3 gaining root and recovery access. All seemed to work well but every GOOGLE app crashes now on start up. I can't go to the market as it crashes "Unfortunately Google play store has stopped". It does this with all Gapps.
I've flashed the GAPPS through recovery since I can't access Play.Google. and it made no difference. I can't log in to Google accounts as soon as try it gives me "google account manager has stopped".
I've tried to RUU back to rom 3.16. but RUU fails to update the phone although the restoral screen shows the scrolling dots indicating it is updating, but it goes on forever. the bootloader shows "TAMPERED" "Unlocked" and this came after using FASTBOOT OEM LOCK command in an attempt to reflash the unit. I have tried to flash to other roms like CM10 but it only gets to the point of the spinning logo and just sits there and spins, etc. Other roms get stuck as well in the first boot up logo of the rom or give a black screen. I can use TWRP to restore the backup each time so the phone works seemingly ok except for anything with Gapps.
I assumed I can't not flash JB roms without S-off and I tried to use Dirty Racun to obtain S-off but I get errors with each step so gave up on that for now. I've resolved myself to sticking with the stock rooted rom but I can't do much without Google Voice which is my text and phone account.
Can anyone shed some light on this for me? I've searched the forums here and elsewhere for dozens of hours and have not been able to find a solution for this or any help that might help me "stumble" into a solution. I don't mind flashing another rom if I could get one to take hold just so I can get this unit working.
I think the TWRP recovery or a old verion of Superuser might have caused this glitch. I did the rooting and recovery using this guide here htcevohacks.com/htc-evo-4g-lte-root/how-to-root-htc-evo-4g-lte-unlock-bootloadertwrp-recovery and the provided TWRP would not accept any input so I replaced it with 2.4.3.0 and recovery then recovery seemed to work and backup/restore but still can't flash any roms successfully. I didn't notice Superuser v0.87 here as being old (my goof) and didn't get a more recent version until after the flashing was done. LIke I said, where I'm left at now is everything seems to work but anything having to do with Gapps just crashes on start.
Any help please?
Couple things you could do if you wanted a new rom. First go to the q&a section there is a sticky titled don't panic it will let you know to fast boot the bootimg for being son or find a rom that has son kernel installer for sense mean bean does
Sent from my EVO using Tapatalk 2
I had this issue today when I flashed viper 4g ROM before doing my s off. I tried every approach and what I ended up doing is a factory reset, cache wipe, D. cache wipe, Android secure wipe, sd ext. wipe (I always do the wipe 3x in a row on each) then I reinstalled my viper rom (comes with the latest google apps) and off I go. Solved all my google sign in related issues. You could also try to locate a downloadable version of goomanager which will automatically check for the latest version of gapps that is compatible with your rom and download it. Doesn't need to have a google playstore link to work either.
Sent from my EVO using xda premium
thicklizard said:
Couple things you could do if you wanted a new rom. First go to the q&a section there is a sticky titled don't panic it will let you know to fast boot the bootimg for being son or find a rom that has son kernel installer for sense mean bean does
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Thicklizard, Thanks, I'll check this out now. Are you saying the rom Mean Bean is a ROM and might take hold flashing it with my s-on situation? Is MeanBean an xda developers rom? I've always had good luck with just about everything from XDA, so would love to try it. My hope is a new rom would solve whatever "hell" my phone is stuck in. Thanks! I'll see if I can find it.
dominicsdad said:
I had this issue today when I flashed viper 4g ROM before doing my s off. I tried every approach and what I ended up doing is a factory reset, cache wipe, D. cache wipe, Android secure wipe, sd ext. wipe (I always do the wipe 3x in a row on each) then I reinstalled my viper rom (comes with the latest google apps) and off I go. Solved all my google sign in related issues. You could also try to locate a downloadable version of goomanager which will automatically check for the latest version of gapps that is compatible with your rom and download it. Doesn't need to have a google playstore link to work either.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
dominicsdad, I'm going to check out what was suggested about Mean Bean but I did try several JP type GB apps, etc. None of them would restore the function. THis has been so frustrating. I'm a guy that can folllow the posts and the guides I read, etc., but not having the core understanding or depth shows it's ugly face for a non-connected guy like me. WHy did you do an SD wipe? That's where I keep my backups which have been the only thing that has let me get back from a few botched rom attempts. I will try the goo manager if I can find a flashable version since I'm locked out otherwise with any kind of app install. I was surprised to see the EVO LTE didn't have a file manager as I was going to try and just install google voice which would at least allow me to use the phone.
THanks!
billaggie said:
Thicklizard, Thanks, I'll check this out now. Are you saying the rom Mean Bean is a ROM and might take hold flashing it with my s-on situation? Is MeanBean an xda developers rom? I've always had good luck with just about everything from XDA, so would love to try it. My hope is a new rom would solve whatever "hell" my phone is stuck in. Thanks! I'll see if I can find it.
Click to expand...
Click to collapse
Thicklizard,
Update, I installed Mean Bean and solved my problem. It gave me a scare thinking it would backfire with the 2 duplicate rom installs it requires but I had to put some faith in something working and it worked. Thank you for getting me on the right track!!!!!! Bill
Before continuing reading, please keep in mind that the problem I am asking support for was already solved for my own. What I want to know is how did it happen. For prevention, you know.
It all started when I flashed the Black Box ROM 2.0.2 (http://forum.xda-developers.com/showthread.php?t=1834915) It flashed normally, without any problem. But, since it lacked the Xposed Framework, I installed it manually, downloading from its thread, and choosing a full install. Using the Framework I downloaded Gravity Box and the Youtube Adaway, before downloading Youtube. Since the modules needed a reboot to work, I rebooted. And this is when the bad things started to happen.
The ROM did not start. It went through the BlackBox logo, but when it appeared that the SIM unlock was going to pop up, then the phone turned off. This happened many times. So I decided to do a full wipe and install another ROM. The problem was that the phone didn´t allowed me to access the recovery.
I was using the PhilZ Touch 6, but when I pressed Volume up+Menu+Power it did not work. The only thing that worked was the Odin Menu, and I got stuck at it, I couldn´t get out the Odin Menu. So, seeing that the phone wasnt going to work anyways, I flashed a 4.3 stock ROM through Odin.
As I suspected, the ROM got stuck at boot, and got a bootloop. So then I flashed another recovery, and flashed good ol´ CWM. And It worked..for a while. The phone would shut down after some seconds. So then I tried to flash TWRP, but it lasted about one second and then the phone shut down again.
Since I was using Odin 3.03, I downloaded Odin 3-04 Moded Edition, from the Modem thread, and then reflashed CWM. In this time, it worked without failing, and I could do a full wipe and flashing an old Cyanogenmod 4.2.2 ROM, finally solving the problem. The day after I flashed Ultima ROM and at the moment it goes fine, without any problem. Which is weird, because it too uses Gravity Box and Xposed Modules. I even installed new modules, rebooted the phone and it works fine, without any problem.
What I want for the people here is that someone explains to me what happened, because the BlackBox ROM looked gorgeous and I wanted to give it a long try. And because I spent an entire night solving that problem, and well, I wont sleep in peace until I get to know what happened to that bastard
r1k1v1 said:
Before continuing reading, please keep in mind that the problem I am asking support for was already solved for my own. What I want to know is how did it happen. For prevention, you know.
It all started when I flashed the Black Box ROM 2.0.2 (http://forum.xda-developers.com/showthread.php?t=1834915) It flashed normally, without any problem. But, since it lacked the Xposed Framework, I installed it manually, downloading from its thread, and choosing a full install. Using the Framework I downloaded Gravity Box and the Youtube Adaway, before downloading Youtube. Since the modules needed a reboot to work, I rebooted. And this is when the bad things started to happen.
The ROM did not start. It went through the BlackBox logo, but when it appeared that the SIM unlock was going to pop up, then the phone turned off. This happened many times. So I decided to do a full wipe and install another ROM. The problem was that the phone didn´t allowed me to access the recovery.
I was using the PhilZ Touch 6, but when I pressed Volume up+Menu+Power it did not work. The only thing that worked was the Odin Menu, and I got stuck at it, I couldn´t get out the Odin Menu. So, seeing that the phone wasnt going to work anyways, I flashed a 4.3 stock ROM through Odin.
As I suspected, the ROM got stuck at boot, and got a bootloop. So then I flashed another recovery, and flashed good ol´ CWM. And It worked..for a while. The phone would shut down after some seconds. So then I tried to flash TWRP, but it lasted about one second and then the phone shut down again.
Since I was using Odin 3.03, I downloaded Odin 3-04 Moded Edition, from the Modem thread, and then reflashed CWM. In this time, it worked without failing, and I could do a full wipe and flashing an old Cyanogenmod 4.2.2 ROM, finally solving the problem. The day after I flashed Ultima ROM and at the moment it goes fine, without any problem. Which is weird, because it too uses Gravity Box and Xposed Modules. I even installed new modules, rebooted the phone and it works fine, without any problem.
What I want for the people here is that someone explains to me what happened, because the BlackBox ROM looked gorgeous and I wanted to give it a long try. And because I spent an entire night solving that problem, and well, I wont sleep in peace until I get to know what happened to that bastard
Click to expand...
Click to collapse
OK first black box already has xposed in ROM control settings.. so maybe because you manually installed it it may have caused conflicts... Don't know why you got a recovery bootloop... but maybe due to same problems... And I am also using blackbox 2.1 and so far it is fantastic...
Sent from my GT-I9300 using xda app-developers app
Partition structure on these phones is very fragile, one bad shutdown can corrupt one or more partitions at the same time. I'd suggest the combination of mods applied caused the kernel panic, while data was being written.
Subsequent events read like normal solution to corruption, it shouldn't happen again but best to apply framework mods one at a time.
Sent from my GT-I9300 using Tapatalk
kunal1540 said:
OK first black box already has xposed in ROM control settings.. so maybe because you manually installed it it may have caused conflicts... Don't know why you got a recovery bootloop... but maybe due to same problems... And I am also using blackbox 2.1 and so far it is fantastic...
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Hmm, I don´t remember that the BlackBox 2.0.2 had any Framework...thats why I did a manual installation. But I will try the new version 2.1. Hopefully the problems may have been solved.
boomboomer said:
Partition structure on these phones is very fragile, one bad shutdown can corrupt one or more partitions at the same time. I'd suggest the combination of mods applied caused the kernel panic, while data was being written.
Subsequent events read like normal solution to corruption, it shouldn't happen again but best to apply framework mods one at a time.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Interesting. So I have to apply mods one by one? Or can I add multiple mods because corruption has already been solved?
On a side note, when I boot the phone the red exclamation mark that used to appear has disappeared. Does that means that I somewhat reseted the flash counter to 0?
Hi guys > i flashed uptil now more than 6 ROMs .. everything is fine but wifi always does not work .. it even do not start
multiple press on its icon causes the device to restart
im using htc desire 816 Dual sim
i will be grateful to recieve any help
I'm assuming you have no working backups? If not... Big mistake. You should always backup before installing a new Rom.
I suggest you download an RUU and go back to unrooted, locked boot loader, completely factory stock and see if WiFi works. If not your issue may very well be hardware related.
Sent from my 710C using Tapatalk
this happened to me a few times when I restored lollipop backup from TWRP, I flased kitkat back up and then installed ota update again
Hello.
I was able to fix the random reboots i had with flashing prerooted zip via TWRP, this apply also on the new 26.1.A.3.111, only tested on E2306.
1. Must backup your data. You are gonna wipe it
2. Use flashtool and downgrade to a rootkitXperia rootable firmware. I used 26.1.A.1.112 but other rootable should be the same. (wipe data may not be necesary in this step but i did it just in case)
3. When flashing done, root the device with rootkit, and install TWRP
4. Use xperifirm to download the 3.111 FW then create the prerooted with its system.ext4 and kernel.elf
5. Flash the zip via TWRP, wipe dalvik, then start the phone and check that you have superuser, and go about phone to make sure everything went well and your in 3.111 with its kernel also.
6. Use flashtool again to flash 26.1.A.3.111 but you this time you must EXCLUDE SYSTEM and KERNEL to keep the root, in other words your gonna flash everything but kernel and system so be sure you ticked them, also should wipe data so you can start fresh and avoid possible incompatible things.
7. Let the phone starts, mine took around 10 - 15 min. You should now be in 26.1.A.3.111 with root and no random reboots. So far im using it since 12 days and no reboots nor system hangs, ive updated all apps via playstore, and even downloaded several 500Mb+ games and its working really fine
Click to expand...
Click to collapse
Sorry for this guide that isnt noob friendly, im doing it quite hurry because im too busy with work but i wanted to share what worked for me with everyone. If this works for you too and someone wants to do a better noob friendly guide with links and such go ahead it is ok.
[NOTE]Random reboots seems to happen when there are diferent modem versions. Special thanks to @sergioslk who discovered this.
Of course, all credits to the respective developers who worked really hard on this tools for us. Thanks devs.
Hey, thanks. I had 26.1.A.2.167 rooted, so I just installed 3.111 with data wipe through prerooted zip on top of 2.167, and then reflashed everything except for kernel and system (also data wipe here) like you wrote in your post. So far so good - almost 30h without reboot, which is far better than before.
Hm, didn't work for me also with 3.111 I reflashed (using stock 3.111 from xperifirm) excluded kern and system but it is still randomly rebooting when installing gapps.
fpghost84 said:
Hm, didn't work for me also with 3.111 I reflashed (using stock 3.111 from xperifirm) excluded kern and system but it is still randomly rebooting when installing gapps.
Click to expand...
Click to collapse
Did you first flashed via TWRP the prerooted zip you created with system.ext4 and kernel.elf extracted from 3.111 FW? did you wiped data after completing flash? which version of FW you had just before flash 3.111?
Yeah, I did as you say. My phone orig had 2.167, but it upgraded itself recently to 3.111, then I downgraded to 1.128 to root, before using the prerooted TWRP zip (with system.ext4 and kernel.elf extracted from 3.111 ftf) to upgrade back to 3.111.
EDIT: I think something went wrong when I created the ftf bundle from the files downloaded from xperifirm. I repeated the whole process and now I'm not seeing the random reboots (at least for an hour with quite a few apps installed and updated) ....So yeah in summary many thanks for this ...It would be nice if it was mentioned on the main how to thread.
thewailer said:
Hello.
I was able to fix the random reboots i had with flashing prerooted zip via TWRP, this apply also on the new 26.1.A.3.111, only tested on E2306.
Click to expand...
Click to collapse
Thanks so much for posting this. I had thought of doing this myself but quickly ruled it out because I thought it was a dumb idea (no offense) and wouldn't work, but after hearing of your success I thought I'd give it a try anyways and I've been powering through a ton of app installs/updates and haven't had a single reboot so far. It sounds to me like this is the key.
I'll post an edit after a few days to let you guys know how it holds to my personal test of time.
Thanks again!
Update:
Well, it's been nearly a week now and I've yet to experience a random reboot. This is definitely the fix we've all been waiting for! I hope this knowledge can be spread to all who have been plagued with this issue!
the random reboots are related to different modem versions, that is why phone reboot when using a hi-speed wifi connection, i said this previously but no one matters :'(
sergioslk said:
the random reboots are related to different modem versions, that is why phone reboot when using a hi-speed wifi connection, i said this previously but no one matters :'(
Click to expand...
Click to collapse
Hey @sergioslk,
Thanks so much for your contribution. I found your post about this problem but it was kind of hard to read whereas the original poster here went into a bit more detail. Sometimes that's all people need, is a little more information. I'm sure you've made other contributions to the community that have been extremely valuable.
To reitterate, this is definitely the fix to the problem we've all been facing when it comes to using the pre-rooted zip to get root on the latest version. I had suspected this to be the problem awhile ago but couldn't really figure out how to fix it.
Thanks everyone for all your hard work!
sergioslk said:
the random reboots are related to different modem versions, that is why phone reboot when using a hi-speed wifi connection, i said this previously but no one matters :'(
Click to expand...
Click to collapse
Oh dude many thanks for this contribution, i havent readed your post before, but now i can say theres a know reason why the random reboots occurs. Im not an expert in android, i just tried this as a last hope, ive tried everithing, no google account, no wifi, no moibile data, no sdcard, deleting all bloatware, untouching bloatware, a lot of wipes..... and this last one for some reason worked but i wasnt sure why untill now. Thanks again!
Hi guys
I have problem with my touchscreen when the antenna switch between 2G 3G 4G when someone call me or I receive sms, specially when data connection is active...
for example when my sim card is on 4G and someone calling, the antenna switch to 3G or 2G witch is normal BUT the phone touch itself and may be reject the call automatically...
I flashed my phone to 7.0 and 7.1.1 more than 3 times but it didn't fixed...
Does anybody have this problem??
Is it a bug from android 7 ???
should I flash to 6.1.1 ????
plsss help!!!:crying:
please give details
1. how are you flashing? seems like your boot is unlocked
2. if yes, then wipe everything and start fresh (userdata, master reset, all options)
3. if you have already done that then try different region's stockrom (xperifirm) and flash that one. (we have now two 7.1.1 rom released)
YasuHamed said:
please give details
1. how are you flashing? seems like your boot is unlocked
2. if yes, then wipe everything and start fresh (userdata, master reset, all options)
3. if you have already done that then try different region's stockrom (xperifirm) and flash that one. (we have now two 7.1.1 rom released)
Click to expand...
Click to collapse
1. with flashtools latest version... I flashed the Official rom, so does it matter the boot is locked or not?
2. I wiped everything such as user data, logs, qnovo, ...
3. now im gonna flash android 6, I'll try and then answer you what happen
mahdi0214 said:
1. with flashtools latest version... I flashed the Official rom, so does it matter the boot is locked or not?
2. I wiped everything such as user data, logs, qnovo, ...
3. now im gonna flash android 6, I'll try and then answer you what happen
Click to expand...
Click to collapse
the reason i asked about boot unlocked status is to make sure no foul play was done with device! for example with unlocked bootloader thirparty roms can be flashed LINEAGE , X roms and if they ever had, chance may be that touch/wiz has been compromised.
if you had dropped your phone touch goes crazy.
so it was a question just to answer many doubts automatically.
if its not hardware problem then android 6 would work just fine