Hello everyone. Wanted to share an experience with my OPO,.
Today i rebooted the phone, and when it booted up it presented me the first configuration wizard. I thought, "ok this is strange" but after i completed again the configuration everything was still there.
Tonight I tried to install the XNPH33R update via TWRP, i loaded the file into the sdcard and rebooted into TWRP.
I thought "let's make a nandroid before, in case of problems", and i saw it could not mount the /system partition. The backup failed and then i tried to reboot. The phone does now not start and when i try to boot into TWRP, it reports that now ALL the partitions are borked and can't be mounted, reporting them 0MB, except for the boot one.
My question is, am i the only one that experienced something similar?!
I'm goin on to flash factory image but this seems a big problem!
Little hint: try to install another recovery (e.g. CWM, Philz...) before returning to stock
I doubt OnePlus (or any other mfg) would count this sort of thing a bug if your phone is running anything other than 100% stock.
CafeKampuchia said:
I doubt OnePlus (or any other mfg) would count this sort of thing a bug if your phone is running anything other than 100% stock.
Click to expand...
Click to collapse
Obviously i don't want to report a "bug" that i want oneplus to fix
I just wanted to know what happened, my partitions corrupted themselves by... rebooting?
since i saw that many users reported being stuck at the oneplus logo after updating to XNPH33R i wanted to know if this is related to their experience :silly:
dreamerguy00 said:
Little hint: try to install another recovery (e.g. CWM, Philz...) before returning to stock
Click to expand...
Click to collapse
I flashed the factory image except for recovery and everything works, same old TWRP now reports everything as ok and running.. it's just strange! i flashed countless devices and i own a Nexus 4 and a Nexus 5!
blackbird5308 said:
Obviously i don't want to report a "bug" that i want oneplus to fix
I just wanted to know what happened, my partitions corrupted themselves by... rebooting?
since i saw that many users reported being stuck at the oneplus logo after updating to XNPH33R i wanted to know if this is related to their experience :silly:
I flashed the factory image except for recovery and everything works, same old TWRP now reports everything as ok and running.. it's just strange! i flashed countless devices and i own a Nexus 4 and a Nexus 5!
Click to expand...
Click to collapse
Sorry wrong thread
Sent from E.P.D.Center
I had the same weird problem last night.....
Except my recovery was also reverted to stock.
it happened after i got notifed about an update available couple days in a row which i canceled.
I even have Droidwall and everything but a few apps are blocked from data usage.
What i would suggest is to freeze the ""system update" system app.
I kinda have a feeling the OTA updates have something to do with it.
This happend to me 1 other time a while back with an HTC One X device. Same pattern, System update notifications then couple days of ignoring .... then pooffff...
blackbird5308 said:
Hello everyone. Wanted to share an experience with my OPO,.
Today i rebooted the phone, and when it booted up it presented me the first configuration wizard. I thought, "ok this is strange" but after i completed again the configuration everything was still there.
Tonight I tried to install the XNPH33R update via TWRP, i loaded the file into the sdcard and rebooted into TWRP.
I thought "let's make a nandroid before, in case of problems", and i saw it could not mount the /system partition. The backup failed and then i tried to reboot. The phone does now not start and when i try to boot into TWRP, it reports that now ALL the partitions are borked and can't be mounted, reporting them 0MB, except for the boot one.
My question is, am i the only one that experienced something similar?!
I'm goin on to flash factory image but this seems a big problem!
Click to expand...
Click to collapse
Related
I have had my phone a month and its been working flawlessly. I've installed a few custom roms on it and I'm comfortable with all the technical side from years of doing this.
What happened is my phone had a random shutdown and on reboot there was a com.androidsystemui error. No problem I thought, so I wiped the phone and restored a backup of the same rom (latest Heisenberg which has been very stable for me) same issue. OK maybe its rom related. So I did a clean install of Slimkat which I have found v stable. Instant reboot on setup. After trying this a few times I took the nuclear option and wiped by entire phone including storage and went through all this again using otg. Same problems.
I can only think its recovery or sim card related? any ideas?
btw I have tried fixing permissions and repairing file system in recovery. Thanks in advance!
parmafran said:
I have had my phone a month and its been working flawlessly. I've installed a few custom roms on it and I'm comfortable with all the technical side from years of doing this.
What happened is my phone had a random shutdown and on reboot there was a com.androidsystemui error. No problem I thought, so I wiped the phone and restored a backup of the same rom (latest Heisenberg which has been very stable for me) same issue. OK maybe its rom related. So I did a clean install of Slimkat which I have found v stable. Instant reboot on setup. After trying this a few times I took the nuclear option and wiped by entire phone including storage and went through all this again using otg. Same problems.
I can only think its recovery or sim card related? any ideas?
Click to expand...
Click to collapse
What recovery are you using? I would consider trying out Philz touch recovery, not sure it will fix it, but its worth a shot anyways.
I have exactly the same bug, with my one (the one with these problems is for a friend) i once had this too, i thougt flashing every image file from stock image has fixed it ill try it in some hours.
BTW i use TWRP v 2.7.1.1 or 2.8.0.1 but this lsat one dont works with multirom for now
I managed to fix it! I used this guide: http://forum.xda-developers.com/one...fs-corrupt-t2879061/post55531560#post55531560
parmafran said:
I managed to fix it! I used this guide: http://forum.xda-developers.com/one...fs-corrupt-t2879061/post55531560#post55531560
Click to expand...
Click to collapse
Thank you very much
Read the full thread. Possibly a latest twrp issue.
I just rooted my phone, restarted made sure it was working (not the first time I've rooted), then I installed a few zips, restarted my phone a couple times and it was all working fine. I then made a nandroid backup with TWRP, and restarted my phone and it's suddenly running really slow, and I have the constant message saying "Storage Space running out" even though I have over 8GB free. I even just restored my phone to this backup, but as I expected, same error. Any ideas?:crying:
Jimmeeehhhh said:
I just rooted my phone, restarted made sure it was working (not the first time I've rooted), then I installed a few zips, restarted my phone a couple times and it was all working fine. I then made a nandroid backup with TWRP, and restarted my phone and it's suddenly running really slow, and I have the constant message saying "Storage Space running out" even though I have over 8GB free. I even just restored my phone to this backup, but as I expected, same error. Any ideas?:crying:
Click to expand...
Click to collapse
Did you wipe /cache in TWRP?
beekay201 said:
Did you wipe /cache in TWRP?
Click to expand...
Click to collapse
Yup, had no effect at all.. I resorted to flashing the factory image and re-rooting and installing zips. Still interested in a fix for this though, on the small chance it happens again[emoji16]
Jimmeeehhhh said:
Yup, had no effect at all.. I resorted to flashing the factory image and re-rooting and installing zips. Still interested in a fix for this though, on the small chance it happens again[emoji16]
Click to expand...
Click to collapse
The next step I was going to suggest was to flash /system again. Some people posted wiping /cache was enough for them, but others had to reflash /system.
beekay201 said:
The next step I was going to suggest was to flash /system again. Some people posted wiping /cache was enough for them, but others had to reflash /system.
Click to expand...
Click to collapse
Ah that makes sense now that I think about it.. I flashed the entire image (boot, recovery etc.) but should have just done system, would have been quicker. Easy solution right there
Jimmeeehhhh said:
Ah that makes sense now that I think about it.. I flashed the entire image (boot, recovery etc.) but should have just done system, would have been quicker. Easy solution right there
Click to expand...
Click to collapse
Yep, glad it worked.
Could you please just add "[SOLVED]" to the thread title? Thanks
Hi.
Yesterday I got a notification to update to 5.1.1. ( My nexus 5 was on 5.1, everything stock, never flashed anything before )
I selected 'install' for 5.1.1, and left my phone aside. After a few minutes I saw that it was in the boot animation. I thought it was the process ongoing. Several hours later I decided to restart the phone manually ( obviously something went wrong ).
After rebooting, again, it's stuck there. On the four colored dots swirling around.
I searched on forums, I got the 5.1.1 stock, got ADB, fastboot etc, flashed as the instructions said ( via ./flash-all.sh and via the long version by manually flashing every partition ) EVERY time the same thing, when I boot it's just showing the boot animation forever.
Any idea on what's wrong?
blackjim said:
Hi.
Yesterday I got a notification to update to 5.1.1. ( My nexus 5 was on 5.1, everything stock, never flashed anything before )
I selected 'install' for 5.1.1, and left my phone aside. After a few minutes I saw that it was in the boot animation. I thought it was the process ongoing. Several hours later I decided to restart the phone manually ( obviously something went wrong ).
After rebooting, again, it's stuck there. On the four colored dots swirling around.
I searched on forums, I got the 5.1.1 stock, got ADB, fastboot etc, flashed as the instructions said ( via ./flash-all.sh and via the long version by manually flashing every partition ) EVERY time the same thing, when I boot it's just showing the boot animation forever.
Any idea on what's wrong?
Click to expand...
Click to collapse
I would wipe data.
Sandman-007 said:
I would wipe data.
Click to expand...
Click to collapse
Tried 'Wipe data/factory reset' a couple of times.
Also tried 'Wipe cache partition' later.
No difference at all. It stays for hours on the booting animation.
Can I somehow see the logs or something to see where it's stuck?
I believe you must flash factory images at this point. Just make sure you backup SD Card data or flash each partition manually skipping the userdata.img (this one erases internal storage)
Sent from my Nexus 5 using XDA Forums
Sandman-007 said:
I believe you must flash factory images at this point. Just make sure you backup SD Card data or flash each partition manually skipping the userdata.img (this one erases internal storage)
Sent from my Nexus 5 using XDA Forums
Click to expand...
Click to collapse
Well I did that, I tried 5.1, 5.1.1 and the M image.
None of them works.
At this point I'm tired of doing the whole process every time and waiting for 15 mins to see if it worked.
Thankfully, I called google support and they will send me a replacement.
I'm just very curious how this whole mess happened from a simple OTA update.
blackjim said:
Well I did that, I tried 5.1, 5.1.1 and the M image.
None of them works.
At this point I'm tired of doing the whole process every time and waiting for 15 mins to see if it worked.
Thankfully, I called google support and they will send me a replacement.
I'm just very curious how this whole mess happened from a simple OTA update.
Click to expand...
Click to collapse
If a complete wipe of the phone with factory images didn't fix it sounds like hardware. Possible corrupt NAND I think.
Sent from my Nexus 5 using XDA Forums
Sandman-007 said:
If a complete wipe of the phone with factory images didn't fix it sounds like hardware. Possible corrupt NAND I think.
Sent from my Nexus 5 using XDA Forums
Click to expand...
Click to collapse
Possibly.
In any case, they already sent me a replacement phone.
Google support has been extremely satisfying.
Hi everyone.
Let's start from the beginning, and by advance excuse me for my poor English : I happen to be a delighted owner of the Oneplus One by the Oneplus company. I've flashed different versions of cyanogen on my phone, rooted it multiple times and I never encountered any kind of problems. Thus, until I decide yesterday to flash the latest release of cyanogen, cm13 (nightly). I did some researches, followed the usual steps, flashed the right opengapps version along with cm13 and.. everything went great. Except that my phone couldn't resolve himself to detect my SIM card anymore. I tried different things in order to solve the problem, including re-wipe the phone "factory reset" style, removing SIM card, wait for the phone to cool down and played with data roaming, but nothing worked. Fortunately I had my fresh nandroid backup waiting to be restored. That's when the real deal start :
even after having restored the full nandroid backup (which make me downgrade to cm12.1), the SIM card wasn't detected.
So I decided to wipe data, dalvik, cache and system, in order to get my phone back to its original state. But the problem remains, and worst of all, the phone now tends to reboot punctually without any reasons.
I surely did something wrong for the phone to end in this state, but I can't see what..
I use TWRP 2.8.7.0 custom recovery, and the phone OS is now cm12.1-YOG4PAS3JL.
Oneplus One 64GB.
Sorry for the length of the complaint, and by advance thanks for your answers.
P.S : I did tried to search for similar threads in the forum, but I didn't manage to found anything that was directly related.
It could be an issue with the modem not being flashed properly when you went from Lollipop to Marshmallow due to TWRP 2.8.7.0. Try TWRP 2.8.6.0, and then either restore the nandroid backup or clean wipe + reflash CM13 nightly.
oble said:
It could be an issue with the modem not being flashed properly when you went from Lollipop to Marshmallow due to TWRP 2.8.7.0. Try TWRP 2.8.6.0, and then either restore the nandroid backup or clean wipe + reflash CM13 nightly.
Click to expand...
Click to collapse
Thanks a lot for your response. I've been searching a lot and the problem effectively seems to be the modem not being flashed properly. So I tried to flash it manually, (found the file 2 threads higher, sorry I can't post links yet) via fastboot and then flashing cm13 (with twrp 2.8.6.0), considering the fact it seems to have worked for others.
But no matter what I do, the issue remains : the phone isn't able to detect SIM card and goes into crash, rebooting every 2mn..
I've tried to flash cm13 unnoficial version by sultan, following his instructions, but no improvement either.
Even my nandroid backup (running cm 12.1) can't detect SIM anymore, have serious wifi connectivity issues, and keeps rebooting randomly at very reguliar intervals..
I'm really beggining to feel hopeless,
but thanks again for your time and your advices, really apreciate it.
It seems that I have same problem..... after flashing CM13 and restoring backup
Any progress with this problem?
Edit - If my phone is connected into PC with USB cable it doesnt restarts
gersa said:
It seems that I have same problem..... after flashing CM13 and restoring backup
Any progress with this problem?
Edit - If my phone is connected into PC with USB cable it doesnt restarts
Click to expand...
Click to collapse
Same for me, the phone stops crashing and rebooting randomly once connected to pc via USB cable. But still doesn't recognize SIM card. Wifi also seems to work better.
No further progress unfortunately, I've tried everything, from restoring the phone to its factory state to flashing all "stable" roms (cyanogen), nothing worked.
MethylHaine said:
Hi everyone.
Let's start from the beginning, and by advance excuse me for my poor English : I happen to be a delighted owner of the Oneplus One by the Oneplus company. I've flashed different versions of cyanogen on my phone, rooted it multiple times and I never encountered any kind of problems. Thus, until I decide yesterday to flash the latest release of cyanogen, cm13 (nightly). I did some researches, followed the usual steps, flashed the right opengapps version along with cm13 and.. everything went great. Except that my phone couldn't resolve himself to detect my SIM card anymore. I tried different things in order to solve the problem, including re-wipe the phone "factory reset" style, removing SIM card, wait for the phone to cool down and played with data roaming, but nothing worked. Fortunately I had my fresh nandroid backup waiting to be restored. That's when the real deal start :
even after having restored the full nandroid backup (which make me downgrade to cm12.1), the SIM card wasn't detected.
So I decided to wipe data, dalvik, cache and system, in order to get my phone back to its original state. But the problem remains, and worst of all, the phone now tends to reboot punctually without any reasons.
I surely did something wrong for the phone to end in this state, but I can't see what..
I use TWRP 2.8.7.0 custom recovery, and the phone OS is now cm12.1-YOG4PAS3JL.
Oneplus One 64GB.
Sorry for the length of the complaint, and by advance thanks for your answers.
P.S : I did tried to search for similar threads in the forum, but I didn't manage to found anything that was directly related.
Click to expand...
Click to collapse
`
Here is solution (for me)
http://forum.xda-developers.com/showpost.php?p=64768887&postcount=3
Read whole, its short
gersa said:
`
Here is solution (for me)
http://forum.xda-developers.com/showpost.php?p=64768887&postcount=3
Read whole, its short
Click to expand...
Click to collapse
Already saw it, but thanks ^^ that's where i found my file modemst.bin
so did it work for you ?
The same thing happened to me last week. I was using Materialized TWRP 2.8.7.0, which I think caused issues with my updating of Sultanxda's 13.1 ROM. SIM card was never detected, phone would restart shortly after every boot. I tried everything I could find to get my baseband and IMEI back.
In the end, only this solution worked for me, and I had to do it twice. I don't know why.
I had the same problem. I got back to TWRP 2.8.6.0 and then flashed the latest CM13(wiped System). after that without wipe i flashed sultans's CM13 then gapps and got the sim working again.
jp.esteban said:
The same thing happened to me last week. I was using Materialized TWRP 2.8.7.0, which I think caused issues with my updating of Sultanxda's 13.1 ROM. SIM card was never detected, phone would restart shortly after every boot. I tried everything I could find to get my baseband and IMEI back.
In the end, only [link] this solution[/URL] worked for me, and I had to do it twice. I don't know why.
Click to expand...
Click to collapse
Thanks for the link. I tried to flash the zip, but twrp(2.8.6.0) gave me an error : Error flashing ONEPLUS+ONE-FIX-Windows.zip
I tried to clean flash it and dirty flash it, nothing seems to work.
ashishsaggu said:
I had the same problem. I got back to TWRP 2.8.6.0 and then flashed the latest CM13(wiped System). after that without wipe i flashed sultans's CM13 then gapps and got the sim working again.
Click to expand...
Click to collapse
I've tried multiple times, it doesn't work. SIM card is not recognized, phones goes to reboot after 30s of use.
Whatever rom I flash the problem ain't solved, even after factory reset from original OS (cm 12.1)..
I really begin to think there is no solution, I've tried to flash my phone at least 20 times with different roms, fix, firmwares, modem, everything that is available on the net and I couldn't notice even the slightest change in the comportment of my phone.
Anyway, thanks a lot for your proposal, I guess it HAVE to work, but for some irrational reason it doesn't...
MethylHaine said:
I've tried multiple times, it doesn't work. SIM card is not recognized, phones goes to reboot after 30s of use.
Whatever rom I flash the problem ain't solved, even after factory reset from original OS (cm 12.1)..
I really begin to think there is no solution, I've tried to flash my phone at least 20 times with different roms, fix, firmwares, modem, everything that is available on the net and I couldn't notice even the slightest change in the comportment of my phone.
Anyway, thanks a lot for your proposal, I guess it HAVE to work, but for some irrational reason it doesn't...
Click to expand...
Click to collapse
Did U flash over TWRP or ADB?
Just popping in to say I have the same problem. I'm trying the various solutions presented in the thread and I'll come back and report if anything worked. I would also appreciate any other suggestions that you may have
For the record, I got into this predicament through the following steps:
1. I was flashing some CM nightly (sorry, I don't remember which one), and after reboot the touch screen didn't work anymore
2. I flashed the OxygenOs .zip that I had saved on internal storage through TWRP
3. After flash touch screen worked but no sim detected
4. Flashed CM 12.1 still no sim
5. Flashed back to OxyOs, still no sim. Curiously I am unable to reboot via software.
Anyway, I basically have all weekend to work on this, so awayyyy we go!
---
<Edit>
Wow that was fast. I followed this guy's instructions (fastboot flashing modemst, then CM12.1) and it seems to be working like a charm! Good luck everybody else!
gersa said:
Did U flash over TWRP or ADB?
Click to expand...
Click to collapse
I flashed via TWRP(2.6.8.0) and via ADB for modemst1.bin and modemst2.bin.
By the way, there's a little improvement : I flashed kalkulin's_stock_OPO Rom and that stopped my phone from rebooting.
Now cm13 is running kinda fine, except it still doesn't detect SIM card, even after reflashing modemst1 and modemst2
Edit : When I try to flash oxygenos, oneplus fix or cm12.1, (roms that are supposed to fix sim detection problem), it doesn't work : Error flashing Zip file. via adb or twrp, that's the same. (excepting the fact that error in adb is about trustzone)
I think my efs partition is somehow corrupt, and unfortunately i have no way to restore it.
MethylHaine said:
Thanks for the link. I tried to flash the zip, but twrp(2.8.6.0) gave me an error : Error flashing ONEPLUS+ONE-FIX-Windows.zip
I tried to clean flash it and dirty flash it, nothing seems to work.
Click to expand...
Click to collapse
It's not supposed to be flashed. Unzip the archive on a Windows PC, then use the .bat files in there to fix your phone.
jp.esteban said:
It's not supposed to be flashed. Unzip the archive on a Windows PC, then use the .bat files in there to fix your phone.
Click to expand...
Click to collapse
Effectively, I kinda did things completely wrong there, sorry. (I'm an exclusive linux user for my defense ^^)
Okay guys, I finally solved my problems.
Here's what I did to fix reboot crashes and SIM detection issues :
-Flash TWRP(2.8.6.0)
-Wipe everything except internal storage
-Flash Calkulin's_Stock_OPO_XNPH44S_ROM_v1.0.zip (can't post links yet, sorry)
-Boot system
-Once done, reboot to bootloader (in command prompt : sudo adb reboot bootloader)
-In command prompt, type the following commands (It will delete modem and /persist partition ! be careful) :
fastboot erase modemst1
fastboot erase modemst2
fastboot erase persist
-If you need to fix "Unable to mount /persist" error in TWRP :
adb shell
make_ext4fs /dev/block/mmcblk0p15
-Flash Oxygen OS (i flashed oxygen_1.0.0_flashable.zip)
That should restore EFS and fix the issues.
Well, that was kind off a pain in the ass, but now my problem is solved, and i'm currently running cm13 quite fine.
Make a backup of your EFS partition.
Thanks to all the people that helped me by posting in this thread !
It's a nightly build, it bound to have some problems.
i am having bootloop issue, tried many roms, erased partition too, still no use. continuous bootloops
---------- Post added at 03:08 AM ---------- Previous post was at 03:07 AM ----------
gersa said:
`
Here is solution (for me)
http://forum.xda-developers.com/showpost.php?p=64768887&postcount=3
Read whole, its short
Click to expand...
Click to collapse
i am having bootloop issue, tried many roms, erased partition too, still no use. continuous bootloops
So here is situation.
Phone been running 8.x version of havocos for months, however I was never fully happy due to broken usb tethering and random lockups (blue light freeze).
I decided to work on the phone 2-3 days ago, this involved doing a manual backup of all of data/media, and a nandroid backup. As well as some exports of configs in tasker etc.
I then flashed OOS stock, and nolimits, discovered tethering was still broken (yet it works with same sim in samsung galaxy s7 and hauwei).
This was the only issue tho, everything else was functioning as expected, phone was still fast.
Then I needed quick access to something that was on my phone from havocos, so decided to do a nandroid restore, this nandroid backup had all partitions ticked. The restore I also had all ticked.
The restore failed with an error 255 during data restore, I googled and found out is a nasty known bug for 2 years on TWRP, this backup was done on 3.2.3, I know now is a newer 3.3.x where this particular bug with corrupt backups might possibly be fixed.
I decided to try and boot havoc anyway but it boot looped, so I then went back into TWRP, and restored the vendor partition which was skipped. As it stopped on data, still boot looped, but also now this created a device is corrupt error on every rom boot even on stock OOS.
I spent ages trying to fix this error and during the process, discovered my phone no longer can be detected in flash boot as a com device in windows so currently the phone cannot be used with the MSM tool.
Eventually I reflashed stock using a flash-all script from here, and also put back on twrp using that script, and noticed even more issues that were not there before.
1 - phone is now much slower, stock before booted in one second after first boot, now its way way slower. Over 10 seconds so 10x as slow.
2 - I think before was a cache partition but is now gone. Supposedly these arent a thing anymore tho.
3 - nolimits zip will no longer flash with an error 1, I did exact same process as before but simply doesnt work now, the twrp detailed log right before the error 1 says "Please install the latest Magisk!" which suggests its failing to detect magisk.
4 - camera app is way slower, and OOS feels slower, laggier in general than before the problem.
5 - MTP no longer works when phone is booted up, again this is stock OOS and even if phone isnt rooted no magisk etc. But still works in TWRP. Basically the device pops up, I can see internal storage, but the size information is missing, and is no visible files/folders.
From what I can see I think my EFS is fine, I see an imei number.
I did fix the corrupted device error using a reboot command someone posted in that thread, so that error is gone now at least.
Try to flash oxygen os beta version from the official download links, let it install the stock recovery, then boot into rom, finish the installation progress by just skipping it and then factory reset it twice from recovery mode.
after doing that and finishing the setup , try to take picture and see if its saves it to gallery ( if the picture delete it self try to factory reset it through recovery for 1 more time)
I think you have figured out whats wrong, it just clicked, and I went to post and found your post so sorry no reply yet.
Indeed the problem seems to be a lack of /data/media/0
I have multiple times wiped data, and twrp has been putting files directly in /data/media, I just discovered I Cannot even take screenshots, magisk cannot download modules as well.
So I guess the stock recovery creates this structure?
Pretty shocking that twrp doesnt fix this or even have an option to. I will report back and let you know how things go, thanks.
Issue still there after stock recovery reset, wow these phones are damn hard to work with.
Also it seemed to do nothing, no settings were lost etc.
So basically stock recovery even if I choose full wipe does nothing, there seems to be some kind of lock on the internal storage that anything made by one plus is refusing to write.
I wonder if this is due to the device is corrupt message I had before where it said the device can no longer be trusted.
I can confirm that files that are on there are now visible in file manager and root explorer. But file manager can do no writes. root explorer can create new stuff but cannot delete or overwrite anything there, gets access denied.
I propose to start over again following this guide, option flash-all-partitions.bat. Helped for me.
I already stated thats already been done.
I eventually got msm working. and that luckily worked.
@chrcol ..., but you've issues
chrcol said:
I already stated thats already been done.
I eventually got msm working. and that luckily worked.
Click to expand...
Click to collapse
In recovery, format data. Problem fixed. Wipe will never fix your problem but format will.