Develop Bugs

Help! "wrong UIDs" right after flashing Stock!? and lots of other Problems.

This is a very sad story about my NoteII going bad.
I would describe myself as computer savvy and moderately experienced with Android. I equipped half of the family with various ROM-customized Android phones and am an enthusiastic Note user since it came out in 2011. Until now, I never had to ask a question in the forum.
Let me start in December 2012 when my NoteII arrived. I updated it, then came cwm and the monxdified ROM. For about a month I was a very, very pleased NoteII user.
Then, one day in Mid-January, I installed an app called "(root) Uninstaller pro", which began to auto-backup up all my apps to internal SD in a background process while I didnt notice. I only realized something had gone wrong when apps began to FC because no space was left on sdcard0. I removed the app and all the backups.
From the day after that , Play Store began to "randomly" refuse to update or install apps, because of "Not enough storage space available‎". Which was bull****. I literally had Gigabytes of free space on internal and external storage. For example, Play Store would refuse to update my tiny TB Pro key apk for "Not enough space" reasons but then happily install Asphalt7 and update Titanium Backup and Dolphin for me. Moreover, every affected app also does not install "manually" from apk. When removed, it can not be reinstalled, except via update.zip from the recovery.
Of course, I googled the error. I found no root cause explanation, just a bunch of hints. I deleted all app data from play store and various store-related apps. I deleted and re-setup my Play Store account. The usual suspects, cache and dalvik, got their wipe. Nothing helped. I downloaded the latest monx ROM and updated it from TWRP. Problem still there. Then my job required my full attention so I left the thing running with only partial updates for several weeks. After all, it still worked petty well.
Then, lately, I decided to tackle the issue again. I went to Settings and did a full factory reset WITH internal SD reformat. In TWRP, I did another factory reset and full wipe, then I flashed the latest (DMB2) monx ROM and restored from my TB backup.... "Not enough storage space available‎".
A friend suggested I should try "Fix permissions". Boy, what a bad Idea. From that moment, LBE Security guard caused a Hot Reboot every time I tried to use Active Protection. Many resets and wipes later, it still does today. I can only install it via update.zip, though, not properly reinstall it: "Not enough storage space available‎".
But all this still is only the beginning. I decided it was time to clean up the mess and factory resetted again (no SD wipe this time, after all it didnt help last time), took good old ODIN and completely reflashed with Stock XXDMB2. Result: Boot Loop. TWRP told me "cannout mount /data" and claimed internal and external SD to be empty (which was not the case). So I reverted to cwm6 and did a fullwipe/reset. Only after that, the newly flashed Stock DMB2 suddenly booted. I went on and reinstalled monxdified DMB2 (the very same zip that had worked before!). But regardless of what I tried, all I got was another boot loop.
Back to Odin, Stock again. This time (and every time after) it booted right away without needing help from cwm, BUT on the very first GUI ("choose country") it told me that UIDs were wrong and suggested to reformat /data. Wait, wasnt that what Odin just did? Instantly after this error, com.google.gapps did an FC. CWM to the rescue. This time, "fix permissions" seemed to actually fix them.
To make this long story a bit shorter, I reiterated though quite a number of futile attempts to install a booting custom ROM until 2am, and failed. Now I am on Stock DMB2 with a non-working LBE and only a handful of the most important apps restored. The "Not enough storage space available‎" problem is still here.
I wonder how the "Not enough storage" problem was able to survive so many flashes and resets. I am utterly helpless about how a Stock ROM, flashed from Odin can expose UID problems and FCs on first boot. Could this be a sign of a malfunction on the internal flash storage? If so, how would I be able to find out? Or could it be that this "uninstaller" did something nasty to the secure storage system of JB (which I dont have any idea of how it works and what it needs at all), at a point that all my wipes and flashes did not actually reach?
What else could I do to really, really reset every possible bit on this otherwise wonderful piece of hardware and possibly get rid of all those pesky problems (and back into a Custom ROM)?
Please help me to make this baby shine again!

Re: Help! "wrong UIDs" right after flashing Stock!? and lots of other Problems.
Ive read your story and i feel really bad for you. Good luck m8, if I had some knowledge id help you for sure but im new to android ) goodluck! Dont give up x
Sent from my GT-N7100 using xda premium

Re: Help! "wrong UIDs" right after flashing Stock!? and lots of other Problems.
Do a mega wipe with recovery. Then install stock rom and nothing else. Don't restore stuff. Instead download them from play store.
Sent from my GT-N7100

