Database Info

[Q] Internal memory stuck as read only?

Hey guys I seem to have quite a problem with my skyrocket. My internal storage has become read-only. No amount of wiping, formatting, or flashing with ODIN changes anything.
As soon as anything on my phone tries to save data, the /data partition gets remounted as RO and every app begins to crash.
I tried a factory reset, which reported success until I booted up and everything was still there on the phone.
So I tried to reflash the phone with ODIN which also reported success, but when the phone rebooted it was still running the same ROM (CM10 nightly) and all my old data was still there. I've tried flashing both the rom and the recovery and neither can be written to.
Any ideas on what happened? Sadly the phone was a refurb and so it's 90 day warranty is up so I can't just send it in.
Edit: I should add that I didn't do anything to the phone when this happened. It happened during the evening while I was out. I woke up the next morning to my phone force closing and on reboot all the texts and pictures I had since about 12:30 AM were gone.

What did you flash with Odin?
Try flashing a completely stock build.
Remounting partition as RO happens when partition has errors. You might want to reflash stock with repartitioning, there is a PIT map in one of the threads on the main page of Q&A.

Jack_R1 said:
What did you flash with Odin?
Try flashing a completely stock build.
Remounting partition as RO happens when partition has errors. You might want to reflash stock with repartitioning, there is a PIT map in one of the threads on the main page of Q&A.
Click to expand...
Click to collapse
Originally I tried flashing a different CWM build and TWRP. Neither of which actually got written to the phone.
I just tried flashing stock ICS without repartitioning and it booted right back into CM10.
So next I tried flashing stock with re-partitioning checked and a PIT file vincom had posted in another thread. It still booted right back into CM10 after reporting success in ODIN.

Very strange, but if even download mode doesn't succeed in writing to the device - I don't think there's anything that can be done but HW repair.

That's what I thought as well. I've found a couple of other people with the same problem throughout the various GS2 variants. Unfortunately the only fix I've seen anyone find is to get a replacement from Samsung.
I may have to buy one off someone with a broken screen and swap out the circuit boards.

to clarify, do not check "repartitioning" in odin, it will cause a hardbrick for the skyrocket, in op's case he has a nand error so repartitioning wont cause a hardbrick because it wont repartition since it wont write anything because a failure in the nand(write failure). as far as i know its a hardware failure and there is no workaround for that failure. but u can read this post http://forum.xda-developers.com/showthread.php?t=1704646 and see if the steps there will help

[Q] Flashing no longer possible: Flash successful but system does not change

Hello!
I can no longer flash anything to my GT-P5110, even factory reset has no effect. The internal storage seems to be read-only.
I think this is a longer story: About one year ago the stock firmware became incredibly slow, to the point that processes started to force close, then my user data was lost, and after factory reset the tablet went into endless boot loop.
So I decided to give CM10 a try and it worked flawlessly. The tablet was fast again. I even could upgrade to CM11 later. But around 2 month ago, only sometimes processes started to force-close or the tablet randomly rebooted itself - mostly during charging. I left it that way in the charger for some days because I had no time to bother with that issue. Then, I tried to factory reset my device only to find out that this has absolutely no effect. Installing app updates: No effect. Changing system settings: No effect. And apps start to force-close at an insane rate short after boot. The device is unusable. My could only shut down and reboot into recovery. I left the tablet lying around, turned off, out of charger, for 2 months. Now I tried to investigate:
When I "adb shell" into recovery and call dmesg, I see lots of these lines:
Code:
mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
I think something is really broken with the internal storage. I tried to flash a newer recovery but it has no effect, even when done from download mode.
Factory reset sometimes fails with an error. Reinstalling CM fails with an error. Wiping cache seemingly succeeds but I'm sure it has no effect. I tried installing SlimRom instead which seemingly succeeds, too - but after reboot I'm greeted with the CM boot logo again.
I tried to flash stock firmware with Odin. It is very very slow, runs for about 15 minutes, then fails at around 50%. Of course: That "half flashed firmware" does in no way affect the device: It still boots CM11 "without problems", then a few seconds after finishing boot (showing home screen), force-closes start to pop-up.
What should I do? I suppose the device is out of warranty for a few weeks or months, now. And even when not: It has been flashed with CM, the triangle counter is not zero. I suppose that combination of problems (read-only/failing storage, non-stock firmware) voids warranty in a way that Samsung will deny any repair. If at least I could return the device to stock firmware things would be different maybe.
Any ideas what I could try? Is it possible that the internal storage is simply fried? fsck'ing the partitions shows no errors, just the data partition is unclean with unwritten journal data but all data is readable. So the internal storage has probably not died. It just sticks to read-only mode for whatever reason.
I've found some posts with similar problems but those seem to be about older Galaxy Tab 1 devices built 2011 or before.

