Database Develop

[PRJ] Linux and Android for CDMA Diamond (DIAM500)

Android 2.0 (Eclair) for CDMA Diamond (DIAM500)
Instructions
Put the files from my zip file (zImage, modules, startup.txt) in the root of your Internal Storage
From this xda post, download the latest XDANDROID build.
From the XDANDROID 7z file, extract system.sqsh, haret.exe, initrd.gz, calibration, conf/, media/, and (optionally) AndroidApps/ into the root of your Internal Storage
From stinebd's rootfs autobuild site, download the latest rootfs, rename it to rootfs.img, and put it in the root of your Internal Storage.
If you are updating from an earlier version of Android or just want to clear your settings, you can delete data.img from the root of Internal Storage.
Run haret.exe and boot
Notes
Touchscreen calibration values are stored in the ts-calibration file in the root of Internal Storage. To re-calibrate, delete the file and restart.
The "end call" button takes the phone in and out of sleep.
Android's "Menu" button is mapped to the top-left/Home button. The 5-way pad and the scroll ring both work.
Android's "Home" button is mapped to the power button on top of the phone.
Wi-Fi is working, although Linux sometimes crashes when WiFi is turned off.
If you want to try Android 1.6: From this Android build, extract haret.exe, initrd.gz, system.sqsh, calibration, calibration_diamond, and the AndroidApps/, conf/ and media/ directories into the root of your Internal Storage.
ChangeLog
3-23-2010:
Touchscreen double-tap issue should be gone, big thanks to eval- and especially bzo
HTC wired headset and 3.5mm headphones both work
3-8-2010:
Hardware 3D is re-enabled (accidentally disabled it)
3-6-2010 Update:
Bluetooth now works, big thanks to bzo
Touchscreen should be improved
Power-off now resets the phone instead of crashing
2-25-2010 Update:
When WiFi is turned off the phone shouldn't crash
2-19-2010 Update:
Power collapse now works, so power consumption should be much lower when the screen is turned off.
WiFi should work, as long as you use a new rootfs from stinebd's autobuild site. If you tried to use WiFi in the last ~2 weeks and it failed, WiFi still may not work with this new rootfs and kernel. See this post for solutions.
2-17-2010 Update:
Microphone works without having to make a call in WinMo
WiFi still isn't working, but I'll post a patched rootfs soon to fix it
2-10-2010 Update:
Hardware 3D acceleration is working under Eclair
Brought in makkonen's fixes for battery status--they're rough, but better than being stuck at 5% all the time
WiFi is not working at the moment, but I'll lean on the XDANDROID guys to get my fix in.
2-3-2010 Update:
Linux is now using much more of the phone's memory: 180MB vs. 103MB, thanks to some patches from the Hero and Droid Eris kernel source.
Touchscreen calibration is now supported with the Feb. 2 XDANDROID build, thanks to makkonen and phh.
1-27-2010 Update:
Stability should be much improved
A new touchscreen driver is included that is a big improvement over the old one, thanks to makkonen and phh. A calibration utility is coming soon. Until then, calibration is stored at the bottom of conf/eclair.user.conf, and you can put your WinMo calibration in there with this guide.
The USB product ID has been changed in the hope that ADB will work on Windows. Try it out and post back if it works.
1-22-2010 Update:
The power button (on top of the phone) is now mapped to Home, and holding it down will show apps running in the background
Sound, data, and WiFi should all be working
1-11-2010 Update:
Tested and working with Eclair
Deep sleep should be working better (use less power)
12-26-2009 Update:
Kernel improvements:
The speaker and earpiece now work (but not the microphone)
Screen backlight control works
Rootfs improvements:
Thanks to makkonen's RIL fix, cell data works in Android without having to end the connection in WinMo first
I made a change to /init that might help mjb94, hackman238 and others that have partitioned internal storage. If you were getting a "cannot mount" error on boot, let me know if this fixes it.
12-16-2009 Post
We do have a Google wave for Android--right now it's a cross between a wiki-status-report and chat room. I'm not sure how to give a link to a wave, but it's open to everyone and called "Android on HTC Windows Mobile Phones (Diamond, Raphael, Blackstone, Rhodium, Topaz)". If anyone wants a wave invite, PM me and I have a few to give out.
Enjoy Android, and if you need help or have questions, PM me or post here
Donations are greatly appreciated , or help finding an engineering job in San Diego!

thanks mr. pippy for all your work. my wife is happy that once the microphone works i wont want to buy a new phone!