Re: MegaWipe
UtkarshGupta said:
Do a mega wipe with recovery. Then install stock rom and nothing else. Don't restore stuff. Instead download them from play store.
Click to expand...
Click to collapse
Ok. So I found MegaWipe and put it on my SD-Card. I started it and the aroma Installer presented to me the Mega Wipe Option which I chose. A text screen appeared which said, that several partitions had been wiped but it happened in less than a second which I foudn to be suspicious. Then, when tapping "Next" again in the MegaWipe Aroma Tool, I found out Aroma was frozen and the recovery system did not react to any key press or tap anymore. I had to press the Power button for a while to get back into recovery where I flashed a ROM, then rebooted.
Guess what: all my apps were still present, the SMS history and Launcher fully intact. Dalvik had been wiped apparently (all apps re-optimized), though, and my Wifi AP settings were gone. Of course, the "not enough memory" problem is still here, too!
It appears like whatever problem I have, it also prevents me from using MegaWipe properly. Any more ideas?

Re: Help! "wrong UIDs" right after flashing Stock!? and lots of other Problems.
Try again.
Sent from my GT-N7100

Re: MegaWipe
UtkarshGupta said:
Try again.
Click to expand...
Click to collapse
Tried again. Twice. Internal SD contents were gone. Froze again after "Installation complete". Maybe that "Mega Wipe" took two seconds instead of one this time. The second time I tried flashing Omega after the wipe just for the kicks and that (full wipe Option in Aroma) apparently took my user data away, finally.
To my not-so-big surprise it greeted me with "Inconsistend System UIDs" right after startup, completely with the gapps FC I had already seen with stock so many times, now. This does not feel like real progress.
I have read around a bit. Maybe I should try to flash a multipart ROM in Odin with repartition? Appears to be pretty dangerous, though, and I dont know where to find one that matches my "DBT" CSC properly...

Re: Help! "wrong UIDs" right after flashing Stock!? and lots of other Problems.
Flash latest stock rom for your country.
Sent from my GT-N7100

Flashing stock that wipe ur internal and format sdcard.
Some stock rom dont wipe fully internal thus issue still exist even u flashing stock rom.

Re: Help! "wrong UIDs" right after flashing Stock!? and lots of other Problems.
u use CWM? i had a problem with cwm if i use aroma it always freeze use a other recovery and do the megawipes?? iam not very good at this but i wish you all the luck ..
Sent from my GT-N7100 using xda app-developers app

Re: MegaWipe
UtkarshGupta said:
Flash latest stock rom for your country.
Click to expand...
Click to collapse
XXDMB2 *is* the latest Stock ROM for my country. In my first post I described how I flashed it and it did not work out very well.
nameejokerx said:
Flashing stock that wipe ur internal and format sdcard.
Some stock rom dont wipe fully internal thus issue still exist even u flashing stock rom.
Click to expand...
Click to collapse
Yes, and which one would be such a ROM? I was not very adventurous with ROMS until now and did never flash multipart ROMs. I am afraid bad things could happen if I flash something with wrong CSC. Where exactly should I look for such a ROM and what do I have to take care of? Of course HOWTO pointers are welcome, too.
Sorry if this sounds too clueless but I really dont want to make things even worse.

Maybe SDS
Hi all,
after some more wiping and flashing, fiddling and tiddling and basically reinstalling everything from scratch, mostly without help from Titanium, I got my NoteII back to work. I only restored my most important app data, all apks reloaded from play store instead from backup, made several backups with twrp during this process. Two times, the "no space" problem came back and both times I basically reverted back to the last working backup from twrp. This way, I managed to turn it back into a usable system.
Not for long though, because two hours ago, in the midde of buying an ebook in kindle, my NoteII screen went black and now the whole thing is completely dead. I took out the battery for 10 minutes, but it won't come back on again; not even a download screen or battery loading animation.
So my problems might just have been the harbingers of its future death. I just read that "SDS" also affects some Note2 models and it has something to do with the internal storage which would be sort of a match for the symptoms I experienced. Looks like I'll have to send it in. Because of all the flashing and restoring I had not yet encrypted my internal storage and will have to change all passwords. Duh
I really should have stayed with my trusty old Note1 which never failed on me...

[Q] All 4.1.2 ROMS permanently Encrypted