Just reading over this and it sounds very similar to what I'm currently facing, which is doubly annoying as no one else has chipped in a solution
I had reboot issues with my Tab2 10.1 (GT-P5110) on stock so after realizing I'd need to factory reset bite the bullet and rooted so I could use CM10.
Had occasional reboots but nothing I couldn't live with however from yesterday evening the tablet is seemingly stuck in a boot loop. It comes on, some apps fire up and an update starts. Sometimes apps force close then BOOM I get the boot splash screen.
I've tried factory reset in recovery (CWM 6.0.2.7) to no avail and wiping just about everything which also had no noticeable effect as all my settings and the rom are still the same when I get back in (albeit briefly!).
I've tried flashing new recovery via ODIN which reported a success however that also didn't appear to take. I'm beginning to think it some serious file system or storage corruption ;(

Same problem here...
Hopefully someone can come up with a solution or at least a cause. I've tried to Odin every recovery available for my 5113 and nothing has taken. I'm currently on Omni with cwm and tried to update to the latest cwm and twrp and aroma installer yet nothing takes. I too rooted because of the incessant bootloops about 3 months ago.

bigg fella said:
Hopefully someone can come up with a solution or at least a cause. I've tried to Odin every recovery available for my 5113 and nothing has taken. I'm currently on Omni with cwm and tried to update to the latest cwm and twrp and aroma installer yet nothing takes. I too rooted because of the incessant bootloops about 3 months ago.
Click to expand...
Click to collapse
For what I can tell, my device is effectively read-only. Even in download mode (Odin) I cannot even flash a different recovery (tried to flash TWRP, still boots CWM).

hurikhan77 said:
For what I can tell, my device is effectively read-only. Even in download mode (Odin) I cannot even flash a different recovery (tried to flash TWRP, still boots CWM).
Click to expand...
Click to collapse
exactly, can't even uninstall an app. It's as if it boots from a permanent back up because even deleting pictures or files isn't permanently successful. You can uninstall and delete to your hearts content, get false hope, and get crushed after it reboots and everything is unchanged

Not looking very optimistic for this I was getting a similar inkling that it's gone into a permanent RO mode as not even the wipes from recovery have an effect. I'd also tried un-installing apps as I noticed one updating and thought it was crashing it however even when it did fire up and I disabled WLAN to stop Play Store auto-updating and removed the app on the next reboot cycle the app was back:crying::crying:
I fear I may have a big white paperweight....

Sounds like the internal partitions might need to be completely reformatted. This CAN be done through recovery, but is tricky... However without actually having your device in my hand I'm not sure 100 what the best course of action would be. Try searching for the commands to format (or maybe someone else will post them) or maybe PM me for them but no promises. I won't post them publicly on XDA because honestly there are too many users who do stuff like one-click root and don't actually know what they're doing and I don't want to be in some way responsible for someone following the command wrong and bricking their device for good. I don't need that on my conscience. Personal choice.
Sent from my Nexus 4 using XDA Premium HD app

shakatu said:
Sounds like the internal partitions might need to be completely reformatted. This CAN be done through recovery, but is tricky... However without actually having your device in my hand I'm not sure 100 what the best course of action would be. Try searching for the commands to format (or maybe someone else will post them) or maybe PM me for them but no promises. I won't post them publicly on XDA because honestly there are too many users who do stuff like one-click root and don't actually know what they're doing and I don't want to be in some way responsible for someone following the command wrong and bricking their device for good. I don't need that on my conscience. Personal choice.
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
Would this method be any different to the way it attempts to reformat the internal partitions when you select to format the various mounts from CWM? If so I'm more then willing to give it a go as I really have nothing to lose as the damn thing is useless atm!

shakatu said:
Sounds like the internal partitions might need to be completely reformatted. This CAN be done through recovery, but is tricky... However without actually having your device in my hand I'm not sure 100 what the best course of action would be. Try searching for the commands to format (or maybe someone else will post them) or maybe PM me for them but no promises. I won't post them publicly on XDA because honestly there are too many users who do stuff like one-click root and don't actually know what they're doing and I don't want to be in some way responsible for someone following the command wrong and bricking their device for good. I don't need that on my conscience. Personal choice.
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
Good call......Smart move?

help!!
same issue here , sort of .. i have stock rom and stock recovery and i cannot flash CWM .. no matter how many times i try through ODIN or hemidal nothing changes.. any idea what is going on here?

