Develop Bugs

is my galaxy nexus bricked?

i have a big issue with my nexus, last night i leave the phone charging, this morning i turned it on and there was a message asking me for a password to decrypt the data (i never activated that ) :S, then i went to recovery mode, tried to do a factory reset , and install the stock rom again, it said it installed it but NO, i rebooted the phone and it came back to the same 4.2.2 version i had previously installed (with all my apps on it, it is like never installed the rom) this time android did not ask for decrypt password but i got "android.media process has stopped" error (something like that) and a few seconds after that the phone rebooted itself.. at this point i decided to try odin, and i flashed a 4.1 version , odin did everything right, not error messages at all.. then the phone rebooted after finishing the installation but it came back to the same OS 4.2.2 with all my apps installed and with the same issue of android.media process has stopped blablabla, and reboot..
ive tried nexus toolkit, odin, etc.. and nothing.. it looks like it flash the files normally but then it come back to the same OS (4.2.2) with troubles.
i dont know if im wrong but it is like 4.2.2 cannot be deleted with twrp 2.3.2.1 or odin... but thats weird.. when i wipe internal storage, system, etc from TWRP it said it wiped everything, but then i reboot the phone, go to TWRP again and if i look in "install" i can see all my files. i dont know whats going on.

I dont know why you're posting the same thing in two different sections.

Relock then unlock the boot loader again. If that doesn't wipe everything you're hosed.

I'm pretty sure every version of TWRP that has been released since 2.3.1.0 has been (somewhat)broken. At least from the multiple users confirming issues of every version since then in TWRP thread... Anyways Go to the main "Team Win Recovery Project" post in the Nexus Development section and click the link to their webpage to download an older version. I personally use 2.4.1.0 without issue.
If rolling back to an older recovery doesn't solve issues, try CWM recovery. If that doesn't work either, use fastboot commands to flash the stock Google images.
Check the forum stickies in ALL of the galaxy nexus sub-forums. Everything you will need is there. Please do not use toolkits! See? It tells you success! But it was not. And now you have NO idea why. At least using fastboot if something fails it will tell you what, when, where, and why and you can relay that info and we can actually help you out more.
But I think changing recoveries will solve your problem. If not report back I'd be glad to assist you further.

RoyJ said:
I'm pretty sure every version of TWRP that has been released since 2.3.1.0 has been (somewhat)broken. At least from the multiple users confirming issues of every version since then in TWRP thread... Anyways Go to the main "Team Win Recovery Project" post in the Nexus Development section and click the link to their webpage to download an older version. I personally use 2.4.1.0 without issue.
If rolling back to an older recovery doesn't solve issues, try CWM recovery. If that doesn't work either, use fastboot commands to flash the stock Google images.
Check the forum stickies in ALL of the galaxy nexus sub-forums. Everything you will need is there. Please do not use toolkits! See? It tells you success! But it was not. And now you have NO idea why. At least using fastboot if something fails it will tell you what, when, where, and why and you can relay that info and we can actually help you out more.
But I think changing recoveries will solve your problem. If not report back I'd be glad to assist you further.
Click to expand...
Click to collapse
thanks for your answer, ill try that!

jsgraphicart said:
I dont know why you're posting the same thing in two different sections.
Click to expand...
Click to collapse
maybe because this is my only phone, i dont have warranty, i dont have money to buy another, ive tried everything i know to try to fix it and it doesn't work so at this point im a little bit desperate?

i tried using fastboot commands, and it does everything ok, i first erased system and userdata, then flashed system and userdata again, it take a while to do it, and there is not a single error in the process, but then i reboot the phone and it goes back to that damn "bigxie deodexed 4.2.2" that i installed a week ago.. for some reason it seems everytime i reboot the phone that rom and all my old files are again in the phone. (it runs the OS but it last just a few seconds before i get the android.process.media error and then an ugly reboot)
for jesus, mother theresa, allah, buddha and ganesha, help me guys!!!!

rodmc123 said:
i tried using fastboot commands, and it does everything ok, i first erased system and userdata, then flashed system and userdata again, it take a while to do it, and there is not a single error in the process, but then i reboot the phone and it goes back to that damn "bigxie deodexed 4.2.2" that i installed a week ago.. for some reason it seems everytime i reboot the phone that rom and all my old files are again in the phone. (it runs the OS but it last just a few seconds before i get the android.process.media error and then an ugly reboot)
for jesus, mother theresa, allah, buddha and ganesha, help me guys!!!!
Click to expand...
Click to collapse
If you can not change ROMs or wipe anything isn't that the sign of a bad flash partition? Its rare but can happen
Toro | Atom v9 | AK Cylon 728

Sandman-007 said:
If you can not change ROMs or wipe anything isn't that the sign of a bad flash partition? Its rare but can happen
Toro | Atom v9 | AK Cylon 728
Click to expand...
Click to collapse
and how could that be solved?

Somehow change the flash chip housing your ROM?
Posted from a Unicorn powered Nexus 4 running XDA-premium.

