yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] Christian Nothing:
What :eek:

Now you have an s2 Gaby :cool:

Greetings my friend in our community ;)

Sent using my Premium-DUAL-Zanpakutōs (斬魄刀) powered by my Shinigami soul ◣_◢
[Galaxy S II Android Development] stgaby:
It doesn't
[Galaxy S II Android Development] stgaby:
thats your opinion
[Galaxy S II Android Development] stgaby:
hi. well for now its just cm10.1 stock .. soonm i'll replace them with 4.1.2 stock famework
[Galaxy S II Android Development] stgaby:
Hi Cristian yes i have it for a month .. i just want to make some new stuf :) soon i'll post a new ROM for LG P500
[Galaxy S II Android Development] vc3181:
well, i think ur rom will be popular if using 4.12 framework base on 4.22 baseband. thank you.:good:
[Galaxy S II Android Development] neuropsychosis:
What did you change? Anything unique about this rom? It looks like normal cm 10.1 with tw skin.
[Galaxy S II Android Development] stgaby:
i'll try to put some S4 apps (s voice, s translator, ... etc) soon ....
[Galaxy S II Android Development] ab-samy:
Welcome mate!

Another custom rom for our beloved Galaxy SII. good work
[Galaxy S II Android Development] Christian Nothing:
good for you mate :cowboy:

oh you're still using my old theme that i posted in your rom for p500 :confused:
[Galaxy S II Android Development] andrewwright:
Seems a great idea to do tw in cm ROM. Is this stable. Is the battery better building this way or is it just hype? Many thanks. Downloading now :thumbup:
[Galaxy S II Android Development] stgaby:
.... i think so .. its the same from TW5 for Lg P500
[Galaxy S II Android Development] stgaby:
well the battery seems to be the same as in Stock... and yes it's stable
[Galaxy S II Android Development] Christian Nothing:
Oh ok then I should make another one but with tw6 graphics pngs :D

Sent using my Zanpakutō (斬魄刀) powered by my Shinigami soul ◣_◢
[Galaxy S II Android Development] andrewwright:
Flashed ROM and works nice and smooth. Good job on the look. Hope to see some updates for it. Would love stock 4.1.2 contacts and message. Works well with dorimanx kernel. Only kernel I use :D:thumbup:
[Galaxy S II Android Development] stgaby:
Release ...v2... Uploading
[Galaxy S II Android Development] eissenvale:
can you describe more detailed about your rom...'m interested :fingers-crossed:
[Galaxy S II Android Development] stgaby:
I added s4/note 3 lockscreen it's the same lockscreen as in RevolutionRom

I added s4 settings ... ad some ... other apps form s4...

i think for now its almost the same 4.2.2 like s4's 4.2.2
[Galaxy S II Android Development] piotrmokrzycki:
If I want install V2 I need some gapps ?
[Galaxy S II Android Development] vishal11in:
Battery on these rom are very bad. Otherwise they work smooth
[T-Mobile Samsung Galaxy S 4] boostjunkie92:
So I flashed my metro s4 to a custom rom (wicked v4 for tmobile) since the phone is basically a tmobile phone with a few metro badges according to other threads...flashed seamlessly, works great aside from tethering.

I cant get the tethering to work anymore, before it would direct me to the metro tether page, but now the page connection (i.e google.com) times out...I am connected to the phone and my wireless connection says I have "internet access" but wont load anything.

I assume this is because the APN settings were replaced with Tmobile APN settings per the tmobile rom.

I Checked the settings and they are in fact 2 apn sets to choose from. Either tmobile LTE or tmobile tethering, I had to alter the tmobile tethering apn to get it to connect to 4g. but it wont allow my laptop to recieve any data.

Im assuming I need metro PCS's tether settings since my phone is attempting to tether through Tmobile maybe.

Anybody have that information or know how I can get this working?

On a side not I am forced to use the native tether app on the 4g instead of my original app i tried (wifi tether TrevE mod) because that doesnt seem to work...my laptop doesnt see any ssid being broadcasted with that app.
[T-Mobile Samsung Galaxy S 4] boostjunkie92:
Nothing?
[Upgrading, Modifying and Unlocking] muadong_nhoem:
I was tried to open

Xda_IIi_LaunchROM_v1.10.124