PMs have been sent. Hopefully it works.
Sent from my Nexus 4 using XDA Premium HD app

im also having this issue with my galaxy tab2 7".. help is badly needed

Well, the proposed fix I had didn't help. Was worth a shot...
Sent from my Nexus 4 using XDA Premium HD app

hope someone finds a solution for this.

No Access to ADB
shakatu said:
PMs have been sent. Hopefully it works.
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
Hi Shakatu,thanks for the PM, however, my device in ADB is unauthorised, so wont let me get into shell. Is there a way around this please?

sunnytimes said:
same issue here , sort of .. i have stock rom and stock recovery and i cannot flash CWM .. no matter how many times i try through ODIN or hemidal nothing changes.. any idea what is going on here?
Click to expand...
Click to collapse
Unmark "Auto Reboot" in Odin when CWM is flashed... Stock room overwrites it during start.
After flashed CWM start in Recovery mode and flash new ROM.
this is offtopic in this tread

same problem please help me... :crying:

seagman said:
Unmark "Auto Reboot" in Odin when CWM is flashed... Stock room overwrites it during start.
After flashed CWM start in Recovery mode and flash new ROM.
this is offtopic in this tread
Click to expand...
Click to collapse
i have tried that 100 times .. its also exactlly what this thread is about , not being able to flash because nothing changes..

sunnytimes said:
i have tried that 100 times .. its also exactlly what this thread is about , not being able to flash because nothing changes..
Click to expand...
Click to collapse
same here too, i have same issue.. unable to flash or do anything to my phone....

Probably this is the end for our tab. As off now the tab is useless.
Sent from my GT-N7000 using XDA Free mobile app

OTA update Fail, Save my data

Hi ~
- Be kind with me, it's my first post! -
I'm facing a very bad problem with my Galaxy S6. A week ago I received an OTA from Samsung and I installed it. My phone rebooted and showed the bugdroid, meaning that the update was progressing. After that, the device keep rebooting over and over just after I entered my encryption password. I said to myself that I can try to wipe the cache because maybe an application was causing this problem. But now, the device is only showing the Samsung logo then just shut himself off.
Now I need your help to get my data. The hard part is that my device is encrypted. After many hour of search I see two solutions:
Flash the rom via ODIN
Install TWRP which can read encrypted volumes
The first solution seems easy and I keep the warranty. The problem is that I'm not 100% sure that flashing the rom again will not touch the /data and /sdext partitions (and the header/footer where master key are to decrypt the volume).
The second solution seems safer and should not touch any other partitions. But knox counter will be incremented and I will loose my warranty.
So, does anyone could test if flashing the rom via ODIN do not absolutely touch encrypted volumes and certificate that I will be able to get my data again?
Thank you a lot

Have a leap of faith. Go ahead and flash. Otherwise bring it to Samsung for warranty repair. They may be able to recover your data for you.

roydok said:
Have a leap of faith. Go ahead and flash. Otherwise bring it to Samsung for warranty repair. They may be able to recover your data for you.
Click to expand...
Click to collapse
I want to be sure and I don't want to loose any photos if possible, so no
I already tried to go in a Samsung repair store (Allo PSM), but they just don't care about my data, their job is just to make the phone working again.

So Anyone is able to confirm to me that flashing stock Galaxy S6 ROM (AP Via Odin) doesn't touch the /data and /sdext partition that are encrypted?

After many hours of search, I was able to make my phone working again!
For anyone concerned by the problem in the future, here's some informations:
You can flash a stock rom, your encrypted /data will not be erased and you will be prompt to enter your password on the next boot
In my case flashing a newer rom didn't solve my problem (bootloop after entering the password of the encrypted partition). I had to flash the rom that was in the phone before the OTA.
Now everything seems to working again. No data were lost, all my configuration was saved. Android showed a message that a problem occurred during the upgrade process and I sent logs to Samsung, hoping that it will help them!

Issues after cm13 flashing, infamous bootloop, and other festivities

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

S7 edge stock. Need advice. Annylise of 4 months.