wow
you are definately making progress on the diamonds android

Is there any chance of the mic working anytime soon? I know this isn't an fast paced process but I'm just so sick of wm.

Can someone invite me to Google Wave please?
my gmail account is mike.cgy

bdusmc said:
Can someone invite me to Google Wave please?
my gmail account is mike.cgy
Click to expand...
Click to collapse
I just sent you one.

Awesome - I got it... Thanks a lot!

Wow, you're getting a lot done in a short period of time, Thanks!
Will donate as soon as I can!

the boot stops on
"handhover: boot [htc_fb-1] -> real [ttyo]"

For the latest version, it will boot for me, but as soon as I have a 3g connection it seems to reboot any time I touch anything.

Boots up fine
Latest build boots up and seems to run fine for several hours but after playing with it, it seems to get more and more unstable. I went 10 hours with it plugged in sleeping and then unplugged it and used it moderately for about 3 hours before it crashed. Now it's crashed 3 times within minutes of each other. Good stuff though, can't wait until it's stable enough to use full time. Diamond has plenty of nuts to run it pretty good. Sure would be nice to have a dual boot phone. No reason to upgrade and get the best of both worlds...

giovesoft said:
the boot stops on
"handhover: boot [htc_fb-1] -> real [ttyo]"
Click to expand...
Click to collapse
I get the same error on my Raph500. I tried from the micro SD card and from the root of the fs.

giovesoft said:
the boot stops on
"handhover: boot [htc_fb-1] -> real [ttyo]"
Click to expand...
Click to collapse
rothgar said:
I get the same error on my Raph500. I tried from the micro SD card and from the root of the fs.
Click to expand...
Click to collapse
Sorry, my kernels are only tested on DIAM500. The RAPH500 mtype (set in startup.txt) is 2182, you should have better luck with that. Also, this thread is for RAPH800 but there may be some RAPH500 people there.

mr pippy i still get the same error as in your other post with the failed to mount sd and the 2 partions, i tried reformatting

mjb94 said:
mr pippy i still get the same error as in your other post with the failed to mount sd and the 2 partions, i tried reformatting
Click to expand...
Click to collapse
Did you reformat or repartition? Would you happen to be one of those people who has a partitioned card? Basically, I think the layout of your MC can have as many partitions as you want on it as long as mmcblkp1 (the first partition) is a fat32 partition with the needed files on it. There's also a little info on this problem on the wiki, lavender.t posted a solution that works 100% of the time if you're able to enter keystrokes.

Willis111 said:
Did you reformat or repartition? Would you happen to be one of those people who has a partitioned card? Basically, I think the layout of your MC can have as many partitions as you want on it as long as mmcblkp1 (the first partition) is a fat32 partition with the needed files on it. There's also a little info on this problem on the wiki, lavender.t posted a solution that works 100% of the time if you're able to enter keystrokes.
Click to expand...
Click to collapse
I simply in disk utility clicked on restore and erased the disk restoring with ms-dos fat
is there another way to do this. i have access to linux and osx not windows
it only shows i have one partition so idk!
no dice. heres what i have done
ok i restore the disk in to ms-dos fat
no dice
i repartiton with a scheme of one partition
no dice
i change the partiton table no dice
i tried lavaders thing but i couldn't get the keyboard to come up

there is a new android version called eclair 2.0 here http://forum.xda-developers.com/showthread.php?t=601751 .

i also formatted from the phone

Possible fix for microphone
I haven't tested this yet, but blast3r in irc tested a workaround for the microphone this morning and said it worked:
In WinMo, start a voice call and leave it connected while you open HaRET and boot into Linux. In Android, the microphone should now work for voice calls.

MrPippy said:
I haven't tested this yet, but blast3r in irc tested a workaround for the microphone this morning and said it worked:
In WinMo, start a voice call and leave it connected while you open HaRET and boot into Linux. In Android, the microphone should now work for voice calls.
Click to expand...
Click to collapse
Yep, confirmed for me. Made a phone call with android and could talk just fine. Probably can just call voice mail with win mobile and launch HaRET. Trying that right now.

[Q] Help recovering data from Capy with mashed screen