I have tried everything and I have not been able to find anyone else on this site (in any on the forums) reporting this. I have been trying out 4.2.2 ROMS for a while now...and they are getting pretty good. Especially sense it only officially came out a month ago. But there seems to be a ~bluetooth~ "issue" of some sort in all the ones I have tried (that I liked). I am running Liquid with the latest everything and it rocks! ~But~ it doesn't let my bluetooth sleep, so it drains fast it if I don't turn it off. It is a big enough issue for me to go back to 4.1.2 until they improve these glitches.
That is when I discovered this weird problem. No matter which 4.1.2 ROM I flash or try to recover, I get hit with an encryption password. I am not a very creative guy; I can count all the passwords I have used in the last 20 years on one hand. I have tried every password I can thing of and nothing works. I have tried formatting the entire phone with CWM. I have tried several versions of different custom recovery systems. I cannot install a 4.1.2 ROM nor can I recovery one previously backed up. Today I completely unrooted my phone. Yep, I reversed the whole process, then tried to ODIN the original stock (un-touched, straight out of the box) ROM. Yep, it asked me for encryption code
Where can this be coming from? Why does it only happen with 4.1.2 ROMs? Please help Do I need to replace the SIM card maybe? The SIM card is the only thing I can't format.

Go into your stock recovery and wipe data, factory reset the device....g

