Develop Bugs

CWM Recovery Reboots when wiping /data

I'm having a strange problem with my phone. Earlier today it stopped booting for some reason (Gets to boot animation, then reboots), so I figured something was wrong with my ROM. So, I went into CWM and tried to wipe my phone, but when it got to wiping /data, my phone rebooted. Nothing allows me to format /data, and my phone refuses to boot. I would Odin to stock, but I don't have the files (or know which ones to use as my phone had the bootloader required for newer CM), and I'm worried it may cause more problems. Anyone know how to fix this?
FIXED: So... Yeah, that was weird. The second (and I do repeat, second) time I tried to wipe data with no external sdcard (A suggestion I saw in another thread), data formatted like it was no one's business, and I was able to flash a new ROM to my phone. So, I guess everything is good now.

[Q] UID system Inconsistent- Solved

Hi Forum,
I was running Indie ROM 4.3, v19. I did the 3 wipes and installed Indie ROM, v20. After installation,
I got this message( "UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable."
with a button that stays "I'm Feeling Lucky).
I research XDA , some stated to reflash the ROM using TWRP, and then fix permission. I am using Phil Touch CWM, which has fix permission. However, I still get the same message.
The phone is usable, but certain Google app wont install.
Anyone has an idea how to fix this? Would flashing a ROM from another Dev fix this problem?
Thank you for looking, and then some.... for your helpful suggestion.
OK, I got tired to flashing. Used TWRP to repartition the whole drive. This fixed all the issue.
I solved the problem. I install TWRP, wipes and fix permission. However, TWRP reported that fix permission has failed. I let the phone reboot. ROM start up with out problem. Guess I will be using TWRP from now on.
I spoke to soon. I was not able to install many of Google apps. Reinstall ROM again and now getting the the same message ...UID..
Anyone have any idea?

What does this mean - it's solved, but it ends with a question?

Okay. So I use philz 6.26.6 and never had an issue. I've had UID issue before, but only when dirty flashing roms. A factory reset (in the settings menu) always resolved it.

Probably the cleanest solution HERE

Unfortunately NetworkSystemProvider has stopped (Google Play services)

I just got done taking the PG1 update and things were working fine except TitaniumBackup had the issue with the writing to SD Card. So I did some research and thought that I could modify the
Code:
/system/etc/permissions/platform.xml
, however when I rebooted the phone, I started getting the dreaded "NetworkSystemProvider" and "Google Play Services" stopped errors every few seconds. I have put the file back the way it was, rebooted, cleared cache & dalvik, but still I get the error. I really do NOT want to factory reset if I can help it.
It's frustrating even more-so because I generally run TitaniumBackups nightly and even TWRP backups pretty regularly too. I just hadn't gotten to one of the later, and ironically I was trying to fix the damn SD card write issue so that I could in fact do my TBs!! #FML
This seems like it should be something fixable no? I do have root and TWRP. I just can't find a good site that explains how to do it. I also tried to run the TWRP 'fix permissions' button too to no avail.
Can I just re-ODIN the PG1 or something worse case? And then re-root? ... without a factory reset I mean, so I keep my data and settings as they are?
I really don't understand how things go so jacked up from just changing an .xml file (and putting it back the way it was)??
Please help! Thanks!

Did you make a backup before you started modifying?
Did you try wiping cache and rebooting? Did you have a backup of the file you modified to restore? Check name and permissions?
If neither of the above help, factory reset and Odin again. Make a backup right after TWRP in case this happens again. Marshmallow is tricky and petty sometimes, unlike the earlier Android OS versions.
What you need is a PG1 modified services.jar for custom ROM. Don't recall seeing one shared for PG1. But there is a custom ROM in development forum.
Sent from my SM-N910P using Tapatalk

Crosshatch Issue With ROMs & TWRP. Strange Occurrences

Ok, So Here's The Deal.. The Thing.. The WTF
So I had an older version of the Scorpion ROM installed and working fine for a while and wanted to change it up. I downloaded the newest TWRP. Both image and installer.zip, newest Magisk and RR 7.
I flashed the latest stock and you know, followed all the proper steps and after I flashed RR 7, it wouldn't boot up. (Not the issue) as others have had the same issue with RR 7. I left a post about that on the RR 7 thread and went about reflashing stock and proceeded to find a different ROM to check out.
No matter what I try to flash: Lineage, Scorpion, RR 7, dotOS the same thing happens... Everything flashes like it should, but then it won't boot, AND THEN every time I boot back to TWRP to try something else the haptic feedback vibration thing on the pixel 3 xl goes banana sandwich crazy and won't shut off until I reboot to fastboot to flashall to start over. LOL
And not only that but when I jump back to TWRP to try to flash something else stored on the phone, it says the storage is empty and there are nothing available in the menu. And I couldn't get a screenshot but there were some errors that have popped up in twrp as well...
Could This Be An Issue WITH TWRP itself? Because it does it with every single ROM I have flashed today. It's very strange. I have never ran into any issues like this when flashing ROMs, Kernals, etc.
I'm lost. Any help would be awesomely appreciated.
UPDATE: It now vibrates constantly in TWRP and when I reflashed to factory it did the corrupt software screen so I gave it a good ole' factory rest and then it was is stuck in a loop at the G while conecting and disconnecting to the USB over and over and over... now back to corrupt software screen.
I guess I'm just going to have to reflash Stock and just leave it.
Update 2: Still Give The Corrupt Software Thing After Performing FlashAll - soooooooooooooooo

Slo-mo Designs said:
Ok, So Here's The Deal.. The Thing.. The WTF
Could This Be An Issue WITH TWRP itself? Because it does it with every single ROM I have flashed today. It's very strange. I have never ran into any issues like this when flashing ROMs, Kernals, etc. I'm lost. Any help would be awesomely appreciated.
UPDATE: It now vibrates constantly in TWRP and when I reflashed to factory it did the corrupt software screen so I gave it a good ole' factory rest and then it was is stuck in a loop at the G while conecting and disconnecting to the USB over and over and over... now back to corrupt software screen.
I guess I'm just going to have to reflash Stock and just leave it.
Update 2: Still Give The Corrupt Software Thing After Performing FlashAll - soooooooooooooooo
Click to expand...
Click to collapse
Couple of things. Yes there was an issue with v3.2.3-4 TWRP and the vibrator, but that is separate from your boot issues. Go to the dedicated TWRP thread. As for your updates, 1) an FDR just deletes your data and so would not solve your issue. and 2) Guessing you removed the -w switch from the flash-all script or you would not be getting the corrupt software screen. Run the script again with the wipe switch in place, allowing it to wipe your partitions and start over. You've already deleted all your data with the FDR so it won't matter. Best of luck!