I could use the help of you gurus trying to get some data off my phone since I sat on it yesterday and horribly mangled the screen. The screen wont come on but it sounds like the phone is still working. The screen also doesnt respond to touching it not surprisingly
Really all I want to do is get my texts off of the thing, but with the screen not working, and ADB seeming to be disabled, im not sure how to go about that.
Is there any way for me to:
A) Remotely enable ADB(im guessing no)
B) Remotely enable Wifi(so I can use an app that is already on my phone to control it from my computer)
Any help is appreciated!
BB

If you had a custom kernel on the phone before it broke there is an option in clockwork to restart adb you would just use up down vol buttons and power buttons. I will give you a Button sequence in a minute. Just gotta reboot my phone
[Edit ]
I just rebooted my phone and the dark core kernel does not have the option to restart but I do know some kernels do post what you are tuning and maybe someone else knows. Also there is the TV OUT option just plug into your tv and see if you don't get a picture maybe its on by default. Good luck(;~}
Sent from my phone on vacation

Thanks for the reply! I was unaware you could restart ADB from CWM. I am running Serendipity VII with the most up to date Serendipity kernel I will try to find out if they support it(if anyone reading this can look in CWM and give me the key sequence that would be so awesome)
http://forum.xda-developers.com/showthread.php?t=1107894
I thought about the TV out option but I would still be unable to input anything from the touchscreen so would be a bit limited with what I can do
Thanks for the assist!
BB

Baconbreath said:
Thanks for the reply! I was unaware you could restart ADB from CWM. I am running Serendipity VII with the most up to date Serendipity kernel I will try to find out if they support it(if anyone reading this can look in CWM and give me the key sequence that would be so awesome)
http://forum.xda-developers.com/showthread.php?t=1107894
I thought about the TV out option but I would still be unable to input anything from the touchscreen so would be a bit limited with what I can do
Thanks for the assist!
BB
Click to expand...
Click to collapse
The only thing I can think of, if find out where the texts live, ADB into the phone and pull them to your PC.
I use SMS Backup app, but if you don't already have it, it won't do you any good at this point.
You know, Maybe what you can try is a nandroid backup from ADB. You may be able to save the entire ROM and contents, then pull it from your device to your PC.

Also the key sequence for mount usb in recovery might be useful but you don't get access to system only the sd card.
Sent from my phone on vacation

That would be really helpful key combo too to get some photos off of it..and maybe Tibu backed up apps. Mental note: use google+ cloud storage for photos and video in the future
BB

I gave up on this for a while....but tonight I decided to give it a go again with results! Posting steps here in case someone else runs into this...
I took the phone full apart to see if there was any damage internally besides the mashed screen and I couldnt find any. Put it back together and oddly ADB started working!
After much searching...I was able to find this solution:
http://androidcommunity.com/forums/...s-storage-through-the-recovery-console-19999/
for a step by step, all I did was :
Adb root
Adb reboot recovery
Running:
ADb devices
Showed:
List of devices attached
32326B102E3E00EC recovery
then run:
adb shell
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
and the SD card became mountable and I was able to rescue my stranded data
BB

[Q] S3 LTE I9305 - Unable to boot, corrupt OS? and data recovery