(http://www.my-xda.com/downloads/Xda_IIi_LaunchROM_v1.10.124.exe)

with Windows Mobile 2003 - ROM Editor but the password was wrong(the following passoerds weretried '0x20040304', '0x89124137', '921211', 'HTC' but none seemed to work. If you are sure this is a WM2003 update file you can try to enter an alternate password.)

Anybody know the password??? please help
[Micromax A110] Raghavendra Karanth:
Hi, bsuhas i have installed your rom version 12.1. Its extremely good and thanks for the same. I eagerly await the next version with the corrected OTG function.

thanks again for your wonderful Rom.
[Micromax A110] Parthalucky:
Thanks for ur awesome rom

Hello Mr.Suhas,

Thanks for ur awesome rom. I have been with ur rom from V1 to V12.1 and eagerly waiting for ur next version v13
[Galaxy S I9000 Q&A, Help & Troubleshooting] kikko118:
Hi, i have a problem. In my Samsung i9001 I installed the ROM Ginger Revenge, but the problem thenar with any other ROM I go to install. Only when they are connected via mobile data and the network goes EDGE phone has two anomalies. The apk active close and the phone starts alone to make screenshots. I tried to do clean installations, change recovery, but still the same problem. Someone who can help me? Thanks in advance
[Galaxy S I9000 Q&A, Help & Troubleshooting] freakymod2120:
Hi,

have you done a fresh install with wiping caches and so on ....???

The making of screenshots is irritating me ...on a PC it would sound like a virus ...but it won`t be some ...:o
[Galaxy S I9000 Q&A, Help & Troubleshooting] kikko118:
Yes i've install all rom with clean installation, with all wiping included but the problem its the same :mad:
[Galaxy S I9000 Q&A, Help & Troubleshooting] freakymod2120:
But there is no special app you`ve installed???:confused:

Have you checked logfiles ,for example dmesg ==> kernel-messages ???
[Galaxy S I9000 Q&A, Help & Troubleshooting] ktulu84:
this is a phantom key press problem... the only known workaround for this is to install a kernel with phantom key presses filter... but there are no kernel for GB, only ICS and JB

look here http://xdaforums.com/showpost.php?p=42354290&postcount=2

and here http://xdaforums.com/showthread.php?t=2265256
[Galaxy S I9000 Q&A, Help & Troubleshooting] kikko118:
thanks a lot I solved the problem now everything works perfectly :D:D:D
[Galaxy S I9000 Q&A, Help & Troubleshooting] ktulu84:
Glad to hear that :D
[Galaxy S I9000 Q&A, Help & Troubleshooting] compacity:
no thanks?
[Galaxy S I9000 Q&A, Help & Troubleshooting] ktulu84:
What are you talking about?

Inviato dal mio GT-P3110 usando Tapatalk 4
[Galaxy S I9000 Q&A, Help & Troubleshooting] mrjraider:
GingerRevenge is a GB ROM how on earth is PFK working??
[Galaxy S I9000 Q&A, Help & Troubleshooting] ktulu84:
He changed rom

Inviato dal mio GT-P3110 usando Tapatalk 4
[Desire Q&A, Help & Troubleshooting] Scamm0r:
Hello all,

I've done a search on this but can't find anything describing a problem exactly the same as mine (although I have a feeling it is what people mean when they say bootloop?).

So with the eventual aim of freeing up the internal storage on my Desire by partitioning the SD card (and using link2sd), I have gained S-OFF with the Revolutionary method, got root with superuser.zip and used 4ext Recovery Touch to format the SD card by using this guide. Now this is where things went a bit wrong. 4ext kept saying I was in safe mode and didn't seem to be doing anything. I followed some more instructions from here to wipe the cache and possibly some other things (this is probably where I went wrong..). I do believe I now have a 2GB sd-ext partition (ext3) and 6GB FAT32 (it's an 8GB card).

Now, when I boot the phone it goes straight to the hboot screen (white screen with skateboarding androids). No matter what options I choose it won't boot into Android-proper. I can however, get back into Recovery (4ext) so I'm assuming I'm not in a huge amount of trouble and have perhaps just screwed up my stock install.

