Develop Bugs

System UIDs Inconsistent

So i got this error after doing the update to Virtuous 1.0.2 or w.e the most modern version offered by Rom manager...
phone worked last night, did a restart this am, and thats what came up...
now it says i have to wipe the data part partition or my device will be unstable.
So is this just telling me to do a full wipe? So go into clockwork, re load the virtuous, and do a full wipe while doing it?
is that the easiest way to fix this.... also any idea why this happened?

Don't know why that happened but try fixing permissions. Instructions here
http://wiki.cyanogenmod.com/index.php?title=Fix_permissions

[QUESTION]No Space enough for installation

Hi guy, I got my HTC ONE X "rooted" and with a Custom ROM MaXimus 3.0, but I have tried many others as Revolution HD 9.0.0 and Cyanogen.
My question is: Everytime when I don't like an app, I uninstall it, as usually I do in my PC, well, the problem is, if I want to install it again, it returns an error, "NOT ENOUGH SPACE AVAILABLE" (or something like that) ...well, I tried everything, erase cache partition and delvik cache...in recovery mode and fix permissions...both without success...
Ah...when I go in "Wipe Dalvik Cache" from recovery, it returns e: unknown volume for path [/sd-ext] ...(strange thing hu?!)
I'd like to know if you, more experienced guys have a real solution to this.
Tks a lot!

best option is to reflash the rom
Sent from Mars

hello00 said:
best option is to reflash the rom
Sent from Mars
Click to expand...
Click to collapse
Ths for answering...
Well, it's an option, and that's the way I always treat this problem... but I wanna know if its normal and happens to other people.
Remembering it occurs with all ROMS I've tried. Cyanogen, Revolution and MaXimus.
pt2. Well..I solved the problem this way: I restored to Factory Defaults, kept the same ROM, and installed all apps again, the difference is...now I didn't experimented the issue mentioned above.

Wildfire Random Restarts - please help

Hi all,
I have HTC wildfire for almost a couple of years, recently it started to randomly restart, about 5-8 times a day (the phone is off during the night).
At the time it begun I had OLDWildPuzzleROM_2.2 Froyo v8.0.11 ROM, with HBoot 0.8.
Before the restarts happened I rooted my phone using unrEVOked-3-2-Windoze (it stayed S-Off though).
I don't think the restarts happened right after the root so I'm not sure that is the cause
I few days ago I flashed it with "RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.2 4H_3.35.20.10_release_160191_signed" which changed my HBoot from 0.8 to 1.01.0001. I found the ROM here and followed the instructions.
I had to make a goldcard (I formatted the SD card using the phone and not using the PC).
My phone continues to randomly restart.
We don't have HTC representative in my country, only non official labs that deal with repair, so I can't go to the company for repair. talking to the lab guy he says it is probably a software issue and not a hardware issue, though I don't understand how it is possible since I flashed a completely new ROM. Oh, and the lab guy says he will charge me whether the repair works of fails....
Do you have any suggestions?
Many thanks
PS
I read about boot loop, I'm not sure what boot loop is, but when my phone restarts it shows the HTC logo as it does during power on or full restart.

bootlooping is random restarting or continuous looping of boot.
reasons could be many......
overclocking your cpu to high.
low on memory (too many apps installed / running).
v6 / supercarger / juwwes ram scripts etc etc.
MokeeOs

So that doesn't apply to me
I don't overclock
I have restarts even without installing any apps
I don't know what v6 / supercarger / juwwes ram scripts mean
any ideas of what should I do?
slymobi said:
bootlooping is random restarting or continuous looping of boot.
reasons could be many......
overclocking your cpu to high.
low on memory (too many apps installed / running).
v6 / supercarger / juwwes ram scripts etc etc.
MokeeOs
Click to expand...
Click to collapse

Clonimus said:
So that doesn't apply to me
I don't overclock
I have restarts even without installing any apps
I don't know what v6 / supercarger / juwwes ram scripts mean
any ideas of what should I do?
Click to expand...
Click to collapse
like slymobi already mentioned it could have several reasons - but we've already excluded a few...
Another idea is to start your phone without the sdcard and look if the reboots continue
Important: flashing a different ROM to solve the issue almost doesn't help if you haven't done a complete wipe/factory reset - it has also been reported (not confirmed, though) that Clockworkmod recovery randomly fails with wiping - so it might also help to repeat the procedure.
Probably slymobi will point to a thread where he explains a complete wipe... (you could search in his threads - I'm busy and it's really hot here atm )
I mean: to be sure I always try to format + wipe + factory reset (sound redundant but feels safer...)