You are my hero! I want to kiss and hug you!:highfive: I am in rooted stock now (4.1.2); from here I should be able to get into a 4.1.2 ROM that I like. I wish AxisM was available for N2 ( :
Thank you, Thank you, Thank you!!!
gregsarg said:
Go into your stock recovery and wipe data, factory reset the device....g
Click to expand...
Click to collapse

LOL...
Always welcome my friend....It's no problem...
And of course...happy flashing...
Just remember to use that method when going back to full stock, or rooted stock.
It's the only way to completely clean the device for stock usage...g

Issue with booting on 4.3

Alright, so I am having this weird issue. I thought I found the fix for it several times, however, NO dice.
I've researched for a few hours now, I just don't know if I have over looked it or what. If it has been answered, I apologize.
I looked at the modified recoveries thread for newer s3 devices, but it doesn't seem to fit my area of error.
The Details:
I've been really curious to try some 4.3 roms. Of course, they are for D2SPR. I get them to flash correctly, after a full wipe. The issue happens right after I set everything up in the phone, and reboot. When I reboot I get hung at the splash screen. I have tried to reflash the rom muliple times only to fall flat on the splash screen again. Now, I don't have an SD Card in the phone, except, I left a TW rom in a folder. I use twrp, forgot to mention that. I rewiped the phone and installed that touchwiz rom, and still it wouldn't allow me to get past splash into that tw rom.
So the only way that I could think of to get out of this hole was to flash the rooted LJ7 tar file I have through ODIN. After getting the S3 into download mode, Odin successfully push LJ7 into my phone. Now again, I had an issue getting it to boot. I read somewhere that when this happens, I need to check the Erase NAND option in Odin. So I tried that out and forced LJ7 back on. After successfully flashing, it boots but gets stuck on the boot animation; the fix to that is booting into stock recovery and wiping once more. Then you are able to get into the OS.
I let the phone sit and take the OTAs till I get from LJ7 to MD4 so I re-root the phone using Odin and Chain Fire's root method. Now I am able to flash the recovery (TWRP) using OpenScript through Goo Manager.
I've only tried flashing Illusion and Carbon's 4.3 rom. The second time I used Carbon's rom. Same results. So I have no Idea what the heck is going on. Can anyone explain this to me better or point me into the direction that I need to go?
Thanks much!

your not the only one that has this problem i have the same thing have tried everything and most of the 4.3 roms same thing. no one on xda seems to know at least i havent gotten any help or responses i have just given u on 4.3. good luck finding any ideas.

Set it up I'm sure you restored some apps and data which may no longer be compatible. Or data which is corrupting the 4.3 rom. Try just flashing the rom setting up your Google account and don't add any apps. See if it does it.
Either way this seems to be a common issue across different devices and 4.3 seems it's part of using roms built on leaks and ports. None are bug free. Very similar to all gb leaks back in the day that would go into bootlooping.
Have a great day!

bbrita said:
your not the only one that has this problem i have the same thing have tried everything and most of the 4.3 roms same thing. no one on xda seems to know at least i havent gotten any help or responses i have just given u on 4.3. good luck finding any ideas.
Click to expand...
Click to collapse
Well, it's good to know that I'm not the only one, however, it's horrible that it's happening to others. I appreciate you spreading the info!
edfunkycold said:
Set it up I'm sure you restored some apps and data which may no longer be compatible. Or data which is corrupting the 4.3 rom. Try just flashing the rom setting up your Google account and don't add any apps. See if it does it.
Either way this seems to be a common issue across different devices and 4.3 seems it's part of using roms built on leaks and ports. None are bug free. Very similar to all gb leaks back in the day that would go into bootlooping.
Have a great day!
Click to expand...
Click to collapse
When I go to set up, I just install about 15 apps, I don't restore. I just download them fresh. I had a habit of doing that and it just stuck. I don't restore anything with Titanium or and root backup/restore app. Could one of those apps not be updated then that causes the partitions to get locked up, or just corrupt /data in general? If that's whats happening.
I just find it extremely odd that I (maybe others), can't wipe, and then re flash another rom; actually I can, it just gets stuck at the splash and never goes forward, that is what had me confused most. If I had an sd card, and formatted data itself, would that fly?

thanks Ed i have tried this after the first 2 tries . i dont have any problems installing 4.3 its just after rebooting it gets stuck. Like you said there are always bugs Im fine with using other roms for now. Hopefully when an official 4.3 drops problems will go away

[Q] ROMs Failing, Start Fresh?

Ive tried several ROMs over the years on my ATT GS3. Lately Ive been using the Liquid Smooth ROM. About 4 months after install I started getting screen flashes/colors, random restarts, the phone was getting hot and Ext SD card errors so it was pretty much unusable. Went to try some other ROMs and cant get them to flash. Tried Beanstalk, ProBAM, and Goodness Reborn and they fail immediately. Ive downloaded from different mirrors and the file size is identical. Ive tried flashing from internal and still wont work. Also updated TWRP throughout this process and didnt fix it. The only one that does flash is Synergy but im not a fan of 4.1. Would rather have 4.2/4.3.
Any ideas on why these ROMs arent flashing? Ive tried multiple times.
I dont know the ins and outs all that well but it seems something is corrupted. Would it make sense to odin back to stock/unroot and start fresh? Follow this? http://forum.xda-developers.com/showthread.php?t=2186967
Or is this a fixable issue without going through all that?

Who Am I? said:
Ive tried several ROMs over the years on my ATT GS3. Lately Ive been using the Liquid Smooth ROM. About 4 months after install I started getting screen flashes/colors, random restarts, the phone was getting hot and Ext SD card errors so it was pretty much unusable. Went to try some other ROMs and cant get them to flash. Tried Beanstalk, ProBAM, and Goodness Reborn and they fail immediately. Ive downloaded from different mirrors and the file size is identical. Ive tried flashing from internal and still wont work. Also updated TWRP throughout this process and didnt fix it. The only one that does flash is Synergy but im not a fan of 4.1. Would rather have 4.2/4.3.
Any ideas on why these ROMs arent flashing? Ive tried multiple times.
I dont know the ins and outs all that well but it seems something is corrupted. Would it make sense to odin back to stock/unroot and start fresh? Follow this? http://forum.xda-developers.com/showthread.php?t=2186967
Or is this a fixable issue without going through all that?
Click to expand...
Click to collapse
From what it sounds, it could be a bootloader problem. Did you ever update to 4.1.2? All 4.3 ROMs require at least the 4.1.2 bootloader, which you can get without Odin'ing 4.1.2 from here:
http://forum.xda-developers.com/showthread.php?t=2321310
As always read, read and read. If this doesn't help, I recommend maybe trying out CWM (I'd restore back to your TouchWiz backup since that backups from TWRP and CWM aren't compatible.) If that still doesn't help, then by all means, Odin to stock, OTA to 4.1.2, root and go on. As always, this is just information from one member to another, so I am in no way, shape or form responsible for anything and everything that could go wrong.

The 4.1.2 ota update just came out today so no. I'll try that in the morning thanks!

Who Am I? said:
Ive tried several ROMs over the years on my ATT GS3. Lately Ive been using the Liquid Smooth ROM. About 4 months after install I started getting screen flashes/colors, random restarts, the phone was getting hot and Ext SD card errors so it was pretty much unusable. Went to try some other ROMs and cant get them to flash. Tried Beanstalk, ProBAM, and Goodness Reborn and they fail immediately. Ive downloaded from different mirrors and the file size is identical. Ive tried flashing from internal and still wont work. Also updated TWRP throughout this process and didnt fix it. The only one that does flash is Synergy but im not a fan of 4.1. Would rather have 4.2/4.3.
Any ideas on why these ROMs arent flashing? Ive tried multiple times.
I dont know the ins and outs all that well but it seems something is corrupted. Would it make sense to odin back to stock/unroot and start fresh? Follow this? http://forum.xda-developers.com/showthread.php?t=2186967
Or is this a fixable issue without going through all that?
Click to expand...
Click to collapse
Fail immediately? As in you're able to flash them but can't boot properly or you have glitches?
Sounds like a hardware issue to me. Hope you got warranty.

I click install, select the zip and it starts working for a couple seconds and fails.
Just updated the bootloader and ProBAM and Goodness failed. Tried Beanstalk and it completed fine. Gonna try it out for a bit. It is 4.3 so not sure what the issue it with the other ROMs yet
Beanstalk is up and running. Thanks drx!!

edit

Just dl'd Carbon ROM and CM 10.1.3. Both failed immediately when I used TWRP to flash them. Updated bootloader, updated SuperSU. Should I go back to CWM?
What am I missing? If there are no other ideas is my only option to ODIN back to stock and try again?

Who Am I? said:
Just dl'd Carbon ROM and CM 10.1.3. Both failed immediately when I used TWRP to flash them. Updated bootloader, updated SuperSU. Should I go back to CWM?
What am I missing? If there are no other ideas is my only option to ODIN back to stock and try again?
Click to expand...
Click to collapse
Try Task650's rom. It's the most stable and smooth I've used. Also, he has good instructions on what bootloader to use.
Sent from my SGH-I747 using XDA Premium 4 mobile app

Moved to internal and flashed fine. Rebooting now.
Spent most of yesterday on AirDroid moving files back to my external. Came back and it looks like it killed the battery. Plugged in, rebooted and now my ext sd card wont show up. I bought a 64GB Samsung microcard off Ebay. Formatted on the phone and started tranferring files fine. Was going slow but working. Really dont want to format and start over but the phone wont even see it so I cant format it from the phone.

[Q] Various problems with phone. Completely restore phone?

As of recent, I've been having a ton of stability problems on my S2 across all ROMs. It will often get sluggish and randomly shut down, the WiFi will completely drop and I won't be able to connect unless I restart my entire phone, and various other problems. I've done a full wipe when installing any ROM and problems only came up when I installed cwm 6.0.4.3 and I was wondering if that may have been the issue. Either way, I was wondering if there was a way to completely wipe my phone and bring it all the way back to factory and how it came in the box so I can completely start over to try to fix these problems. Any other suggests would be greatly appreciated, too.
Currently running BeanStalk 4.4+, last "stable" build was with Cyanogenmod 10.1 nightly.
Thank you to everyone in the XDA Developer community, you certainly are amazing and thank you to the developers of the search function, I may not know how to use it to it's greatest potential but it's certainly helped me a TON. This is the first time I've felt I've actually need to make a post for something going wrong, sorry if the problem has happened in the past and I missed a post.

Dude i had a similar problem a while back switching from TWRP to CWM. Somehow I corrupted my Dalvik partition. I couldn't even get back to recovery.
So I went here. Followed the instructions and completely went back to stock.
Quick Note that I don't see mentioned enough, YOU WILL LOSE YOUR APPS AND SETTINGS, (hopefully thy're all backed up with Titanium), BUT YOU WILL NOT LOSE YOUR STUFF ON YOUR INTERNAL OR EXTERNAL SD CARDS. The first time I went back to Stock I was scared s***less because I thought I was losing all my pics.
When I booted up the first time, I got the "repairing" Android Icon, it rebooted and I was back in business.
Then I had previously grabbed the TWRP odin flashable 2.5.0.0. tar file from over here. I got 2.5.0.0 because I planned to flash a 4.2.2 ROM after all is said and done. I flashed that with Odin from Download Mode.
I didn't even bother logging into Google on the stock 4.1.2 ( I just can't go back TouchWiz after Cyanogenmod). I just rebooted right into TWRP 2.5.0.0 manually with Volume up and Power button.
From there I factory wiped everything, then superwiped and cachewiped ( both can be found http://forum.xda-developers.com/showthread.php?t=2235141), just to be on the paranoid side.
And finally I flashed Cl3Kener's latest 4.2.2 version of his BlackLiquid and his latest 4.2.2 stable Uber Kernel. I personally think this is the most stable, and as close to perfect ROM thats going to come out for this phone. Of course that is just my opinion after my own experiences with 4.3, 4.3.1, and 4.4.
This is a completely streamlined version of the complete cluster f** I did researching, trial and error, and starting over, while I was in the middle of actually doing it. One last tip I can give, is to get all the files you think you might possibly need and put then on your external SD if you got it, or internal SD. Its a real pain stopping and starting cause your missing a zip you forgot.
Hope this helps
Huge thanks to the Developers threads I Linked to.