Related
I have just recently tried to install the official cm11 images for my g3. They worked fine. Then, when I installed gel x-posed settings and activated it, I would get said error. It would pop up again and again. This would lead me to reflash my ROM. Then, I do not know what happened, when I would flash a ROM, I would get the error from the start. I eventually fixed this error. But then, when I tried to upgrade the nightly, I got the error again. So I flashed the ROM again, and let it sit. After a little while of perfection, the error came back up!
Here's what I have tried:
-reflashing the boot.IMG (unzipped)
-clearing cache (recovery)
-clearing Sim tool cache/data (said they were non existent when trying)
-reflashing stock, then reflashing cm11
I really want cm11 on my g3, but with these issues, I don't know whether I can now.
Any help would be appreciated!
Sent from my Nexus 7 using XDA Free mobile app
CM Nightlies are working perfect for me with no errors. Here is the process I went through:
I am still using TWRP 2.8.0 which is the version I installed when I originally Bumped! my phone.
I downloaded CM and Gapps to root of my internal SD storage
I chose to Wipe in TWRP
I chose Advance Wipe
I picked every option except for Internal Storage and External SD Card/Storage
I then Wiped
Out of habit, I do this 3 times (don't ask why, I just do it from when I had older android devices)
I then go back to wipe main screen and slide to do the standard wipe, 3 times
Yes, this is probably overkill!
I then go to install in TWRP
I install CM, then I install gapps (using the gapps that are on this list: https://itvends.com/gapps/
Yes, the date of those gapps are a little older, but that is what worked for me per OP'S instructions
I went through setup of my phone, fixing APN, Setting WIFI to USA, signing into Google after first loading into Rom instead of signing into Google on first bootup. Did a reboot
Installed Xposed, and the modules needed, reboot
I never received any error
I have done 3 nightly updates so far, as of 11/30. I am sure 12/1 will be ready in an hour or so.
I always click on about phone, download said update and let the process do its thing automatically, walk away and the phone is ready to use
Still no errors whatsoever. In fact, this has been the first version of AOSP I have used for the G3 with 0 errors. It is perfect, for me - No issues.
Hope that helps.
mwest316 said:
CM Nightlies are working perfect for me with no errors. Here is the process I went through:
I am still using TWRP 2.8.0 which is the version I installed when I originally Bumped! my phone.
I downloaded CM and Gapps to root of my internal SD storage
I chose to Wipe in TWRP
I chose Advance Wipe
I picked every option except for Internal Storage and External SD Card/Storage
I then Wiped
Out of habit, I do this 3 times (don't ask why, I just do it from when I had older android devices)
I then go back to wipe main screen and slide to do the standard wipe, 3 times
Yes, this is probably overkill!
I then go to install in TWRP
I install CM, then I install gapps (using the gapps that are on this list:
Yes, the date of those gapps are a little older, but that is what worked for me per OP'S instructions
I went through setup of my phone, fixing APN, Setting WIFI to USA, signing into Google after first loading into Rom instead of signing into Google on first bootup. Did a reboot
Installed Xposed, and the modules needed, reboot
I never received any error
I have done 3 nightly updates so far, as of 11/30. I am sure 12/1 will be ready in an hour or so.
I always click on about phone, download said update and let the process do its thing automatically, walk away and the phone is ready to use
Still no errors whatsoever. In fact, this has been the first version of AOSP I have used for the G3 with 0 errors. It is perfect, for me - No issues.
Hope that helps.
Click to expand...
Click to collapse
I did everything exactly as you did, including the 3 wipes, also out of habit. I too however, get the same error with the latest nightly. It starts popping up as I try to add my Gmail account at the initial setup. Previously, the 'unofficial' builds did not do this to me. This is the only rom that does this, I have tried them all out. I have yet to try to flash a different gapps package to see if that makes a difference. Apparently I dont get the data issues with cm12, but get phone issues with cm11.
I'm a bit relieved to see I'm not the only one having this problem. Been updating every night to see if maybe it's fixed, but I still get the same error. Didn't happen on the first nightly I flashed, though. It lol seems to be happening at random for me. Sometimes I'll set my phone down for a couple hours, working perfectly fine. Then I pick it up to check something and I suddenly start getting that error. I've tried every "solution" I find and none of them work for me. Even thought it was an issue with reading my sim card because when I get the error, it shows that my sim card isn't being read. But I still get it when I take it out. A normal factory reset doesn't fix it either. I have to do a complete data format to remove the error.
I found a quick little fix where i make a backup earlier in the day and just restore it whenever I start getting the error, but it's still very annoying.
Same issue
Hey bros,
Same thing here. It's a baseband radio issue. Notice in settings under About Phone it says 'Baseband Version: Unknown'. Either TWRP is flashing over our baseband (not likely, calls and texts can be made before the error message attacks come), or CM11 has some issue on certain builds with reading our SIM cards. I think having an official 10B or 11C flashable baseband radio to install at the time of the ROM install will fix this problem. Waiting on CM to patch the code will take too long. Let me know if you find one of these basebands or can find out how to extract it (from file manager or somewhere?) as I have not been able to find this info on XDA or anywhere.
EDIT: I FIXED IT
I'm a new member, and XDA won't allow me to post links..... look in the OP for JasmineROM (all credit to author for posting this 11C modem and fabulous stock LG debloated ROM) under downloads, you'll find the 11C modem. Download it.
1. Place 11C modem.zip on external or internal, whichever you want. I prefer external.
In TWRP:
2. Backup, unless youre livin' life on the edge.
3. Wipe it all except for external (or internal, if you prefer to flash from your internal storage)
4. Add to Install zip que in order:
a) latest CM11 nightly
b) 11C modem found in JasmineROM OP of main thread
c) GAPPs of your choice (I like nano PA GAPPs, and just install whatever else i want after)
5. FLASH
6. profit
7. PHAP
I have heard the 10B radio works great too. holler back and post results between the 2 stock radios for VS985.
Please hit thanks, as I am new and want to be helpful, where possible. Please share this so others know that we can overcome this nonsense.
CM11!!! Phappin' so hard right now!
Got it again.... totally blowed right now. maybe reconfig APN to match VZW and it will work?
Thanks for all the responses, it currently seems that the problem is cm11. I will probably wait for a stable build. For now, I'm using an unofficial cm12 ROM. Thanks for all the help!
Sent from my LG-VS985 using XDA Free mobile app
8pscott said:
Thanks for all the responses, it currently seems that the problem is cm11. I will probably wait for a stable build. For now, I'm using an unofficial cm12 ROM. Thanks for all the help!
Sent from my LG-VS985 using XDA Free mobile app
Click to expand...
Click to collapse
Are you using that PA GAPPs package that's in alpha? I think i'm going to give up and go to 12 too... I do know that the first official nightly of CM11 doesn't give me any errors, but Trebuchet is so buggy it won't take widgets. Had to download Nova
It makes me cry. My phone lasted through the night. Woke up at around 7 and it was fine. Went back to sleep and woke up at around 8:30 and I was crushed to see the problem happening again. There doesn't seem to actually be anything thy triggers it. :/
Yeah I think I'm gonna just try out cm12 and see how that goes.
Double check to make sure the phone isn't running in art. That fixed my problems! Xposed and art do not work together!![emoji2]
Im getting the same error on my phone usually a few says after using any of the nightlies. When i go to make a phone call it gives me the force close and doesnt stop. Ive since moved back to stock hoping someone had more info on the issue. My phone was not using Art but I did have xposed installed.
Coming from the simplicity of a Nexus 7 and a Moto G, I am a little confused by how the Z3TC handles recovery and flashing. After a two hour session last night I finally got CM12 20150217 running but not matter what I try, I can't seem to get Xposed 2.7 alpha1 to run (it works just fine on Cm12 on my Nexus so it ought to work, somehow).
In the god awful CM12 recovery, flashing xposed fails with an error message I remain unable to read. Flashing it with the twrp that someone integrated into the stock kernel succeeds according to the twrp status but then the xposed installer still does not see the app_process (it sees the bridge however, which I find weird and have not seen like this before).
So did anyone already manage to cleanly install xposed on a Z3TC? Also, is there any way to get TWRP 2.8.X with CM instead of their awful CM recovery?
In principle, I am open to going to AOSP if someone can point me to a scorpion_windy image (all I can find on FXP is scorpion for AOSP, which is another weirdness that confuses me) and feels I have better chances of getting it to work there....
Hi,
what you need to do is to install twrp recovery to the FOTA partition.
(This will also allow you update cm12 through cyanDelta, which is not possibe with the crappy cm12 recovery)
It's all decribed here: http://forum.xda-developers.com/z3-tablet-compact/development/daily-cm12-unofficial-builds-t2983400
The twrp img is actually a modified Z2 twrp, but it seems to work.
(i am writing "it seems" because i have a SGP621 myself, for this one I can say "it works").
Please note:
- It is no problem if app_process displays only ---, that is a known bug of the alpha
- not all xposed modules are working. XGELS is working for sure, if you want to test.
- You need to invoke soft reboot from within the xposed app after each flashing of the xposed zip (which you need to flash after each ROM update). Otherwise xposed will not work currently.
That seems to have resulted in a (soft?) bricked SGP611. At least now it sits at the Sony logo showing a solid yellow LED and doesn't even turn off anymore (meaning I can't even try to boot it to bootloader to flash a known working kernel anymore)
Edit: Or not, a 10 s power & vol + action followed by power on lets me boot both TWRP and CM12, very strange.
Now lets see if I can get Xprivacy to do its job (for starters, the boot.img contents are different than on the GOogle/Moto devices so we shall see)
nupi said:
That seems to have resulted in a (soft?) bricked SGP611. At least now it sits at the Sony logo showing a solid yellow LED and doesn't even turn off anymore (meaning I can't even try to boot it to bootloader to flash a known working kernel anymore)
Click to expand...
Click to collapse
wow, I'm really sorry to hear that ... I have no idea what might have gone wrong.
You can turn off the device by holding the power button for 7-10 seconds.
If ou want to remove twrp from the FOTA partition, simply reinstall (ONLY) FOTA from the current ftf (SGP621_23.0.1.A.0.167_CE.ftf) through flashtools.
Never mind, I got it back and TWRP flashed xposed cleanly but I can't get it to work - soft reboot does not help, either
However, the kernel seems to have the wrong WiFi drivers for the SGP611 (at the very least, I don't get WiFi anymore). Back to flashing the CM12 kernel for now... I am thinking I should go back to KitKat until someone with a little more clue figures this one out
nupi said:
So did anyone already manage to cleanly install xposed on a Z3TC? Also, is there any way to get TWRP 2.8.X with CM instead of their awful CM recovery?
Click to expand...
Click to collapse
Cyanogen has made the worst mistake every with CM12 and CM Recovery Testing at the same Time.
As long as Cyanogen does not develop a real Recoveryfunction to CM Recovery this crap will block much more then Xposed.
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Hello,
First, have you checked that the ROM you flashed was fully compatible with your device? Yes, this is obvious, but I have to ask.
Second, I'm not a ROM flashing via custom recovery fan... The best way to efficiently flash a ROM in my opinion is Odin-Download mode but whatever (your USB port is screwed, so pfu.)
Redownloading apps doesn't work for you? (updating the apk may fix that!)
Atronid said:
Hello,
First, have you checked that the ROM you flashed was fully compatible with your device? Yes, this is obvious, but I have to ask.
Second, I'm not a ROM flashing via custom recovery fan... The best way to efficiently flash a ROM in my opinion is Odin-Download mode but whatever (your USB port is screwed, so pfu.)
Redownloading apps doesn't work for you? (updating the apk may fix that!)
Click to expand...
Click to collapse
Thanks for your reply!
Yes, I do have used ROMs compatible with my device as they've all are made for espresso3g (which is my device).
I know it's not really the best way but I'll keep on trying with custom recovery for some more time and then perhaps try buying a new cable, and see if that works.
Tried installing Google Play Store from APK both on a clean ROM without GApps and with, but it still doesn't run and keeps on saying that either Google Play Store or "com.google.process.gapps" has stopped.
Alright...
I'm out of idea x/
lordquestionmark said:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
Hello...!
You could try the following....
1. make absolutely sure you are using the correct version of gapps for the custom rom you are currently using. If your custom rom is on android 6, you need gapps for android 6 for example.
2. after flashing gapps wipe cache/dalvik and make a factory reset BEFORE exiting twrp. You will lose personal data but since you are preparing to give the device to somebody else that should not be much of a concern.
Let me know if it helps, if it does not, I might be able to try and provide additional suggestions.
Good luck!
r&xp said:
Hello...!
You could try the following....
1. make absolutely sure you are using the correct version of gapps for the custom rom you are currently using. If your custom rom is on android 6, you need gapps for android 6 for example.
2. after flashing gapps wipe cache/dalvik and make a factory reset BEFORE exiting twrp. You will lose personal data but since you are preparing to give the device to somebody else that should not be much of a concern.
Let me know if it helps, if it does not, I might be able to try and provide additional suggestions.
Good luck!
Click to expand...
Click to collapse
Hi and thanks for your reply!
1. The ROMs I've been trying to install are all android 6.0.1 and I've been trying with different OpenGApps packages for the 6.0 version which should work (except CM 12 which is android 5.1 with which I've tried OpenGApps and A-Gapps for Android 5.1).
2. Tried that with 3 different ROMs today and the results are following: Slimrom gets stuck in setupwizard which doesn't start, CM 12 starts but the same error as first seems to appear (I get notifications about GApps which stop working) and Lineage bootloops the lineage start screen.
lordquestionmark said:
Hi and thanks for your reply!
1. The ROMs I've been trying to install are all android 6.0.1 and I've been trying with different OpenGApps packages for the 6.0 version which should work (except CM 12 which is android 5.1 with which I've tried OpenGApps and A-Gapps for Android 5.1).
2. Tried that with 3 different ROMs today and the results are following: Slimrom gets stuck in setupwizard which doesn't start, CM 12 starts but the same error as first to appear (I get notifications about GApps which stop working) and Lineage bootloops the lineage start screen.
Click to expand...
Click to collapse
Ok...
This is what I would do if it was my device and I was facing what you are describing. It might take some time and a little patience to do everything described here, but it might also work.
1. Usin Odin, flash latest available official rom for the device. Let it boot and complete setup.
2. Use odin and use CF autoroot to root. Again boot and complete setup.
3. Flash Twrp. Enter Twrp and flash latest flashable supersu.zip. At this time I believe is version 2.82. Again boot and let it reach your welcome screen.
4. Enter Twrp. Enter advanced wipe. Wipe everything except external SD and usb at least 3 times. Do not exit twrp.
5. Install you rom. Do not exit Twrp.
6. After installing your rom, Twrp will ask you if you want to wipe cache/dalvik. "Yes" but DO NOT reboot.
7. Install correct version of gapps for your custom rom (correct both android version and architecture version). Again twrp will ask you to wipe cache/dalvik. "Yes" and this time reboot.
See what happens. If it gets stuck, try entering twrp again and do a factory reset only, only once and reboot again.
If that fails again... I will at a loss here myself too...
I did a quick search here on xda on P5100, I am providing some links that you can take a look at. You probably already searched yourself but you never know...
https://forum.xda-developers.com/ga...-2-unified/rom-cyanogenmod-13-cm13-0-t3303798
https://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-blissmallow-t3312320
https://forum.xda-developers.com/showthread.php?t=1686514
https://forum.xda-developers.com/showthread.php?t=2581782
https://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-candy-5-v2-5-5-t3136904
If nothing else helps, perhaps the best way to go around this would be to find a custom rom with at least some google apps pre-installed, in order to save you the trouble you are currently facing.
lordquestionmark said:
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
did you find a solution
lordquestionmark said:
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
Hey, just try uninstalling Google play services and install them again. I faced the same issue and now it's all working on my Samsung Galaxy Core 2
HI, All
I have had Nord 2 three months now. First Nord 2 was in service 3 times. So I got new device. Now this new has been two times at service. I have rooted both with TWRP (denniz) and Magisk of course.
I was wondering if TWRP is causing all the problems or is it just that Nord 2 does not like to be rooted.
And now I am thinking not to root but root has its benefits, so I guess I'll root but which method, TWRP or not.
Have you had problems after rooting? If you have, have you used TWRP and Magisk or just Magisk, no TWRP??
It would be nice if you would share your comments.
Thank you
My experience: if sent in for service, all they do is re-flash stock rom. This is where the problems start! I've been talking with an experienced guy from "The Phone Lab" in The Netherlands, which is the contractor for OnePlus repairs in my country.
Thing is, if your phone got messed up, THINGS REMAIN IN THE MEMORY after re-flashing stock. The ONLY thing that works to get a flawless CLEAN system (once even a TWRP-folder survived, but espacially the partition for your fingerprint etc. tempts to stay currupted in a way leading to several strange behaviours).
So to get a clean system, the "repaircompany" should:
- flash stock rom
- boot into STOCK recovery
- fully wipe
- flash stock rom again
NOW your device will work as stock WITHOUT strange behaviour. Mine has been stock flashed 5 times. I know what I am talking about. Every time different errors, which stopped / got eliminated after wiping inbetween.
The problem is, if you send your device to an OnePlus contractor or OnePlus servicepoint, they will not do this, since even THEY are not aware. Because after a stock flash the phone INTENTS to work normally. Strange behaviour sometimes even starts after set-up.
It's the most frustrating phone I ever had.
exis_tenz said:
My experience: if sent in for service, all they do is re-flash stock rom. This is where the problems start! I've been talking with an experienced guy from "The Phone Lab" in The Netherlands, which is the contractor for OnePlus repairs in my country.
Thing is, if your phone got messed up, THINGS REMAIN IN THE MEMORY after re-flashing stock. The ONLY thing that works to get a flawless CLEAN system (once even a TWRP-folder survived, but espacially the partition for your fingerprint etc. tempts to stay currupted in a way leading to several strange behaviours).
So to get a clean system, the "repaircompany" should:
- flash stock rom
- boot into STOCK recovery
- fully wipe
- flash stock rom again
NOW your device will work as stock WITHOUT strange behaviour. Mine has been stock flashed 5 times. I know what I am talking about. Every time different errors, which stopped / got eliminated after wiping inbetween.
The problem is, if you send your device to an OnePlus contractor or OnePlus servicepoint, they will not do this, since even THEY are not aware. Because after a stock flash the phone INTENTS to work normally. Strange behaviour sometimes even starts after set-up.
It's the most frustrating phone I ever had.
Click to expand...
Click to collapse
Hi and thank you for reply.
That was new to me but explains a lot. But also I remined that my 1st Nord2 got new motherboard (IMEI and S/N was different) and now my new Nord2 has new motherboard. So after replacing motherboard it should be as totally new. But still with 1st device I end up problems. I have not rooted my new Nord 2 because my intention was to find out if it is TWRP which is causing problems or is it the device - hardware vs OS after root rocess regardless TWRP or not.
Basically is Nord 2 working as "normal" devices after rooting or not.
To tell you the truth, I am fed up with this phone too
Hi jis251: we can shake hands. After the 4th (!) stockrom-flash by a OnePlus-servicecenter and still having strange behaviour (for example I was not able to set a fingerprint, the device-motor just kept shaking when I tried), they "decided" that my motherboard was broken. It was switched under warrantee and after that I messed up something and then a "regular" stock-flash didn't work either. You DO need to flash stock (@servicepoint or by yourself), then REBOOT into STOCK recovery, WIPE EVERYTHING, and flash stock again (with OnePlus-tool only they have).
The problem is that OnePlus (and their servicecenters) are NOT aware of this (and probably don't care). But once rooted with strange behaviour this is a must.
For now, fingers crossed, everything seems to work. I have TWRP 3.6 (Denniz) installed, Magisk 24.1, several modules (AFWall Boot AntiLeak, BuiltIn BusyBox, F-Droid privileged Extension, Magisk Bootloop Protector -not sure if this does anything, not tested-, Shamiko, Universal SafetyNet Fix and Zygisk LSPosed.
Also in LSPosed I have 4 modules activated: AFWall+, Disable FLAG_Seure, XPrivacyLua and GravityBox [R].
This setup works and passes SafetyNet without problem. Banking Apps work. The only thing I cannot get to work (keeps detecting root) is my Cupra App (for my car - same as Volkswagen App) as posted here: Cupra
The setup on my OnePlus 7 pro (A10) and Nord 2 5G (A11) - both stock roms - is the same. Both pass banking apps but the Volkswagen/Cupra app they do not. I can live with that as long as that is the only exception. It sucks, but privacy above all ;-)
after a week no broblem with my rooted nord 2 (twrp+ magisk canary) all working as well!
exis_tenz said:
My experience: if sent in for service, all they do is re-flash stock rom. This is where the problems start! I've been talking with an experienced guy from "The Phone Lab" in The Netherlands, which is the contractor for OnePlus repairs in my country.
Thing is, if your phone got messed up, THINGS REMAIN IN THE MEMORY after re-flashing stock. The ONLY thing that works to get a flawless CLEAN system (once even a TWRP-folder survived, but espacially the partition for your fingerprint etc. tempts to stay currupted in a way leading to several strange behaviours).
So to get a clean system, the "repaircompany" should:
- flash stock rom
- boot into STOCK recovery
- fully wipe
- flash stock rom again
NOW your device will work as stock WITHOUT strange behaviour. Mine has been stock flashed 5 times. I know what I am talking about. Every time different errors, which stopped / got eliminated after wiping inbetween.
The problem is, if you send your device to an OnePlus contractor or OnePlus servicepoint, they will not do this, since even THEY are not aware. Because after a stock flash the phone INTENTS to work normally. Strange behaviour sometimes even starts after set-up.
It's the most frustrating phone I ever had.
Click to expand...
Click to collapse
No way. I had my phone serviced at the same place and now I don't get OTA updates anymore and have to install them manually. My Bluetooth is also working less reliably. I had my suspicions but thanks for confirming it.
You DO need to flash stock (@servicepoint or by yourself), then REBOOT into STOCK recovery, WIPE EVERYTHING, and flash stock again (with OnePlus-tool only they have).
Click to expand...
Click to collapse
Just to be clear: is it possible to do by myself? Or is their tool required in this step? But yeah I was really hoping flashing would be as straight forward as with my previous OnePlus phones
Kenaestic said:
No way. I had my phone serviced at the same place and now I don't get OTA updates anymore and have to install them manually. My Bluetooth is also working less reliably. I had my suspicions but thanks for confirming it.
Just to be clear: is it possible to do by myself? Or is their tool required in this step? But yeah I was really hoping flashing would be as straight forward as with my previous OnePlus phones
Click to expand...
Click to collapse
Hi Kenaestic, so you are from The Netherlands as am I? Honestly, I don't know if you can do it yourself. Maybe with the tool from (I mean Pankspoo) you can put back all the partitions etc., get to some kind of "stock-state" and be able to wipe everything in stock recovery. But I am just not sure.
I am kind of "ready" with this phone. I am on version 17 (stock A11) and once rooted I decided to not take anymore OTA's. The phone is just way too unreliable. And it IS my daily driver for work, so I can't risk it. It freaks me out that I can't "normally" flash back a stock rom, an d I am too unexpierenced for ASB, commands, etc. I'm an user, not a programmer.
I got 5 (!) reflashes from The Phone Laband a new mainboard. Once, I got suspicious when a TWRP-folder was STILL THERE after a stock-re-flash. From that moment on, and all the problems with fingerprint and PIN-locks, that something just survives that factory flash (I always managed to mess things up by rooting).
Now the damn thing works (and really I still like it). I came from the OP7pro, but this device is just so much lighter and better in the hand (not top-heavy). It's snappy, it's fast. But in the meantime I will start working on my OnePlus 7 pro to get E/OS running and finally my goal is to de-google. Once that works, the OP Nord 2 will be sold and the OP7 pro will be my back-up phone.
The Nord 2 is good and I love it, but software is a failure. Never a MediaTek-device for me again.
exis_tenz said:
Hi Kenaestic, so you are from The Netherlands as am I? Honestly, I don't know if you can do it yourself. Maybe with the tool from (I mean Pankspoo) you can put back all the partitions etc., get to some kind of "stock-state" and be able to wipe everything in stock recovery. But I am just not sure.
I am kind of "ready" with this phone. I am on version 17 (stock A11) and once rooted I decided to not take anymore OTA's. The phone is just way too unreliable. And it IS my daily driver for work, so I can't risk it. It freaks me out that I can't "normally" flash back a stock rom, an d I am too unexpierenced for ASB, commands, etc. I'm an user, not a programmer.
I got 5 (!) reflashes from The Phone Laband a new mainboard. Once, I got suspicious when a TWRP-folder was STILL THERE after a stock-re-flash. From that moment on, and all the problems with fingerprint and PIN-locks, that something just survives that factory flash (I always managed to mess things up by rooting).
Now the damn thing works (and really I still like it). I came from the OP7pro, but this device is just so much lighter and better in the hand (not top-heavy). It's snappy, it's fast. But in the meantime I will start working on my OnePlus 7 pro to get E/OS running and finally my goal is to de-google. Once that works, the OP Nord 2 will be sold and the OP7 pro will be my back-up phone.
The Nord 2 is good and I love it, but software is a failure. Never a MediaTek-device for me again.
Click to expand...
Click to collapse
Haha ja zeker So this is something I have noticed as well. I'm in the same boat as you. I'm not a programmer and I come from a device where flashing was way easier. But for some reason this phone has persistent data on it that can not be reset or wiped. Maybe it was intended as a security measure. When you flash TWRP you probably noticed you can not boot into it without a commandline on your computer. Otherwise it will completely ignore the volume down + power combination and go straight to booting the OS. So I'm guessing OnePlus made it harder to tamper with the recovery. But for rooting it's only confusing, gives me headaches but most importantly; when you accidentally remove the ADB server authentication you're screwed because there is no recovery to boot into. I'm really hoping the miracle workers in the modding community find a way to work around these things. Because I first just thought it's kinda janky because they used a few work arounds to get TWRP running as fast as possible when the phone came out. But now I just don't know anymore. Anyway, I have an appointment with ThePhoneLab tomorrow and I'll report back if it did anything. Cheers.
exis_tenz said:
My experience: if sent in for service, all they do is re-flash stock rom. This is where the problems start! I've been talking with an experienced guy from "The Phone Lab" in The Netherlands, which is the contractor for OnePlus repairs in my country.
Thing is, if your phone got messed up, THINGS REMAIN IN THE MEMORY after re-flashing stock. The ONLY thing that works to get a flawless CLEAN system (once even a TWRP-folder survived, but espacially the partition for your fingerprint etc. tempts to stay currupted in a way leading to several strange behaviours).
So to get a clean system, the "repaircompany" should:
- flash stock rom
- boot into STOCK recovery
- fully wipe
- flash stock rom again
NOW your device will work as stock WITHOUT strange behaviour. Mine has been stock flashed 5 times. I know what I am talking about. Every time different errors, which stopped / got eliminated after wiping inbetween.
The problem is, if you send your device to an OnePlus contractor or OnePlus servicepoint, they will not do this, since even THEY are not aware. Because after a stock flash the phone INTENTS to work normally. Strange behaviour sometimes even starts after set-up.
It's the most frustrating phone I ever had.
Click to expand...
Click to collapse
I agree to some point... When it comes to rooting and updating when rooted this Phone is a p.i.a. If kept stock it is not to bad... But you want root for a reason. I think it is because of the mediatek processor. But I am struggling with it too. I am on A16, with TWRP, not rooted. I want to go back to stock (locked bootloader), but I am having a hard time to understand how to do it. I would appreciate a step by step guide.... The ones on XDA so-far haven't helped me any further...
Ik zit dus in hetzelfde schuitje... (sorry for the Dutch) really curious if "The Phone lab" can fix it
The Phone Lab can only re-flash stock (not repair). You'll loose all data.
Hi everyone. this is my very first post. I'm an Owner of a Redmi 6a (Cactus) Running Lineage OS 17.1 Unofficial (20200727) and I'm having some issues with the from so. first, I would like to know which Custom ROM Its better for this model now in 2022. more stable and updated. and also. if I can change the custom ROM to another without problems, just wiping some things ( I have TWRP and Bootloader unlocked already), or I have to get back to MIUI again.
I'm seeking something with the highest android version available for this model without problems like slow charging. camera stops or issues with daily usage, I would like to get my phone a little more powerful again.
Any suggestions, and comments, are well received by me.
Thanks to everybody
welcome to the dark side
so at the beginning i just tested some of the available costom roms, each for a few days (like go shopping) to get to know the functions and to see if they are stable (stable enough - because you can't find all bugs in short time). i am now using LineageOs but this is a personal preference. maybe i should go "shopping" again to see how the other costom roms have evolved over the past two years. as long as i did this testing i flashed all the roms "dirty", this means as you said, just wiping/formatting in twrp and flash new rom but as soon as i left testing and decided to use a rom for a longer period of time i did a "clean" flash. this means flash stock rom again (be careful to don't lock your bootloader again, its preselected in miflash unlock tool), then boot system, enable adb debugging, flash twrp, flash costom rom. i would say from experience that if you do a dirty or even clean flash, lets say you do it 10 times in a row, you will not always get the same result. maybe sometimes in LineageOs (at some devices) the radio is missing, sometimes it's not. sometimes you have a bug with a camera, sometimes you don't. flashing clean should reduce the error rate. this in the first place and the different region versions make it hard to help someone who has a device specific - rom specific - one in a hundred times bug - they need some help with.