I was planning on keeping it stock (it is actually my girlfriends so I didn't want any hassle), but now I am thinking I could just install a new ROM? Just wondering what my best route from here is..

Should I attempt to go back to stock by following a guide like this (2nd post) with a 'Desire 2.3 RUU (PB99IMG)'? Will that work? Will it undo everything else I've done? Having read up on here about RUUs I'm a bit scared of that to be honest..!

Or should I follow post #1 on the troubleshooting guide and use 4ext to install a brand spanking new ROM?

Thanks for any advice.
[Desire Q&A, Help & Troubleshooting] eddiehk6:
No need to RUU, that would undo everything.

So you're already s-off, with 4ext installed, and you can boot into recovery :good: You've partitioned your sd card correctly too (ext4 should in theory be faster than ext3, you can convert it quite easily in 4EXT, but may not make much difference)

Now just install a new rom from scratch is the easiest way. Pick one from the development section, still plenty of choice. You can even find the stock rooted 2.3.3 Rom there somewhere if she wants that. Use the "wipe all partitions except sd card" option within 4EXT, then install the ROM.zip.

When you pick a ROM, you should also check which hboot is more optimal for space within each thread. You're currently still on stock hboot I take it, which has 250MB system size. A lot of ROMs have smaller system than this, so using a more efficient hboot with smaller system size (and larger internal memory (/data) partition :) ) is beneficial. You'll need to go to alpharev.nl to find the hboots, and I recommend to flash them using fastboot commands

Depending on the ROM, you may not need to use link2sd at all as it likely has an A2SD script built in, or you may need to activate it via terminal commands, read/search the individual rom thread for details.

If you're still worried about space, I always recommend to use an app like 'diskusage' to browse all your partitions.
[Desire Q&A, Help & Troubleshooting] Scamm0r:
Thanks, very helpful. I did originally partition the ext-sd as ext4 but when it didn't work I thought I should perhaps try ext3. I thought perhaps the Desire wasn't recognising the ext4 format. As it turns out I think it was just because I had done it all in safe mode? Will the Desire recognise a 2gb ext4 partition? If so, I may as well reformat again..!

Unfortunately I'm at work now so don't have the phone infront of me. I remember it says 'Revolutionary' in pink at the top in hboot, but I can't remember the numbers.

As for ROMS.. hmn so many options. Any recommendations for something stable and reasonably fast. Stable being the top priority I suppose. I'm tempted to try a JB ROM but I'm assuming that wouldn't be particularly fast or stable! Might be interesting to try though. I will use Apex Launcher over the top of it anyway...
[Desire Q&A, Help & Troubleshooting] Chromium:
Try deleting the 4ext folder on your sd card to fix the safe mode issue, or also try going into wipe and select "Format all partitions (except sd card)."

I would recommend any of milwilds roms. My personal favourite is this one. Its very fast and stable, based on gingerbread, and its usually what i install on other peoples desires.

As for jb roms go, i wouldnt recommend one if your installing it for someone that doesnt know much about phones. They arent particularly fast, but the one i use (in my signature) is quite stable in my opinion.
[Desire Q&A, Help & Troubleshooting] eddiehk6:
If you don't remember changing hboot, you're still on stock hboot.

I can also vouch for mildwild roms. These have much smaller system sizes, so best to change hboot before you install them as instructed above. Most of them fit into cm7r2 hboot, but check each thread for compatibility.
[Desire Q&A, Help & Troubleshooting] Scamm0r:
Thanks guys. Would you recommend that MW ROM over something like CyanogenMod 7.2.0.1 off their site? I see CM banded around quite alot, seems to be a go-to ROM for alot of people?

I'm home now, this is what I see on hboot:

-Revolutionary-

BRAVO PVT1 SHIP S-OFF

HBOOT-6.93.1002

MICROP-031d

TOUCH-PANEL-SYNT0101

RADIO-5.11.05.27

Also, before I do it. Any problems for the Desire to see a 2GB ext4 partition? With the rest as FAT32? She won't be putting alot of media on it as she has a separate iPod.

Thanks.
[Desire Q&A, Help & Troubleshooting] Chromium:
I would go with mw over cm. Cm 7 feels old and stale, while milwilds redux ROM feels fresh and different. In terms of stability and speed they are pretty much the same.

2gb shouldn't be too much of an issue, but usually the max recommend ext partition is 1.5gb.
[Desire Q&A, Help & Troubleshooting] Scamm0r:
Thanks again. I'm now up and running. Looks very nice indeed! I'll be honest though, I bailed out of flashing a new hboot. Too scary. After incurring the girlfriend's wrath after one day with a dead phone, I wouldn't want to brick it entirely! :D

A couple of questions now..

- Do I need to install link2sd? I'm looking at 'diskusage' but I'm struggling to make much sense of it. I can see my sd-ext on there though which I guess is good!

- Are there any peculiarities installing generic apps like Facebook, Youtube etc? At first glance the market seems to work ok.

- Does the cpu underclocking (whilst screen off) work well? Is it risky at all if I use the generic settings?

Also, I was going to chuck Apex launcher on it for her (I love it, and she wants a scrolling dock) but it's not compatible. Any others that are good? Nova isn't compatible either :(
[Desire Q&A, Help & Troubleshooting] Chromium:
No need to install link2sd. A2sd is installed by default and is already activated. Dont worry about it.

Apex and nova need 4+, so i would recommend holo or go launcher. i think the default cpu settings work good enough.
[Desire Q&A, Help & Troubleshooting] eddiehk6:
You won't brick your phone by flashing an hboot, as long as you follow all the instructions ;) . It's beneficial just in case your girlfriend starts installing many apps. App data still gets stored on the internal memory (/data) partition, so it may get the low memory warning again which kind of defeats the purpose of doing this in the first place.

Open diskusage again, choose /system. You'll see a lot of free space on this partition....that's basically all completely wasted on stock hboot. At least you can see you sd-ext partition fillling up though.

There's another way to flash hboot without fastboot commands if you prefer. I always recommend that way simply because it forces the user to understand a little about what they're doing, plus it's always handy to install adb and fastboot drivers anyway :)

So:

- Download the PB99IMG_cm7r2.zip from alpharev.nl, rename it to PB99IMG.zip exactly, not PB99IMG.zip.zip, put it on the root of your sd card

- Reboot directly into recovery, nandroid backup (hard to go wrong now, no need to worry)

- Power down, boot into bootloader (vol down + power)

- It should find the file, and ask you to flash it, select yes

- Reboot into recovery, full wipe and nandroid restore

- It's exactly the same, but enjoy the extra internal memory. Open diskusage again, you'll find that there's less free space on /system, and /data has increased :)
[Desire Q&A, Help & Troubleshooting] Scamm0r:
Thanks Eddie, you're right of course. How safe is that method compared to using Android Flasher? I already had that installed on my PC for one of the steps previous.

So the nandroid backup will keep the phone set up as it is? I know she will have been customising her homescreens etc already now that it's up and running haha. OR is it best to reinstall the ROM again anyway and start from scratch?

I presume the backup option in 4ext recovery is a nandroid backup? I think I did one of those before after I got MW up and running.

Thanks again.
[Desire Q&A, Help & Troubleshooting] eddiehk6:
Android flasher is the same as fastboot really. It's just a program so you don't type things. I've never used it personally, but it should work. I believe you flash the cm7r2.img directly (not the.zip file). All 3 of those methods (fastboot, android flasher, PB99IMG.zip are safe, get the same result eventually)

The thing to remember (which I should have mentioned before) whichever method you use, check the md5 sums of the .img files before you flash them (you should be able to see those long text/numbers on the alpharev page). Search for a program called md5check. (It just basically verifies the file against that md5 sum like a barcode so you know haven't downloaded a bad file.)

Nandroid backup is an exact image of the phone as it is. Homescreens, saved game data, texts, everything. So you won't lose anything after restoring it. I suggested that you change hboot before you install the rom for this exact reason, so you wouldnt have to backup and restore, but we're here now already ;)
[Galaxy S III Q&A, Help & Troubleshooting] xG-Tank:
Hi,

i have tried changing from a couple of roms and i am just unable to connect to the front camera. I do not know what is wrong! can someone please hlp me?
[Galaxy S III Q&A, Help & Troubleshooting] ashraf sharif:
try going back to stock rom. camera still not working? than it is probably a hardware issue .take it to a service center
[Galaxy S III Q&A, Help & Troubleshooting] pulley06:
Try flashing the ROM again after wiping caches. Faced this problem today for the first time with Omega. If that doesnt help try to flash some other ROM.
[Galaxy S III Q&A, Help & Troubleshooting] rroronoa:
E: Sorry, read wrong the OP
[Galaxy S III Q&A, Help & Troubleshooting] skassa22:
Check camera firmware digits this in the dialer:

*#34971539#
[Galaxy S III Q&A, Help & Troubleshooting] xG-Tank:
it says invalid code... can someone please help me change the camera firmware?
[Galaxy S III Q&A, Help & Troubleshooting] JJEgan:
See your identical same post
[Galaxy S III Q&A, Help & Troubleshooting] CODENEX:
Is this a common issue

From the experiences on installing custom roms (AOSP based) such as CM 10.1(snapshot release) and AOKP(milestone). Camera crashing was the common and irritating bug ever had. In CM 10.1 it was slightly less, but in AOKP Camera freezes like 1 time interval (1st time not responding and 2nd time it's working).

I've read in most of the AOSP based roms for S3 (I9300), this is a common since the firmware itself is locked. Is there any glitch free AOSP based roms with good rom controls and customizable options available for S3? I'm really looking forward for Paraniod Android and RootBox, fingers crossed :rolleyes:

Also does flashing kernal will do any good? (see: http://xdaforums.com/showpost.php?p=42766353&postcount=4)

I'm sorry if this post intended to against the thread topic.

** FIXED THIS WITH THE ROOTBOX ROM, BUT PROBLEM CAUSE IS STILL CONFUSING **
[Android Q&A, Help & Troubleshooting] Destroyedbeauty:
Guys, I need some serious help with getting a couple of init.d tweaks to execute at boot on my Xperia Z. I'm stuck atm because this is also stopping my work of an custom ROM..

Every time I'm trying to verify that my init.d scripts are working and can be executed at boot, I got some strange errors (see attached screenshots for further details down below).

I have tried with a lot of things - changed permission of certain folders, changed permissions of scripts etc etc but nothing is working

The init.d scripts I'm trying to execute is the battery script from Here (Check init.d section) and undervolting script from this link

See attached screens for more info..

Error 1

Error 2

What am I doing wrong?
[Nexus 4 Q&A, Help & Troubleshooting] Thibaultvw:
Hello! I know I have already posted a few threads about this, but I want to be 100% right, that's the only way to learn Android!

So I want to flash CWM touch recovery to my device, and I don't want to use any toolkits like I did before. The only thing I want to have from the toolkit now are drivers, because I won't uninstall them, seems pointless. :)

This is how I think you have to flash a recovery, but please correct me if I'm wrong!

1.Download fastboot files and place them in any directory (how many files are they? Do I have to extract them?

2.download customrecovery.img and place the file in the same directory as the fastboot files.

3.Open command prompt in that directory and type "fastboot flash recovery customrecovery.img"

Is this the full guide on how to install a recovery? Thanks in advance!
[Nexus 4 Q&A, Help & Troubleshooting] rickbosch:
In a nutshell, yes, you are correct. For more detailed answers:

1. Yes, place them in the same directory as your ADB drivers, that way you won't have to CD when switching between the two.

2. correct

3. this is correct, but you HAVE to be in bootloader mode.

So the order would be:

adb reboot bootloader

fastboot flash recovery customrecovery.img

Easy, and +1 for wanting to learn how to do things the proper way.
[Nexus 4 Q&A, Help & Troubleshooting] Thibaultvw:
Ok so the only files I need are adb drivers, fastboot drivers and the recovery. But do I have to extract any of them? Or just download and place them in the directory without changing the files?
[Nexus 4 Q&A, Help & Troubleshooting] rickbosch:
that would depend where you got them. I use this, because I don't want to download and install the SDK. Download the zip at the bottom of this post (http://xdaforums.com/showpost.php?p=34552123&postcount=1) named "platform-tools-v16.zip". Extract the contents to an easy to reach folder, I use C:\Android. Then when you want to use terminal commands shift+right click "open command window here", connect your device, ensure USB Debugging is on and that you've given ADB permissions when it asks for the RSA key. Then you can run "adb devices" to see if they work properly.
[Nexus 4 Q&A, Help & Troubleshooting] Thibaultvw:
And when I've done all that I just have to reboot in bootloader mode and I can flash the recovery?
[Nexus 4 Q&A, Help & Troubleshooting] rickbosch:
yessir.
[Nexus 4 Q&A, Help & Troubleshooting] Thibaultvw:
Are ADB and fastboot correctly set up now? From now on I just have to download the recovery and I'm good to go?
[Nexus 4 Q&A, Help & Troubleshooting] ksilver89:
Boot your phone into bootloader mode, connect your phone to your PC with USB cable, run command "fastboot devices" to check if the driver is properly setup. If you can see your device ID then it is good to go.

Else, download google usb drivers here: http://developer.android.com/sdk/win-usb.html
[Nexus 4 Q&A, Help & Troubleshooting] Thibaultvw:
This guy says you have to wipe data/factory reset. I dont think thats needed right? Cause he actually wipes his OS right?

http://youtu.be/nb_MweQpGbQ
[Nexus 4 Q&A, Help & Troubleshooting] electric0:
You don't have to flash the user data image, but it could result in not getting past the boot screen on initial boot.