eventcom said:
like slymobi already mentioned it could have several reasons - but we've already excluded a few...
Another idea is to start your phone without the sdcard and look if the reboots continue
Important: flashing a different ROM to solve the issue almost doesn't help if you haven't done a complete wipe/factory reset - it has also been reported (not confirmed, though) that Clockworkmod recovery randomly fails with wiping - so it might also help to repeat the procedure.
Probably slymobi will point to a thread where he explains a complete wipe... (you could search in his threads - I'm busy and it's really hot here atm )
I mean: to be sure I always try to format + wipe + factory reset (sound redundant but feels safer...)
Click to expand...
Click to collapse
thank you,
I will try to find a tutorial that illustrates how to do a format and complete wipe, I will appreciate it if someone will have the time to point one, but will look for it myself too.
so I understand you all think it is not a hardware issue.
BTW I did a factory reset on my original ROM before I flashed a new one.

Clonimus said:
thank you,
I will try to find a tutorial that illustrates how to do a format and complete wipe, I will appreciate it if someone will have the time to point one, but will look for it myself too.
so I understand you all think it is not a hardware issue.
BTW I did a factory reset on my original ROM before I flashed a new one.
Click to expand...
Click to collapse
Sorry, couldn't find how to do a system format. can you help?
Does "wipe" as you call it the same as factory reset? if so that I did but no format.

In the recovery go under Mounts and Storage and select Format System.
Technically factory reset is a wipe, it wipes cache, data and sd-ext