Ponox said:
Somehow change the flash chip housing your ROM?
Posted from a Unicorn powered Nexus 4 running XDA-premium.
Click to expand...
Click to collapse
eeh, that is not an option.
nobody can help me?
i tried to repair and to format the partition /dev/block/mmcblk0p12 using mke2fs and e2fsck but it says is apparentely in use and will not make a filesystem there, with e2fsck -b (using backup superblock) it says it cannot put a flag on the superblock blablah...
i don't know what else to do.

rodmc123 said:
eeh, that is not an option.
nobody can help me?
i tried to repair and to format the partition /dev/block/mmcblk0p12 using mke2fs and e2fsck but it says is apparentely in use and will not make a filesystem there, with e2fsck -b (using backup superblock) it says it cannot put a flag on the superblock blablah...
i don't know what else to do.
Click to expand...
Click to collapse
What happens if you install an app and reboot. Is the app still there? If not you are screwed and need a new phone
Toro | Atom v9 | AK Cylon 734

Sandman-007 said:
What happens if you install an app and reboot. Is the app still there? If not you are screwed and need a new phone
Toro | Atom v9 | AK Cylon 734
Click to expand...
Click to collapse
i cant do that, when the OS loads, it last like 5 second before it reboot itself, so i dont have time to do anything.
all i can do now is from recovery, fastboot, adb, etc.. i cant do anything inside the OS.
i think the flash memory of the phone is dead or something.. thats why it comes back always to the same state after a reboot.
for example i used adb push to send a rom to the sd card, and inside the recovery, in "install" i saw the file i just passed but i rebooted the phone, went back to recovery and the file was gone... the same if i format data, it seems it works, but i reboot and everything is there again. All changes i do in the internal memory from fastboot, adb and recovery disappear after a reboot.

rodmc123 said:
i cant do that, when the OS loads, it last like 5 second before it reboot itself, so i dont have time to do anything.
all i can do now is from recovery, fastboot, adb, etc.. i cant do anything inside the OS.
i think the flash memory of the phone is dead or something.. thats why it comes back always to the same state after a reboot.
for example i used adb push to send a rom to the sd card, and inside the recovery, in "install" i saw the file i just passed but i rebooted the phone, went back to recovery and the file was gone... the same if i format data, it seems it works, but i reboot and everything is there again. All changes i do in the internal memory from fastboot, adb and recovery disappear after a reboot.
Click to expand...
Click to collapse
Yep flash memory is done
Toro | Atom v9 | AK Cylon 734

Jeesus , how many ROMs have you flashed that you wore out the ROM chip in your phone?! It takes like 1,000 writes to kill it!
Posted from a Xylon powered Nexus 4 running XDA-premium.

Ponox said:
Jeesus , how many ROMs have you flashed that you wore out the ROM chip in your phone?! It takes like 1,000 writes to kill it!
Posted from a Xylon powered Nexus 4 running XDA-premium.
Click to expand...
Click to collapse
thats the weird thing.. i flashed in total like.. 10-15 times?? i think is not that much , because there is people here flashing their phones atleast twice per day...
anyway the phone is not totally dead, i mean i can turn it on, go to fastboot, recovery, adb works... the thing is as soon as i reboot the phone, every change i did dissapear (like wiping data, system, etc) , and the phone has again the exact same files, rom, etc.. the worst thing is that i cant even use the rom that stil loads, becase it reboots like 2 seconds after i enter my pin.
i tried everything, fastboot formating and flashing, e2fsck, mke2fs, etc..
this kind of issue should requiere a mainboard replacement i guess? is there a way to force the flash memory to work again.. like giving it an electric shock lol! i miss my nexus :crying:
this is my phone now :crying:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

rodmc123 said:
thats the weird thing.. i flashed in total like.. 10-15 times?? i think is not that much , because there is people here flashing their phones atleast twice per day...
anyway the phone is not totally dead, i mean i can turn it on, go to fastboot, recovery, adb works... the thing is as soon as i reboot the phone, every change i did dissapear (like wiping data, system, etc) , and the phone has again the exact same files, rom, etc.. the worst thing is that i cant even use the rom that stil loads, becase it reboots like 2 seconds after i enter my pin.
i tried everything, fastboot formating and flashing, e2fsck, mke2fs, etc..
this kind of issue should requiere a mainboard replacement i guess? is there a way to force the flash memory to work again.. like giving it an electric shock lol! i miss my nexus :crying:
this is my phone now :crying:
Click to expand...
Click to collapse
Eh, its been a while since the last post, but when running e2fsck, did you make sure /data was unmounted before running terminal?

desktopfusion said:
Eh, its been a while since the last post, but when running e2fsck, did you make sure /data was unmounted before running terminal?
Click to expand...
Click to collapse
yep

Try this:
http://forum.xda-developers.com/showthread.php?p=25775981
Sent from my Galaxy Nexus using xda app-developers app