Hello all.
It's a long story and I will try explain my problem as good as I can.
So it all started a year ago on my other s7 edge. It was rooted and I was running a rom. Loved that one. Not gonne name it because my screen totally burned in with an app. It was due the screen was broken. So samsung gave a new one for free. They didnt even check.
This is where I think things go wrong. I had to wait a bit so my boss gave me his old htc for the time being. So finally I got my new edge. A week or two before npugat update. Now after nougat I notice things are not right. Allot of core apps don't upgrade. So had to do it manually.
Okay no problems. So called help support. They ticked auto update on wifi and mobile a few time. And he told me. My co worker told me about this weird bug. If this doesnt work you need to make a new google acc and samsung acc and factory reset. So I was like hmmm no. Allot of payed apps.
So I was thinking... lets check some stuf. So I activated the dev settings and then backup and restore. And there it was an option called auto restore after a new installation... well my last login was on a htc.
So okay i have tryed allot and here are things I have discovered.
-Core apps are the most early version there are
-If I go to google play store or samsung. The most basic apps like email and clock and so one. It says not compitable with ur device. Even if I update it manually.
-If I want to report stock apps it will always say app id or package name are missing.
-A few app permissions only work.
-I also didnt update a few apps and they had five or more new releases. Still says nope still ot will say its the latest version.
-So software update still works. Last week a new security patch. But really everything is messed up.
-Cant manual update any apps any more. Always app conflict or not compitable.
-So I installed a few device software and hardware info. Radio unknown sdk unkown and so on.
-So finally installed an emulator and runned the command $sh getprop. U can guess allot of unknowns and false and negative settings. With negative it says -1 or -0.....
So im really clueless. I need a real total clean wipe. Reinstalled bl cp and ap and csc.. If I will check off auto restore after new device or restore and flash it with odin. Will this solve this issue?
And what are the proper odin settings and do I need to use the pit file? Cus Somehow the latest update tryed to install core apps on my external sd card... Its a 0 mb card since I dont use a sd card.. But I did had one on my old one.
I hope to get some tips. Because this time I wont flash or root without someone else his advice. Everything I told is in a period of 4 months.
Thnx in advance. Hope to hear soon.

AllSmokeEm said:
Hello all.
It's a long story and I will try explain my problem as good as I can.
So it all started a year ago on my other s7 edge. It was rooted and I was running a rom. Loved that one. Not gonne name it because my screen totally burned in with an app. It was due the screen was broken. So samsung gave a new one for free. They didnt even check.
This is where I think things go wrong. I had to wait a bit so my boss gave me his old htc for the time being. So finally I got my new edge. A week or two before npugat update. Now after nougat I notice things are not right. Allot of core apps don't upgrade. So had to do it manually.
Okay no problems. So called help support. They ticked auto update on wifi and mobile a few time. And he told me. My co worker told me about this weird bug. If this doesnt work you need to make a new google acc and samsung acc and factory reset. So I was like hmmm no. Allot of payed apps.
So I was thinking... lets check some stuf. So I activated the dev settings and then backup and restore. And there it was an option called auto restore after a new installation... well my last login was on a htc.
So okay i have tryed allot and here are things I have discovered.
-Core apps are the most early version there are
-If I go to google play store or samsung. The most basic apps like email and clock and so one. It says not compitable with ur device. Even if I update it manually.
-If I want to report stock apps it will always say app id or package name are missing.
-A few app permissions only work.
-I also didnt update a few apps and they had five or more new releases. Still says nope still ot will say its the latest version.
-So software update still works. Last week a new security patch. But really everything is messed up.
-Cant manual update any apps any more. Always app conflict or not compitable.
-So I installed a few device software and hardware info. Radio unknown sdk unkown and so on.
-So finally installed an emulator and runned the command $sh getprop. U can guess allot of unknowns and false and negative settings. With negative it says -1 or -0.....
So im really clueless. I need a real total clean wipe. Reinstalled bl cp and ap and csc.. If I will check off auto restore after new device or restore and flash it with odin. Will this solve this issue?
And what are the proper odin settings and do I need to use the pit file? Cus Somehow the latest update tryed to install core apps on my external sd card... Its a 0 mb card since I dont use a sd card.. But I did had one on my old one.
I hope to get some tips. Because this time I wont flash or root without someone else his advice. Everything I told is in a period of 4 months.
Thnx in advance. Hope to hear soon.
Click to expand...
Click to collapse
I would try flashing the stock firmware via Odin, download the firmware and place it in the AP slot in Odin with default settings and options, don't change anything in Odin. Then flash it.
If it bootloops after flashing, boot to stock recovery and factory reset/wipe cache in recovery.
If that doesn't work you can try flashing the firmware again along with the PIT for your model number. Place your firmware in the AP slot then find the PIT tab in Odin and place the PIT there, then in the options for Odin, make sure the "repartition" option has a check beside it, then flash the device.
Again, you might have to boot to recovery after flashing to wipe the device if it bootloops after flashing.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Droidriven said:
I would try flashing the stock firmware via Odin, download the firmware and place it in the AP slot in Odin with default settings and options, don't change anything in Odin. Then flash it.
If it bootloops after flashing, boot to stock recovery and factory reset/wipe cache in recovery.
If that doesn't work you can try flashing the firmware again along with the PIT for your model number. Place your firmware in the AP slot then find the PIT tab in Odin and place the PIT there, then in the options for Odin, make sure the "repartition" option has a check beside it, then flash the device.
Again, you might have to boot to recovery after flashing to wipe the device if it bootloops after flashing.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Thanks for the quick response.
Will this clear core apps aswell? And will it apply the "Restore settings and system" after the flash? Since last time I used odin in this way when it says wiping date it instant completed that part.
And about the bootloop. I work for a company I flash software directly on the boards. When u flash directly on a board a bootloop is good and can take up to 20 minutes. Since it have settings who need to be aplied for the next step. And those only get aplyed after a reboot. Does this count for odin aswell perhaps? When it bootloops keep it doing for a while?
Thanks