Clonimus said:
thank you,
I will try to find a tutorial that illustrates how to do a format and complete wipe, I will appreciate it if someone will have the time to point one, but will look for it myself too.
so I understand you all think it is not a hardware issue.
BTW I did a factory reset on my original ROM before I flashed a new one.
Click to expand...
Click to collapse
There's another thing you might want to check: a lot of people had reboots when they (or the phone) switched on 3G. So do you have reboots, too, with data/3G off?
Furthermore I also know of at least one case where the reboots were caused by a damaged battery - so it might be a hardware issue as well - but in most cases I know of it hasn't been
Re. how to do a clean wipe/format: in this thread I describe my method (sometimes I'll do it different, though) and slymobi describes how he does it (your choice): http://forum.xda-developers.com/showthread.php?t=1833966
Lesicnik1 said:
In the recovery go under Mounts and Storage and select Format System.
Technically factory reset is a wipe, it wipes cache, data and sd-ext
Click to expand...
Click to collapse
yes but as you probably know, sometimes that might just not be clean enough...

reboot into recovery,power off then volume down button and power button at same time,in this menu,using trackball to select,
wipe data / restore factory settings,
wipe cache,
go into advanced and wipe dalvik cache.
press power button to go back.
go into mounts and storage,
format data,
format cache,
format system,
format sdext,
DONT FORMAT SDCARD
you have now wiped your phone clean.
press power button to go back,
install rom from sdcard,navigate to where your rom is on your sdcard and select / confirm,
let it install..........
don't reboot,if gapps are needed?
flash correct gapps in same way as you just flashed rom........
reboot.
MokeeOs

eventcom said:
There's another thing you might want to check: a lot of people had reboots when they (or the phone) switched on 3G. So do you have reboots, too, with data/3G off?
Furthermore I also know of at least one case where the reboots were caused by a damaged battery - so it might be a hardware issue as well - but in most cases I know of it hasn't been
Re. how to do a clean wipe/format: in this thread I describe my method (sometimes I'll do it different, though) and slymobi describes how he does it (your choice): http://forum.xda-developers.com/showthread.php?t=1833966
yes but as you probably know, sometimes that might just not be clean enough...
Click to expand...
Click to collapse
Thank you eventcom,
Actually I didn't think about it but the restarts started a bit after I started using the 3G internet.
If so will the format-wipe-flash procedure will help? this phone suppose to be 3G capable, no?
Many thanks

If the reboots happen because of you enabling 3G I think re-flashing the radio will fix that. (Not so sure on that, someone please complete me)

slymobi said:
reboot into recovery,power off then volume down button and power button at same time,in this menu,using trackball to select,
wipe data / restore factory settings,
wipe cache,
go into advanced and wipe dalvik cache.
press power button to go back.
go into mounts and storage,
format data,
format cache,
format system,
format sdext,
DONT FORMAT SDCARD
you have now wiped your phone clean.
press power button to go back,
install rom from sdcard,navigate to where your rom is on your sdcard and select / confirm,
let it install..........
don't reboot,
flash gapps in same way as you just flashed rom........
reboot.
MokeeOs
Click to expand...
Click to collapse
Thank you slymobi,
but as I wrote above, when I did the RUU thingy I had to do the goldcard procedure and so I formatted my SD card.
Does it have a ROM image after I did the RUU flash?
what is "flash gapps", is it one of the option in the menu? sorry, I'm new to all of this
thank you for your patience and valuable help

gapps is the google apps package.needed for most non sense roms I think
its fine that you have formatted the sdcard at that stage. I meant whenever your performing recovery wipes to be careful not to format sdcard as it does exactly what it says and you will delete all contents of sdcard.
MokeeOs

Lesicnik1 said:
If the reboots happen because of you enabling 3G I think re-flashing the radio will fix that. (Not so sure on that, someone please complete me)
Click to expand...
Click to collapse
can you flash just the radio?

Lesicnik1 said:
If the reboots happen because of you enabling 3G I think re-flashing the radio will fix that. (Not so sure on that, someone please complete me)
Click to expand...
Click to collapse
forgot about this.
yep I think you're correct,if it is the 3g? but what triggered it?
MokeeOs
---------- Post added at 01:36 PM ---------- Previous post was at 01:32 PM ----------
Clonimus said:
can you flash just the radio?
Click to expand...
Click to collapse
lol I knew this was coming next.
yes you can. I'm busy now so hopefully someone will guide you.
if not search forum on how to flash radio etc etc.
MokeeOs

Yes you can.
First download the file I attached and this file: http://www.mediafire.com/?lkhsl6hojm7vplv
Put both on the SD card
Flash the first one in the recovery, this will give you a temporary 2.5.X recovery, that goes away on reboot.
Within that recovery flash the second file I put up (the radio file itself)

Lesicnik1 said:
Yes you can.
First download the file I attached and this file: http://www.mediafire.com/?lkhsl6hojm7vplv
Put both on the SD card
Flash the first one in the recovery, this will give you a temporary 2.5.X recovery, that goes away on reboot.
Within that recoveryond flash the sec file I put up (the radio file itself)
Click to expand...
Click to collapse
I feel so stupid asking this, but how do I 'flash the in the recovery'? I don't know the basics, also the 'Within that recovery and flash the sec file' is a bit esoteric for me
I feel stupid since I am an electronic engineer and working with J-Tag and embedded systems
Thank a lot

Flash them both, just like you flash a ROM
Once you flash the first file a new recovery will pop up, within that one, flash the radio file

Lesicnik1 said:
Flash them both, just like you flash a ROM
Once you flash the first file a new recovery will pop up, within that one, flash the radio file
Click to expand...
Click to collapse
That's my point exactly, I never flashed a ROM on a cell phone
I used the RUU exe, it was as simple as running a windows application.
Do I have to root the device? and mimic a ROM update procedure to do that?
Or wait, is it by using the bootloader menu that comes up when you press down+power on?

lesicnik I would have thought you of all people would give better instructions. Especially after yesterdays pm. lol.
MokeeOs

Unfortunately, app has stopped. [Please help!][LogCat][Reward]

If someone can solve my app issue there will be a reward in the form of a donation! How's that for an incentive?
I understand I posted a similar thread before to this but I wasn't resolved and I am completely out of ideas.
Which ever rom I'm on, which ever kernel, after a random amount of time using my phone an app with crash,
which seems to set off a chain reaction and then all my apps begin crashing.
It's usually google apps that start it, such as messaging, play store or contacts. Apex launcher also often gets affected.
Killing all apps and restarting the phone occasionaly fixes the problem for a little while.
I have used different kernels, used different android builds, factory reset the phone, wiped the sd card, cleared cache etc etc. Is this a hardware issue?
Things that might be worth knowing
When entering bootloader I get the following error messages:
Code:
Sd Checking...
Failed to open usb master mode
[COLOR="Red"][Preload] failed to open usb master mode[/COLOR]
[COLOR="Blue"]loading PJ46IMG.zip image...[/COLOR]
Failed to open usb master mode
[COLOR="blue"]Please plug off USB[/COLOR]
I can not save images, in other words it seems I cannot write to the SD card, looking in mounts and storage in CWM
reads:
Code:
unmount /cache
mount /data
mount /sdcard
mount /system
format /cache
format /data
format /sdcard
format /system
format /system
mount USB storage
Which implies that everything is unmounted? Surely this can't be right and this is why I cant write to SD? Mounting them fixes the writing to SD problem temporarily.
When I get problems occuring next time I'll try to capture screenshots. I really hope someone has an idea what's going on here, if it's hardware I guess I'm screwed as the phone is out of warranty? :S
I have attached logcat's from around when the crashing happened last time, maybe someone can skim through them and identify the issue? Thanks

did you try different gapps???

I've tried lots of different gapps, the miui Rom im using now came with gapps as well

Both of your observations are normal, no problem there.
App force closing does not relate to kernel.
You should make a logcat when the apps start crashing so someone can assist you in diagnosing the issue. (Google it if you don't know how)
Also try re-download the ROM, possibly could be corrupted ROMs that you flashed.

tomascus said:
Both of your observations are normal, no problem there.
App force closing does not relate to kernel.
You should make a logcat when the apps start crashing so someone can assist you in diagnosing the issue. (Google it if you don't know how)
Also try re-download the ROM, possibly could be corrupted ROMs that you flashed.
Click to expand...
Click to collapse
Ok I'll make a logcat now, cheers bud. And I have tried with multiple different roms so it seems unlikely its a download issue

Heres the files. It took me ages to get any results, its typical when you want it to crash, it doesn't! Can someone more tech savvy then me have a thumb through them and try to identify the issue? Thank you very much
I think there is errors in both the logs but more in the second!

Now offering a reward for some help leading me to resolving this issue

bump

Taking a look, check back tomorrow.
Sent from my HTC One X using xda app-developers app

hahhahhaaa said:
Taking a look, check back tomorrow.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Cheers man, really appreciate it!
If it helps, my hunch (baring in mind I'm not that savvy with this) is something to do with partitions unmounting themselves? when looking in CWM
sometimes they are mounted sometimes they aren't

That error in the bootloader is common for all phones, simply unplug the USB and replug it in.
The USB not mounting is caused by old CWM versions, here is the latest.
About the second problem, it seems you are using custom ROMS and the problem started by the SQL management (i would eliminate hardware as a cause)
But please inform me which Rom you are intending to use so I can confirm the procedure, and whether its Sense/Sense+/AOSP.
For now, try the following:
- Re-Install the Rom with SQL tweaks ON,EXT4 tweak, and FORCED GPU rendering OFF.(if options available)
- DON'T restore anything from the system partition

Are you using the latest CWM recovery v5.8.4.0?
The error you get in bootloader has nothing to do with apps crashing and is totally normal. Even I get the same error.
And like the guy above me told, the FC's are caused by SQlite trying to write to readonly databases.
Similar problems to this have been fixed by wiping phone. Have you restored app using e.g. titanium backup?
And also, try formatting sd-card using pc, not recovery.

Vcek said:
That error in the bootloader is common for all phones, simply unplug the USB and replug it in.
The USB not mounting is caused by old CWM versions, here is the latest.
About the second problem, it seems you are using custom ROMS and the problem started by the SQL management (i would eliminate hardware as a cause)
But please inform me which Rom you are intending to use so I can confirm the procedure, and whether its Sense/Sense+/AOSP.
For now, try the following:
- Re-Install the Rom with SQL tweaks ON,EXT4 tweak, and FORCED GPU rendering OFF.(if options available)
- DON'T restore anything from the system partition
Click to expand...
Click to collapse
I am using the most up to date version of CWM 5.8.4.0
What exactly is SQLite anyway?
Currently I'm using ADRH The ICS version, in the instilation I checked all the tweaks so I expect the EXT 4 tweak was on.
What do you mean about restoring from the system partition? I don't restore anything and still get the problems.
hahhahhaaa said:
Are you using the latest CWM recovery v5.8.4.0?
The error you get in bootloader has nothing to do with apps crashing and is totally normal. Even I get the same error.
And like the guy above me told, the FC's are caused by SQlite trying to write to readonly databases.
Similar problems to this have been fixed by wiping phone. Have you restored app using e.g. titanium backup?
And also, try formatting sd-card using pc, not recovery.
Click to expand...
Click to collapse
I have wiped using - Factory reset (bootloader), factory reset (CWM and factory reset in the phone (running sense)
And nope I left titanium backup alone. Do you mean as in mount storage and format in windows, FAT32?

[★] said:
I am using the most up to date version of CWM 5.8.4.0
What exactly is SQLite anyway?
Currently I'm using ADRH The ICS version, in the instilation I checked all the tweaks so I expect the EXT 4 tweak was on.
What do you mean about restoring from the system partition? I don't restore anything and still get the problems.
I have wiped using - Factory reset (bootloader), factory reset (CWM and factory reset in the phone (running sense)
And nope I left titanium backup alone. Do you mean as in mount storage and format in windows, FAT32?
Click to expand...
Click to collapse
Don't ever wipe from the bootloader if on custom roms/recovery.
Don't check all the tweaks, especially the force gpu rendering, this one is known well for causing FCs.
Sent from my EndeavorU

Unfortunately, i am still having the same problems that you are, and still cant seem to get my phone to boot, but i am on the latest Hboot 1.31 but still getting all the same apps crashing as you are
I am hoping for a potential Jelly bean RUU to released maybe?

try running in safe mode and see if a 3rd party app is causing this. Hold the turn off option in the power menu.

Vcek said:
Don't ever wipe from the bootloader if on custom roms/recovery.
Don't check all the tweaks, especially the force gpu rendering, this one is known well for causing FCs.
Sent from my EndeavorU
Click to expand...
Click to collapse
Alright I'll remember that next time haha! How come anyway?
Installed again, no tweaks, stripped it down with rom cleaner, disabled gps services and haven't (yet) synced my google account just to be safe, we will see what happens
Stuar said:
Unfortunately, i am still having the same problems that you are, and still cant seem to get my phone to boot, but i am on the latest Hboot 1.31 but still getting all the same apps crashing as you are
I am hoping for a potential Jelly bean RUU to released maybe?
Click to expand...
Click to collapse
It's a real pain isn't it! Yeah man the sooner the new RUU (1.28 first please!) come out the better.
Vcek said:
try running in safe mode and see if a 3rd party app is causing this. Hold the turn off option in the power menu.
Click to expand...
Click to collapse
I get this error before installing any apps usually so I dont think 3rd party apps have the chance to cause trouble

First problem which I have had before on a sense rom, Pressing the send button on a message does nothing. This usually leads to apps beginning to crash
Followed by a random screen 'turn off' and phone reboot followed by being stuck in splash screen
..Yep, still getting crashed. Can I reformat the whole memory? What would be the best way to go about this?

[★] said:
First problem which I have had before on a sense rom, Pressing the send button on a message does nothing. This usually leads to apps beginning to crash
Followed by a random screen 'turn off' and phone reboot followed by being stuck in splash screen
..Yep, still getting crashed. Can I reformat the whole memory? What would be the best way to go about this?
Click to expand...
Click to collapse
You could reflash the RUU file to get your phone back to stock and work from there. --this rewrites all partitions
You need to downloading it (there's a thread in android development listing them all), relock your bootloader, and run it as administrator from windows.

peedub said:
You could reflash the RUU file to get your phone back to stock and work from there. --this rewrites all partitions
You need to downloading it (there's a thread in android development listing them all), relock your bootloader, and run it as administrator from windows.
Click to expand...
Click to collapse
would this work for someone on jelly bean?

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...