Video and/or step by step firmware upgrade instructions available?

So let me explain the scenario; I have a T-Mobile M9 that's S-Off, running Venom, and wanted to update the firmware from 1.32 to 2.7. I had done this in late July and got the success, and the firmware was running fine, but eventually the phone decided to just shut off on me, and the only way to turn it back on was via forced reboot. For the two weeks after that I had tried just about every method I read on Sneakyghost's post on the subject (I did an RUU, changed to superCID and flashed 2.10, did the full wipe and no wipe firmware) and every single time if I updated to anything newer than what was on my M9 originally it would, inevitably, do that thing where it became unresponsive after a while.
Since this seems to be a problem that only I'm having, I assume it's something I have to be doing wrong. With that in mind, is there any sort of video that has been made or really, really simple and thorough step by step instructions that could guide me through the process in a detailed way? I hate that I have to ask this, but I feel like I've done my homework and tried several different methods, and all of them have failed. I have HTC sync installed, I've tried on two different computers, I've done everything. I even flashed back 1.32 in the exact same way that I flashed 2.7, and as soon as I put it back to the old one it immediately solves the problem. Without fail putting the new firmware on has made my phone do this at least once within two days of installing, and then multiple times after that (I must've tried this about four or five separate times over three weeks). The obvious problem here is that the phone is completely unresponsive, which means that if it does this overnight my alarm doesn't work. Not to mention the missed calls and annoyances that occur when it happens throughout the day.
I just want to be able to experience the new firmware. Because right now I still have to deal with a (relatively) crappy camera experience and a phone that overheats constantly. I'm also really worried that when the M update comes out it may force me to have a newer firmware, and if I can't do it correctly I'll be out of luck.
So if anyone could help it'd be so very appreciated, either by telling me something I could have done wrong (I flashed the firmware via fastboot method both over viper and later over a stock Sense build). I also have the newest radio, so I literally have no idea what I could be doing wrong at this point, but I hope someone does. Again, thanks in advance.

guyverzero said:
So let me explain the scenario; I have a T-Mobile M9 that's S-Off, running Venom, and wanted to update the firmware from 1.32 to 2.7. I had done this in late July and got the success, and the firmware was running fine, but eventually the phone decided to just shut off on me, and the only way to turn it back on was via forced reboot. For the two weeks after that I had tried just about every method I read on Sneakyghost's post on the subject (I did an RUU, changed to superCID and flashed 2.10, did the full wipe and no wipe firmware) and every single time if I updated to anything newer than what was on my M9 originally it would, inevitably, do that thing where it became unresponsive after a while.
Since this seems to be a problem that only I'm having, I assume it's something I have to be doing wrong. With that in mind, is there any sort of video that has been made or really, really simple and thorough step by step instructions that could guide me through the process in a detailed way? I hate that I have to ask this, but I feel like I've done my homework and tried several different methods, and all of them have failed. I have HTC sync installed, I've tried on two different computers, I've done everything. I even flashed back 1.32 in the exact same way that I flashed 2.7, and as soon as I put it back to the old one it immediately solves the problem. Without fail putting the new firmware on has made my phone do this at least once within two days of installing, and then multiple times after that (I must've tried this about four or five separate times over three weeks). The obvious problem here is that the phone is completely unresponsive, which means that if it does this overnight my alarm doesn't work. Not to mention the missed calls and annoyances that occur when it happens throughout the day.
I just want to be able to experience the new firmware. Because right now I still have to deal with a (relatively) crappy camera experience and a phone that overheats constantly. I'm also really worried that when the M update comes out it may force me to have a newer firmware, and if I can't do it correctly I'll be out of luck.
So if anyone could help it'd be so very appreciated, either by telling me something I could have done wrong (I flashed the firmware via fastboot method both over viper and later over a stock Sense build). I also have the newest radio, so I literally have no idea what I could be doing wrong at this point, but I hope someone does. Again, thanks in advance.
Click to expand...
Click to collapse
instructions are here >> http://forum.xda-developers.com/att-one-m9/general/att-developer-edition-ruu-how-to-t3086948
use the sdcard method and the DE RUU or the T-mobile RUU and your phone should work fine

clsA said:
instructions are here >> http://forum.xda-developers.com/att-one-m9/general/att-developer-edition-ruu-how-to-t3086948
use the sdcard method and the DE RUU or the T-mobile RUU and your phone should work fine
Click to expand...
Click to collapse
Would restoring my nandroid after flashing that RUU cause anything to go wrong?

guyverzero said:
Would restoring my nandroid after flashing that RUU cause anything to go wrong?
Click to expand...
Click to collapse
it's always better to start fresh after the RUU

Nope, it's doing the same thing again. This is my GSam from last night.
Now, let me stress that I did everything clean. RUU, did a clean setup, clean venom flash, etc. I didn't restore any settings. I don't know what to do, as the phone is completely normal under 1.32. Oh and I flash 1.32 in the same exact way I do 2.7 as well, there's no difference
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my HTC One M9 using Tapatalk