Hi all,
I hope you can help as something very strange and unusual has happened to my Galaxy S3 LTE i9305 (on Orange in UK). Samsung technical support tell me they've not heard of the issue before as do the official repair shop. I have never installed any unusual software or tried to access the internals etc.
On Sat 26th Oct, in the evening, the phone was connected via USB to my laptop charging. There was no data transfer taking place, and the laptop was idle. The phone was not in use, nor was I nearby but randomly it showed the Samsung splash screen logo - it looked a little weird as it was pure black but with random speckles of coloured dots (which made it look like a Galaxy - I thought perhaps I hadn't noticed it before). I was unable to reset so took the battery out and replaced. It did the same thing and then on the second time of removing hte battery the screen became completely white with black marks generating a fuzzy effect - it's been like this ever since.
I get the white fuzzy screen if attempting to turn the phone on, or attempting to recovery mode, however if going to the install option (which I assume happens before Android boots), the screen is absolutely fine and proves not to be at fault. I should add the screen is cracked slightly, it has been since April and is not the cause of this random error.
Tech support tell me that they'll happily accept it back but ultimately, they will wipe the phone and send back as reconditioned. I've tried to connect via Kies, device not found - nor is it when connected to a computer - infact the computer tries to 'install device drivers'.
I'm sure everyone says this however I am an organiser of a large local festival in the UK and the phone has some very important detail storesd in the ColourNote app which I need to access - also the contacts appear not to have synced with GMail since May.... I'm desperate to access these files, for money too potentially, but cannot afford to go down the simple, wipe and reformat easy option. Can you help? Do you know any software that can access data from the internal memory card (note I've removed the external card which contained the photos) How about once the phone has been wiped, to try and see if anything can be recovered then.
Would really appreciate your support, this developer community is my last option and you're normally so awesome, as can't find any reference to the problem online.

Is your colour note app not synced ??
You can try RECUVA data recover.
You need to read the faqs and guides first .
Including the one that covers storage and recovery ..
Samsung reject warranty on phones that have damaged screen .

JJEgan said:
Is your colour note app not synced ??
You can try RECUVA data recover.
You need to read the faqs and guides first .
Including the one that covers storage and recovery ..
Samsung reject warranty on phones that have damaged screen .
Click to expand...
Click to collapse
Hi,
....no I had never set it up. So ironic that was on the to do list in the app.
I'll look into Recuva, is that for before or after I send it off. Is there much chance do you think?
Yes, sorry. I meant to say I also have phone insurance which covers the screen so will have it off to them first, and then onto Samsung - ie 2 places of data wiping!
Thanks for your reply though,
Kind of hoping I may just be able to fix the problem, even if only temporary, but realise it's unlikely

s_boddy said:
Kind of hoping I may just be able to fix the problem, even if only temporary, but realise it's unlikely
Click to expand...
Click to collapse
Hi mate,
You can try flashing just the system (and boot) images if you think it's a software issue.
That way your data partition will be intact.
Instructions:
Step 1) Download the Stock ROM you want to use
Step 2) Rename the file from .tar.md5 to just .tar
Step 3) Open the .tar with WinRAR or something similar
Step 4) Extract: system.img (and boot.img if you want the Kernel)
Step 5) Create ODIN file from .img files http://forum.xda-developers.com/showthread.php?t=1484304
Step 6) Flash the new ODIN file to restore your firmware to Stock!
On Windows you can use Cygwin to run these commands if you don't have access to Linux.
NOTE 1: That guide uses recovery.img as an example but you can replace that text with system.img on the first line.
NOTE 2: If you are adding more than one file (eg. system.img & boot.img) simply list them one after the other with a space between each file.
NOTE 3: Do not include data.img, it WILL wipe your data! Do not include cache.img, hidden.img, these MAY wipe your data!
Best of luck, I hope this helps you out :fingers-crossed:
Have a great day!
-Shaz

So, here’s how you can recover data from a Soft-Bricked Android smartphone:
1. Once you’ve installed a custom recovery on your device, open it using the specific method for your device. E.g for Samsung you can turn off the device completely, then turn it on by pressing and holding Volume Up + Home + Power Key and you will be able to access the recovery. These methods vary for different devices.
2. Once in CWM or TWRP Recovery you will find a number of options.
For CWM Recovery, select “Mounts & Storage > Yes”.
In Mounts and Storage menu you will find some more options, from the list select “Mount USB Storage or the option depending upon your choice.”.
Now connect your phone to your PC using the data cable.
As soon as you connect your phone to your PC, the USB Storage / Internal Storage will open up in folder view.
You can copy all of your files to your PC now.
3. For TWRP Recovery, Select “Mount > USB Storage”.
Connect your phone to your PC and it will open up the USB / Internal Storage.
3. Copy your desired files.
That’s all! You can easily recovery all of your data stored on the internal storage of your Android device.

[Q] Can not ADB my device?!

I have a Verizon Galaxy Tab 7 (SCH-I800) and I can not link up to it in ADB.
I have installed the Android Development Kit, Samsung drivers, and downloaded CM10.1.
I was able to contact the tablet in command prompt through heimdall and push clockworkmod recovery.
I'm following this guide:
http://rootzwiki.com/topic/33743-ext...rd-only-guide/
I've removed the internal memory card.
I've modified the update.sh file and rezipped everything.
I just need to know WHY adb cannot find my device. When I type "adb devices" in the command line NOTHING shows up. I've tried reinstalling the samsung driver, reinstalling the driver that came with heimdall, and updating the samsung driver via windows update.
By the way, this device would bootloop at the verizon loading screen, could not be updated, and could not load its original android OS, therefore I cannot turn on debugging or anything like that. Alls I can do is access the "PC connection" yellow screen and the CWM bootloader I pushed with Heimdall.