Always late to the party.
v12xke said:
Couple of things. Yes there was an issue with v3.2.3-4 TWRP and the vibrator, but that is separate from your boot issues. Go to the dedicated TWRP thread. As for your updates, 1) an FDR just deletes your data and so would not solve your issue. and 2) Guessing you removed the -w switch from the flash-all script or you would not be getting the corrupt software screen. Run the script again with the wipe switch in place, allowing it to wipe your partitions and start over. You've already deleted all your data with the FDR so it won't matter. Best of luck!
Click to expand...
Click to collapse
So yeah... I just now logged back on and saw your response [I have had notification issues on everything from Reddit to FB since I have had the 3XL]
About the response, I have had the issue with it showing the corrupt software screen a bunch when flashing new stuff. The reason I perform the Factory Slap is because it allows me to enter the menu where I have the option to "Boot from ADB" or whatever it says, sideloading seems to be the only way I can make progress when it starts giving the corrupt error.. The reason I didn't perform the full wipe but I can't remember exactly why now since that was over a month ago.
But I finally got it fixed, and I was going to repost because I had found a way to prevent the vibration thing from happening in TWRP but by the time I got around to posting, the new update had fixed it. Lol

Tinkering with Redmi Note 5, flashing TWRP, trying to enable Camera2, bootloop...

Hello there,
I've recently received my Redmi Note 5 back from warranty service. As much as I like the phone, one thing I always found really disappointing about it is that for whatever reason, it is, as far as I know, the only phone from the Redmi Note series that has Camera2 disabled by default, preventing me from installing GCam. Fortunately, I have found multiple tutorials on how to activate it. Since I've wiped my data before sending it, now was the best time to do some tinkering.
I've used my friend's laptop to unlock its bootloader and install TWRP (it refused to work on my desktop for some reason). the official TWRP web page warned me that the phone uses dm-verity, which is something none of the tutorials mentioned. After some further digging, I found out that should I mess with it, the phone would simply revert any changes, and to prevent this, I needed to flash a dm-verity disabler, such as LazyFlasher
Thinking nothing would go wrong, I decided to try flashing TWRP and deal with the system replacing it with the stock recovery later. All went as planned, and the phone booted into the custom recovery with no issues. It asked me for a password to decrypt the internal storage, which I don't know, so I skipped this step. The first thing I did was creating a backup.
I then tried rebooting, just to see if it would really revert the changes. It did, but it didn't go as smoothly as I had hoped. The system became laggy to the point where it was basically unusable, often freezing for more than 30 seconds after just opening an app. Not knowing what to do, I flashed TWRP back, this time with the dm-verity disabler. A tutorial on how to do this that I found recommended I wipe the cache after flashing the tool. I tried doing that, but the process failed immediately. I rebooted the phone, and the next thing you know, I'm in a bootloop. I've let it sit for a while, but even after some time, the system wouldn't start. Fortunately, I was still able to get back into TWRP.
I restored the backup I created earlier. This, for the most part, solved my issues, the system works fine-ish again (aside from an occasional lag, but it's not nearly as bad as it was) and isn't trying to replace TWRP with the stock recovery anymore, but I'm kinda afraid to tinker with it again. I'd really hate having to buy a new phone just because I bricked the one I have (and I didn't even get to flash the tool that was meant to enable Camera2).
What did I do wrong? Should I've formated the internal storage to gain access to it first? Did flashing TWRP without dm-verity disabled somehow mess up the system? Would flashing a custom ROM bypass having to disable it? I'm confused...