GPS Fix Issues

Is anyone with an HTC 10 having any GPS lock issues? I wasnt having issues for months and months of owning my Vzw HTC 10 but just recently I've been unable to get a lock almost always. I see that my phone can FIND satellites it just can't use them.
Currently rooted and s off, stock Rom with twrp.
I've tried resetting agps and refreshing, I've tried switching between Global and CDMA. I'm not really to keen on factory resetting as I'm afraid a. It won't help and b. I'll have to redo all my work with rooting, sunshine, etc. (I could be wrong about that... Forgive me I'm no expert with this stuff, just know enough to follow instructions to get to where I want to be lol)
Does anyone have any ideas or suggestions? I have a hard time believing there's anything actually wrong with my GPS sensor so to speak especially since it can find satellites it just isn't fixing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Launchpadmcqu4ck said:
Is anyone with an HTC 10 having any GPS lock issues? I wasnt having issues for months and months of owning my Vzw HTC 10 but just recently I've been unable to get a lock almost always. I see that my phone can FIND satellites it just can't use them.
Currently rooted and s off, stock Rom with twrp.
I've tried resetting agps and refreshing, I've tried switching between Global and CDMA. I'm not really to keen on factory resetting as I'm afraid a. It won't help and b. I'll have to redo all my work with rooting, sunshine, etc. (I could be wrong about that... Forgive me I'm no expert with this stuff, just know enough to follow instructions to get to where I want to be lol)
Does anyone have any ideas or suggestions? I have a hard time believing there's anything actually wrong with my GPS sensor so to speak especially since it can find satellites it just isn't fixing.
Click to expand...
Click to collapse
I have not had any issues, i am currently on 1.82.605.6 firmware & deodex base.
1. Have you installed a custom kernel?
2. In the locations settings, have you set the location to just GPS? (shouldn't matter anyways)
3. It looks as though you have a software update? i assume you are running santod rom, which should work anyways.
I would just RUU back to stock, it wont break sunshine. you will need to reinstall twrp & superSU after performing the RUU. then test it stock and go from there.
Good Luck

Launchpadmcqu4ck said:
. I'm not really to keen on factory resetting as I'm afraid a. It won't help and b. I'll have to redo all my work with rooting, sunshine, etc. (I could be wrong about that... Forgive me I'm no expert with this stuff, just know enough to follow instructions to get to where I want to be lol)
Click to expand...
Click to collapse
That's no issue.
Simply backup System, boot and User data in TWRP (well, actually you only need UserData. But if you have them all your safe whenever whatever ^^)
Go to advanced wipe and select UserData, Cache, Dalvik.
Don't select Internal Storage/ SD card this would delete all your data you don't want deleted.
So reboot your phone and setup your Google account again.
Sunshine and root and all that stuff will persist.
If it doesn't help you can easily restore UserData only, via TWRP.
but then you will have to try installing a ruu anyway, which will delete ALL your data.

Launchpadmcqu4ck said:
Is anyone with an HTC 10 having any GPS lock issues? I wasnt having issues for months and months of owning my Vzw HTC 10 but just recently I've been unable to get a lock almost always. I see that my phone can FIND satellites it just can't use them.
Currently rooted and s off, stock Rom with twrp.
I've tried resetting agps and refreshing, I've tried switching between Global and CDMA. I'm not really to keen on factory resetting as I'm afraid a. It won't help and b. I'll have to redo all my work with rooting, sunshine, etc. (I could be wrong about that... Forgive me I'm no expert with this stuff, just know enough to follow instructions to get to where I want to be lol)
Does anyone have any ideas or suggestions? I have a hard time believing there's anything actually wrong with my GPS sensor so to speak especially since it can find satellites it just isn't fixing.
Click to expand...
Click to collapse
i am having the same issue, did you find a fix by any chance?

HateSoul said:
i am having the same issue, did you find a fix by any chance?
Click to expand...
Click to collapse
Sadly nothing seemed to fix it. I did manage to again get a GPS fix but only in some places never the places I did when I first got the phone. It seems like the antenna is just weak all of a sudden. But to be honest I stopped working on it because my Verizon htc 10 was stolen shortly after posting this :/ I've got an Unlocked edition coming next week hoping to test the GPS and see if indeed it was my phone or if the areas I was in are the issue or what.

Messed up TWRP - stuck on decrypting

So, recently, my Magisk stopped working. I thought I fixed it with seveal steps, including updating Magisk and TWRP, and it worked fine at first, but after one of restarts TWRP started requesting encryption password and doesn't boot into system. Entering system pass/pin doesn't let me into TWRP either, it's stuck on "Attempting to decrypt FBE for User 0".
I haven't done anything related to flashing in 1.5 year so I'm kind of lost now. What would be the best way to recover from this without losing any data? I assume some ADB actions, but what do I need to do exactly?

One more note that I thought was irrelevant: I installed Viper in Magisk. Didn't expect such patch could do this, but after some googling I found 2 people having simila issue afte installing that. Please help! Would replacing boot image to MIUI's help in that case?

Try flashing stock boot image then. Google it

That does not help. If it was as easy as googling I'd have it fixed a long time ago. I don't want to lose any data, to remind. But tried flashing original boot.img as it doesn't mes with data and it didn't halp. Any othe ideas?
EDIT: ok, after desperately flashing back both TWRP and boot.img repeatedly and trying to get into TWRP it somehow did something and I got into the system at least to do some fresh backups with Titanium and potentially other apps. I have no clue how to proceed though as I need Magisk to work. Well, the first thing will be to ty to uninstall Viper. But not sure it was the cause in the first place and I'm too afraid to restart. Any clues on what may be the culpit and how to poceed in the safest way?
EDIT2: nvm, ofc I can't really do a full backup using Titanium since Magisk got disabled after flashing original boot.img. Neither uninstall the Viper module. So even more not sure what to do now. Would temporarily disabling the password help?
EDIT3: "google it" type of advice forced me to brick even further as trying to install Magisk/dm-verity now ended up with bootloop. Also, interestingly, older TWRP doesn't have this decyption issue, more info: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1610

"Decryption issue", eh. I bet you are using 12.0.7/12.0.8/12.5.1. Some folk at Xiaomi decides to do a different approach on encryption, rendering encryption issue. This issue has been solved in a newer version of TWRP except for 12.5.1. But do tell me your current MIUI version.
Use MiFlash to flash your CURRENT version of MIUI (or something above or below, I don't care. Just don't downgrade from 12.0.7, you'll face even more headaches) with "Flash all except data" command. Your device will fine, your data will also intact. I've done this dozen of times.
Another piece of advice: don't carry over your magisk module if you're planning to install a stock boot. Install everything freshly.

Destroy666x said:
That does not help. If it was as easy as googling I'd have it fixed a long time ago. I don't want to lose any data, to remind. But tried flashing original boot.img as it doesn't mes with data and it didn't halp. Any othe ideas?
EDIT: ok, after desperately flashing back both TWRP and boot.img repeatedly and trying to get into TWRP it somehow did something and I got into the system at least to do some fresh backups with Titanium and potentially other apps. I have no clue how to proceed though as I need Magisk to work. Well, the first thing will be to ty to uninstall Viper. But not sure it was the cause in the first place and I'm too afraid to restart. Any clues on what may be the culpit and how to poceed in the safest way?
EDIT2: nvm, ofc I can't really do a full backup using Titanium since Magisk got disabled after flashing original boot.img. Neither uninstall the Viper module. So even more not sure what to do now. Would temporarily disabling the password help?
EDIT3: "google it" type of advice forced me to brick even further as trying to install Magisk/dm-verity now ended up with bootloop. Also, interestingly, older TWRP doesn't have this decyption issue, more info: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1610
Click to expand...
Click to collapse
Sorry, I apologize for that

kekesed97 said:
"Decryption issue", eh. I bet you are using 12.0.7/12.0.8/12.5.1. Some folk at Xiaomi decides to do a different approach on encryption, rendering encryption issue. This issue has been solved in a newer version of TWRP except for 12.5.1. But do tell me your current MIUI version.
Use MiFlash to flash your CURRENT version of MIUI (or something above or below, I don't care. Just don't downgrade from 12.0.7, you'll face even more headaches) with "Flash all except data" command. Your device will fine, your data will also intact. I've done this dozen of times.
Another piece of advice: don't carry over your magisk module if you're planning to install a stock boot. Install everything freshly.
Click to expand...
Click to collapse
Thanks for reply. MIUI 11.0.6.0. Thinking about upgrading to 12 but won't that lose data? I read that flashing ROMs in general results in data loss, does flashing current one differ because it's basically the same system? And I guess because of that option. Do I need MiFlash for it or is that also available in any othe tool?
Also, to make sure we undestand data in the same way, by data I mean the following:
- app data, obvious
- app permissions, annoying to set up if lost as I have lots of apps
- notification settings, similarly as above
- other system settings, not as annoying but still some work
Would love to keep all of these.

Destroy666x said:
Thanks for reply. MIUI 11.0.6.0. Thinking about upgrading to 12 but won't that lose data? I read that flashing ROMs in general results in data loss, does flashing current one differ because it's basically the same system? And I guess because of that option. Do I need MiFlash for it or is that also available in any othe tool?
Click to expand...
Click to collapse
Official upgrades won't lose your data (dirty flashable, as the name suggest "update"). In that case, use fastboot upgrade. I will recommend to hold to somewhere in 12.0.5 or 12.0.6, because if you messed up something, you can still downgrade to many versions, maybe up to initial version?
I did many downgrades before because I have tripped AVB many times, something like <newer A10 version available> -> installed magisk and TWRP -> AVB tripped -> <some A9 MIUI via miflash> -> fastboot update via mi flash pro to <same newer A10 version available> -> rinse and repeat until I got a stable system. Without costing any data. But with headaches, indeed.
Mi Flash is also another option. Make sure you choose the "flash_all_except_data". Or else, more unnecessary headaches.
Destroy666x said:
Also, to make sure we undestand data in the same way, by data I mean the following:
- app data, obvious
- app permissions, annoying to set up if lost as I have lots of apps
- notification settings, similarly as above
- other system settings, not as annoying but still some work
Would love to keep all of these.
Click to expand...
Click to collapse
1. App and app data will stay
2. I guess app permission is also stay. But do confirm, since I never had any issue except when I enable/disable MIUI optimizations
3. Personalization will stay

kekesed97 said:
fastboot upgrade
Click to expand...
Click to collapse
Could you be more specific what this exactly means and how to do it without reflashing data? Googling this results in many unrelated to eachother things.
Asking because I had poblems wih Mi Flash before, so would be great to have a reliable alternative just in case.

Destroy666x said:
Could you be more specific what this exactly means and how to do it without reflashing data? Googling this results in many unrelated to eachother things.
Asking because I had poblems wih Mi Flash before, so would be great to have a reliable alternative just in case.
Click to expand...
Click to collapse
Oopsie! Swapped fastboot with recovery rom, ehehe.
Use recovery rom (the 2 gb one). This will require stock boot, stock recovery, mi account, and internet connection. Flashing is done via MiFlash Pro (Just click that "Flash in Recovery" botton or go to recovery tab).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Figure 1: Mi Flash Pro main interface
Or use Mi Flash by loading fastboot rom (the 4gb one) to Mi Flash, and select "flash_all_except_data".
Figure 2: Mi Flash with "flash_all_except_data" enabled

Oh ok, I see, recovery ROM, downloadable easily from MIUI website, is something you upload though recovery and fastboot ROM through fastboot/MiFlash. Found them here https://c.mi.com/oc/miuidownload/detail?guide=2 along with MiFlash 2020 version (is this the latest version?) but how do I find older ROM versions, e.g. my 11.0.6.0? The MIUI website seems to be a total mess, honestly. And I don't trust random Google results, bunch of them seem like virus traps redirecing to Mediafire and similar upload websites.
Is this also the official MiFlash Pro website? https://miflashpro.com/
EDIT: yes, it seems, also found https://xiaomiflashtool.com/ for the other app's latest version

Here for a streamlined versions or here if you need betas
Mi flash is included in mi flash pro if you want all in one solution. It also have miui downloader embedded

Ok thanks. Now I wanted to backup data through older TWRP 3.3.1 that decrypts correctly, just in case, but it fails because it can't copy `/data/misc_ce/10`:
Code:
I:Error adding file '/data/misc_ce/10' to '/external_sd/TWRP/BACKUPS/mfaajbdu5s79pfhy/2021-07-28--04-07-40_PPR1180610011/data.ext4.win007'
Error creating backup.
I:ERROR tarList for thread ID 0
Any clue what this folder is about and how to get around this? Any other way to backup with this level of access?
From what I see it's something about additional user, maybe from the MIUI functionality, but 0 clue if deleting this is safe.

Destroy666x said:
Ok thanks. Now I wanted to backup data through older TWRP 3.3.1 that decrypts correctly, just in case, but it fails because it can't copy `/data/misc_ce/10`:
Code:
I:Error adding file '/data/misc_ce/10' to '/external_sd/TWRP/BACKUPS/mfaajbdu5s79pfhy/2021-07-28--04-07-40_PPR1180610011/data.ext4.win007'
Error creating backup.
I:ERROR tarList for thread ID 0
Any clue what this folder is about and how to get around this? Any other way to backup with this level of access?
From what I see it's something about additional user, maybe from the MIUI functionality, but 0 clue if deleting this is safe.
Click to expand...
Click to collapse
No idea.
SP Flash tools have low level access to your device, including read back in the correct memory region.

kekesed97 said:
No idea.
SP Flash tools have low level access to your device, including read back in the correct memory region.
Click to expand...
Click to collapse
Fixed that: https://forum.xda-developers.com/t/...ils-because-of-data-misc_ce-10-error.4311899/ and have a backup.
Unfortunately, flashing the recovery ROM = still bootloop. Would flashing the fastboot one be any different if I choose to keep data? Would it flash someting extra?
I read that reading these logs may also help with debugging, but not sue what to look for.
Kernel log (/proc/lastkmsg): https://pastebin.com/T2xBBRvi - some error looking lines at the end, but non-comprehensible. Can I use them somehow futher?
dmesg log: https://ghostbin.com/paste/vyBDk - don't really see anything here, but it's quite long and not sure what to look for
logcat: https://ghostbin.com/paste/PSh7f - lots of "avc" errors
EDIT: well, I tried the fastboot one too, recovery got replaced with stock is the only diffeence I noticed, So I guess that means the data is 100% corrupt and the culprit. How would installing Magisk and the dm-verity/forceencypt zip corrupt the data though? Since that's the only thing I did before he bootloop started happening. Does dm-verity/forceencrypt even affect data? I think Magisk does, but this is really weird anyways. Maybe when I tried to install it on the TWRP with broken encryption it caused some file system failure? Does anyone know which /data dirs does the Magisk zip mess with? Maybe deleting those would help
EDIT2: ran Magisk as uninstall.zip in back installed TWRP 3.3.1, which apparently deletes its data files, but nope, didn't do anything.

I'm sorry I don't have the knowledge to go deeper.

G975F TPA (Panama) - can I Factory Reset and go back to Android 11?

Multi CSC Panama (TPA):
Since OTA "upgrade" (or update) to the official Android 12, all I have is trouble with the phone, issues that I didn't have before. I asked about it in this forum, either no one else experiences this or people refuse to answer.
Can I Factory Reset and go back to G975FXXSEFUL1? Anything specific I need to do, order of things, etc? (yes, I know I need to fully backup before).
Thank you.

Nope. It will still be on 12 however if you haven't done a factory reset since the upgrade, do so.
It may straighten it out. There's probably incompatible apps loaded. Don't use SmartSwitch to transfer apps on the reload.
You may be able to reflash it back to 11. A Samsung Experience center can also do it... if they want to.
In the future if you don't want OTA updates, disable it. That's one of the first things I disable.

blackhawk said:
Nope. It will still be on 12 however if you haven't done a factory reset since the upgrade, do so.
It may straighten it out. There's probably incompatible apps loaded. Don't use SmartSwitch to transfer apps on the reload.
You may be able to reflash it back to 11. A Samsung Experience center can also do it... if they want to.
In the future if you don't want OTA updates, disable it. That's one of the first things I disable.
Click to expand...
Click to collapse
Thanks @blackhawk .
So, if I download the 11 image from SamMobile for example, I cannot revert it back to 11 after a factory reset?
If not SmartSwitch, how do you suggest I bring apps back, one by one?
OTA update wasn't done automatically, I clearly could have reject it, I didn't imagine it would cause so many problems, the most serious of which is the phone re-boots out of the blue while I am on a call.

Not sure how to roll it back, sorry. I run stock and been lucky enough to have never had to reflash any of my devices. You're starting to understand why I almost never upgrade. My two N10+'s are still running on what was factory loaded, 9 and 10. No issues.
A reset may sort things out. 12 is causing a lot of cursing from what I'm reading.
If you load the apps from Playstore it should flag any that aren't compatible. For now use the factory loaded versions of the preloaded apps especially system apps. Update those carefully after the reload if at all.

So after a factory reset and another OTA update (right after reset) to G975FXXUEGVA2 - my phone still reboots out of the blue, always in the middle of calls.
My original problem returned quickly, which is while on a call I stop hearing the other party while they hear me loud and clear. I start hearing them again after a minute or so.
Then yesterday 2 days after full reset the crash/reboot problem started again.
I suppose something got screwed up in the phone "radio" or whatever it's called, a hardware issue.
No problems at all with Wifi calling such as WhatsApp audio calls, so it has to be with the cell part of the phone.
Again - it started after updating from 11 to 12.
Can someone weigh in if it's possible to force a downgrade back to official android 11?
Thanks.

sbi1 said:
So after a factory reset and another OTA update (right after reset) to G975FXXUEGVA2 - my phone still reboots out of the blue, always in the middle of calls.
My original problem returned quickly, which is while on a call I stop hearing the other party while they hear me loud and clear. I start hearing them again after a minute or so.
Then yesterday 2 days after full reset the crash/reboot problem started again.
I suppose something got screwed up in the phone "radio" or whatever it's called, a hardware issue.
No problems at all with Wifi calling such as WhatsApp audio calls, so it has to be with the cell part of the phone.
Again - it started after updating from 11 to 12.
Can someone weigh in if it's possible to force a downgrade back to official android 11?
Thanks.
Click to expand...
Click to collapse
Does it happen in safe mode?
If not it's likely an incompatible app.
Otherwise it may be a mobo failure. A rollback to 11 may bypass the damage.
If the bootloader was upgraded too a roll back is possible.

blackhawk said:
Does it happen in safe mode?
If not it's likely an incompatible app.
Otherwise it may be a mobo failure. A rollback to 11 may bypass the damage.
If the bootloader was upgraded too a roll back is possible.
Click to expand...
Click to collapse
I never go to safe mode, don't even know how to
I only loaded a handfull of apps after the reset to try and eliminate the issue. How do I go to safe mode?
Can't tell you anything about the bootloader, how do I check that? The upgrade was done OTA, all official firmware, no rooting or 3rd party stuff.

sbi1 said:
I never go to safe mode, don't even know how to
I only loaded a handfull of apps after the reset to try and eliminate the issue. How do I go to safe mode?
Can't tell you anything about the bootloader, how do I check that? The upgrade was done OTA, all official firmware, no rooting or 3rd party stuff.
Click to expand...
Click to collapse
Google for the safe mode sequence. I rarely use it.
[Guide] How to Read Firmware Information
Hello Members, Today I'm sharing a firmware guide with you in which you can read and know about your Firmware information. Basic Firmware Information Firmware information consists of 3 information. Build version, CSC version, and baseband version. Let's suppose that firmware search result...
r2.community.samsung.com
You can go the same or higher for the significant number in the bootloader but not lower.
In this case it's a 2.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

blackhawk said:
Google for the safe mode sequence. I rarely use it.
[Guide] How to Read Firmware Information
Hello Members, Today I'm sharing a firmware guide with you in which you can read and know about your Firmware information. Basic Firmware Information Firmware information consists of 3 information. Build version, CSC version, and baseband version. Let's suppose that firmware search result...
r2.community.samsung.com
You can go the same or higher for the significant number in the bootloader but not lower.
In this case it's a 2.
View attachment 5544327
Click to expand...
Click to collapse
OK, so these are the four recent versions that I had, old to knew:
Android 11 - G975FXXSEFUJ2
Android 11 - G975FXXSEFUL1
Android 12 - G975FXXUEGULB (problem started with this one)
Android 12 - G975FXXUEGVA4 New update right after the reset.
Am I understanding correctly that E is the bootloader version on all 4?

sbi1 said:
OK, so these are the four recent versions that I had, old to knew:
Android 11 - G975FXXSEFUJ2
Android 11 - G975FXXSEFUL1
Android 12 - G975FXXUEGULB (problem started with this one)
Android 12 - G975FXXUEGVA4 New update right after the reset.
Am I understanding correctly that E is the bootloader version on all 4?
Click to expand...
Click to collapse
I believe so. Apparently they shifted to letters.
Someone else here on a S10 I think it was successfully rollback from 12 to 11.
A safer course might be to let a Samsung Best Buy Experience Center roll it back. They can also do advanced troubleshooting.
I avoid mucking with the firmware and so far haven't had any reason to.
Don't let it OTA updated again as they may update the bootloader and then you're boned...

blackhawk said:
I believe so. Apparently they shifted to letters.
Someone else here on a S10 I think it was successfully rollback from 12 to 11.
A safer course might be to let a Samsung Best Buy Experience Center roll it back. They can also do advanced troubleshooting.
I avoid mucking with the firmware and so far haven't had any reason to.
Don't let it OTA updated again as they may update the bootloader and then you're boned...
Click to expand...
Click to collapse
Well, I am boned either way
Thanks!

You're welcome.
Yeah it sucks. Malware is far easier to deal with than upgrades.

Was able to downgrade it back to 11, no crash yet, however my call issues are still going on (other side can hear me, I cannot hear other side), so it has to be a mobo issue. I installed only a handfull of apps for now but can't see how any of these apps cause it. These are all apps that I've been using before, major banks, WhatsApp, Waze, the minimal things I need. I guess a new phone it is.

sbi1 said:
Was able to downgrade it back to 11, no crash yet, however my call issues are still going on (other side can hear me, I cannot hear other side), so it has to be a mobo issue. I installed only a handfull of apps for now but can't see how any of these apps cause it. These are all apps that I've been using before, major banks, WhatsApp, Waze, the minimal things I need. I guess a new phone it is.
Click to expand...
Click to collapse
Try it in safe mode and do a network reset there, see if that works.

blackhawk said:
Try it in safe mode and do a network reset there, see if that works.
Click to expand...
Click to collapse
I tried safe mode but it doesn't help me because safe mode puts it in Airplane mode and you can't turn mobile data on or make calls.
Also, why would I need network reset if I just did a full factory reset?

sbi1 said:
I tried safe mode but it doesn't help me because safe mode puts it in Airplane mode and you can't turn mobile data on or make calls.
Also, why would I need network reset if I just did a full factory reset?
Click to expand...
Click to collapse
Did you test phone before loading the apps or updating any?
If a 3rd party app screwed it up already again.
WhatsApp I would never install... it only takes one. I doubt it's a hardware failure.

I did not test it. Some of the apps that I installed are needed for work and all of them, including WhatsApp, I have had for years. I am pretty sure it's a hardware failure as well.

You need to be methodical and not make assumptions. 3rd party apps can cause a lot of issues. It's more likely a 3rd party app than a hardware failure but only one way to know which it is. Something changed...

But there were no changes to apps when it started, just an update to android 12. And any recent app that I installed in the days/weeks prior to the update is not on the phone now.

sbi1 said:
But there were no changes to apps when it started, just an update to android 12. And any recent app that I installed in the days/weeks prior to the update is not on the phone now.
Click to expand...
Click to collapse
You need to factory reset and before you install any 3rd party apps see if it's functioning normally.
If you suspect an app is causing the problem uninstall it. This doesn't always work.
Rarely a poorly written app can change settings that aren't user accessible and fail to change them back. A factory reset is the only way to correct this.