By "Internal" Memory ya meant "External" Memory right? as the Internal Memory is the 16GB Flash ROM.
In any case all pedantry aside. Did you remember to check the USB Debug Setting?
I think you can find this under the Wi-Fi Settings (On the Samsung Stock ROMs), IIRC it should be near the "Samsung Kies / Media Player / USB Storage" Settings. On CM10 Builds you'll find it in the "Developer Settings" near the bottom of the List.
Pretty sure you have to check this "Flag" before you can use ADB on your Device...
In that case consider yourself bricked!
In this case I'd recommend you find the Overcome Recovery Package: HERE
Install such Driver that you may need, then fire up Odin3 v1.7
Then set your Device into Download Mode (e.g. Hold Volume Rocker down + Power till you enter the Download Mode Screen)
Pit -> gt-p1000_mr.pit
PDA -> GB_Stock_Safe_v5.tar
Phone -> modem.bin**
Most People would just use the XXJPZ (GSM modem.bin), here but, since you have a CDMA Phablet, you'll have to find and pick the correct modem.bin File that is the best match for your CDMA Device. This is also likely why your now soft-bricked.
Hopefully after all this rigamarole you'll land up on a Stock, non-branded Samsung Gingerbread 2.3.3 ROM.
To which I would just download This, and that should give you Root.
Without all that tedious mucking about with ADB.

The internal chip has failed. I cannot boot the device whatsoever. I removed it as the link states. Therefore i cannot check off debug mode on the tablet. I will try your suggested method and report back

Don't look at Overcome method if you have a CDMA tab.
It will only brick your tab if it ever worked at all.
Regarding bad internal memory, there are two chips. The OneNand 512MB and the MoviNAND 16GB.
If your OneNAND is the one broken, removing the MoviNAND achieved nothing.
The bootloader, modem, (and is it /system too of stock rom?) sits on OneNAND.

If you look at the link I posted, my tablet was doing the same exact thing as pictured in the link. Saying it could not mount any files or anything. No matter what I did, it would just get to the verizon loading screen and keep flashing "verizon".
I haven't tried the "overcome" method as it didn't really seem like it'd work.
I want to ADB my device to push the new ROM to it. I've already formatted the SDcard as suggested in the guide. Since clearly no one is clicking the link and reading the guide, I'll post it:
Summary:
- Open up the device and take internal SD Card out.
- Re-assemble the device.
- Partition the external SD Card (3 partitions, two small ext4 and one big FAT32)
- Modify ICS or later ROM's update.sh to use partition 3 as external SD Card.
- Flash modded ROM via CWM (and Google Apps optional).
- Enjoy
Taking it appart:
Don't panic!, if you can use a screwdriver and build with Legos you are qualified to do this!
iFixit does a wonderful job of showcasing how to open the device up that I rather link to them than try to out-do them.
Follow their guide until step 13 then refer back to this guide. http://www.ifixit.co...Teardown/4103/1
Posted Image
To actually remove the Internal SD Card (that is not soldered to the board but in-fact glued to it), I recommend you take an exacto knife (or other small blade or thin screwdriver) and slide it around the edges gently; once the edges are loose, take your screwdriver under the chip and just pop it up.
Posted Image
There will be adhesive residue on the board, I recommend using some gentle solvent to remove it (I used a cloth with a little paint thinner).
Put everything back together (just follow the iFixit guide on reverse) and feel proud that you are done with the hardware mod.
Partition your external SD Card
I used three partitions (all primary, not logical) , two 500 MB ext4 and a FAT32 with the rest of the space.
Linux users will probably not require much help on deciding what software to use, but for Windows users MiniTool Partition Wizard does a good enough job.
Do note that your device will perform according to your external SD Card, so it's not a bad idea to invest in a category 10 SD Card.
Modifing the ROM:
Download your ICS / JB ROM of choice, unzip it and open update.sh
Edit both line 31 and 35 to be as bellow
SD_PART='/dev/block/mmcblk0p3'Save and zip back.
Loading the Modded ROM to the SD:
Because we messed with the SD Cards, CWM will have a bit of trouble finding the external SD Card (until we flash our ROM).
Go ahead and connect your device to your computer and ADB the following command:
adb shell "echo /dev/block/mmcblk0p3 > /sys/devices/platform/usb_mass_storage/lun0/file"
That will allow you to access your SD Card from your PC, just copy your modded ROM to it.
Now, issude the following command:
adb shell mount /dev/block/mmcblk0p3 /sdcard
This will allow you to install the .zip file from CWM, go ahead and do that.
After checking partition types, your device will reboot and appear on a countdown to find the external SD Card, go ahead and reboot it manually before it does automatically (reboot to recovery with volume up).
Flash the .zip again, this time the installation will go successfully and you will have a working device.
Optionally, flash your desired Google Apps.
Now if we could get back to my original question, does anyone know why this device will not allow me to ADB it even when it's in download mode (a.k.a volume down/power button)
I actually got my tablet to boot up this morning for about 1 minute, then it shut off for no reason and did the "verizon" flash again when restarted.