AllSmokeEm said:
Thanks for the quick response.
Will this clear core apps aswell? And will it apply the "Restore settings and system" after the flash? Since last time I used odin in this way when it says wiping date it instant completed that part.
And about the bootloop. I work for a company I flash software directly on the boards. When u flash directly on a board a bootloop is good and can take up to 20 minutes. Since it have settings who need to be aplied for the next step. And those only get aplyed after a reboot. Does this count for odin aswell perhaps? When it bootloops keep it doing for a while?
Thanks
Click to expand...
Click to collapse
Taking a while to load at first startup is normal, but bootloop is not "normal", sometimes bootloop happens depending on the operating system being flashed but generally speaking bootloop should not happen under normal circumstances when flashing with Odin.
As for clearing your apps, it should automatically format the system partition before it flashes the system.img which "should" overwrite the existing system partition with the new system.img.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Droidriven said:
I would try flashing the stock firmware via Odin, download the firmware and place it in the AP slot in Odin with default settings and options, don't change anything in Odin. Then flash it.
If it bootloops after flashing, boot to stock recovery and factory reset/wipe cache in recovery.
If that doesn't work you can try flashing the firmware again along with the PIT for your model number. Place your firmware in the AP slot then find the PIT tab in Odin and place the PIT there, then in the options for Odin, make sure the "repartition" option has a check beside it, then flash the device.
Again, you might have to boot to recovery after flashing to wipe the device if it bootloops after flashing.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Droidriven said:
Taking a while to load at first startup is normal, but bootloop is not "normal", sometimes bootloop happens depending on the operating system being flashed but generally speaking bootloop should not happen under normal circumstances when flashing with Odin.
As for clearing your apps, it should automatically format the system partition before it flashes the system.img which "should" overwrite the existing system partition with the new system.img.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Ahh okay. Will do you steps then. Hope it will work. I do have one last question.
I've just read before you flash. You have to remove all securitys like fibgerprint and accounts. And after the flash when you get at the setup. They say skip all. And add everything after so it wont restore old stuff. Is this true?

AllSmokeEm said:
Ahh okay. Will do you steps then. Hope it will work. I do have one last question.
I've just read before you flash. You have to remove all securitys like fibgerprint and accounts. And after the flash when you get at the setup. They say skip all. And add everything after so it wont restore old stuff. Is this true?
Click to expand...
Click to collapse
I don't have a Samsung device that requires these steps but it sounds like solid advice to me though. It sounds right because doing it that way means you're signing into the device without associating it to anything from before to let it complete setup without issues and then setting everything up after. Then if any of the things you re-associate cause issues, it will be easier to resolve than it would be if you flashed and restored everything during setup, doing it that way makes it hard to fix things because if something doesn't work it can cause your device to not boot properly. Doing it the after setup avoids some of those issues.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Droidriven said:
I don't have a Samsung device that requires these steps but it sounds like solid advice to me though. It sounds right because doing it that way means you're signing into the device without associating it to anything from before to let it complete setup without issues and then setting everything up after. Then if any of the things you re-associate cause issues, it will be easier to resolve than it would be if you flashed and restored everything during setup, doing it that way makes it hard to fix things because if something doesn't work it can cause your device to not boot properly. Doing it the after setup avoids some of those issues.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Okay.
Thanks allot for taking time and the great advice. Gonne follow it up and after that I might gonne install magisk su. Never heard about since last night. Will let you know the results.
Edit
Thanks sir.
As what I can see for now allot of my issues are fixed. Probaly need to test more. But like they say time will tell. Great support much appreciated. Next steps twrp superstock kernel and magisk.