priyana said:
Don't look at Overcome method if you have a CDMA tab.
It will only brick your tab if it ever worked at all.
Regarding bad internal memory, there are two chips. The OneNand 512MB and the MoviNAND 16GB.
If your OneNAND is the one broken, removing the MoviNAND achieved nothing.
The bootloader, modem, (and is it /system too of stock rom?) sits on OneNAND.
Click to expand...
Click to collapse
Please correct my but, what other then the modem.bin File could brick such a CDMA Device?
AFAIK as long as he picks the correct CDMA modem.bin it should work alright?
In the case that I am in error, then how does One recover such a CDMA Device then?

I can easily recover this device if I can get the ADB commands to start working. I feel like no one is reading the instructions. If you look at the link where the instructions are, there is a screenshot of his device. All of that "unable to mount" etc is what was happening to my device, hence why I removed the failed chip.
If I could get my device to show up in ADB, I wouldn't be asking this question!
By the way, I'm on an HP DV6. I tried all this in windows 8 and got nothing, so I installed a backup hard drive and put windows 7 on (this is what I'm on now) to see if that'd make a difference. Still nothing. I also tried on my old Gateway desktop but in download mode my old PC (still USB 1.1 1GHz celeron 512mb ram) the PC has no clue what the tablet is.

So I finally got this thing to boot into 2.2. Now the touch screen is unresponsive and the battery goes to 0 as soon as it's unplugged. Going to take it apart in the morning and make sure everythings connected. Might try a new battery but if this thing doesn't show more promising results soon I'm going to just say screw it and get rid of it.
Edit: Touch screen works but is flipped. If I slide my finger side to side nothing happens. If I slide it up and down i can awkwardly unlock the device. I'm guessing reload the factory image?!

the CDMA device is of different hardware. Not just the modem.
I am not technical enough to explain the difference. But I know Overcome method will brick it.
EliteEmerz: can you at least share how you get the PC to detect your device again?

priyana said:
the CDMA device is of different hardware. Not just the modem.
I am not technical enough to explain the difference. But I know Overcome method will brick it.
EliteEmerz: can you at least share how you get the PC to detect your device again?
Click to expand...
Click to collapse
If you put it into download mode it shows right up in my device list, drivers for "samsung USB device" load up. I can contact the tablet through heimdall to load bootloaders, images, etc.
For some reason I got it working pretty good last night except the touch screen issue. I reloaded the stock rom again and am playing with the SD card partitions since that's how I got it to boot up the last 2 times. I dont even care if I can load Jellybean on, I just want a working tablet.

By the way, this is SOLVED.
It will now boot up using a Stock ROM plus the zImage + recovery from clockworkmod
My touch screen is flipped (so I have to slide up and down to get it to swipe side to side) but at least it's on now. Made a new thread to address the flipped touch screen issue!!

[Q] Second Screen Simulation activated - Phone doesn't boot properly

Hi,
i just activated the "Second Screen Simulation" in the developer options on my S 3 Mini, now it won't boot again to work completely.
I got the SlimKat CustomRom and TWRP v.2.7.1.0.
After i press the Power-Button the Samsung Logo appears and then the "SlimKat" Logo appears. The SlimKat Logo pulses and then it just stops to pulse and the phone freezes.
Now i got the idea if i could just edit the settings via terminal in TWRP, is this possible? If yes, can anyone tell me where the settings-files are located?
If no, anyone got another idea to get it back to work again? I definetly don't want to reinstall it.
And YES, i searched the forum!
greetings

solved
I just fixed it myself.
And here's how you do:
backup the file "settings.db" under the path /data/data/com.android.providers.settings/databases. I accessed my phone via TWRP file manager and copied it on my computer.
open the file with a sql manager e.g. the firefox addon SQlite Manager.
browse to the key "global" and DELETE the last key with name="overlay_display_devices". I know this is risky but it worked for me.
Than simply copy the settings.db to the original path and boot your phone.