yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] ABHIII:
Hi Marcellocord, can you release a new build based on the latest Cyanogenmod9.1 stable version? I see that the current version is based on nightly.
[Galaxy S II Android Development] :
When I have time I'll release v3 based on latest nightly. Though you won't find any significative difference between v2 and 9.1.0 stable and newest nightly. I don't care about labels, "nightly" is as stable [or even more] as "stable".

ps: main feature on 9.1.0 is something with NFC. I guess it's NFC payment.
[Galaxy S II Android Development] ABHIII:
i agree on that part.. CM9.1 just got few add ons.. Can you please share some screenshots on battery Screen time on..

---------- Post added at 09:28 PM ---------- Previous post was at 09:24 PM ----------

Since it's has siyah kernel.. does it has the annoying siyah boot splash ??
[Galaxy S II Android Development] :
I'm with CM10 right now, and I won't post any screen on time because I normally don't go under 60%, and I charge every night. And it's also very relative, some people get 7h screen on, some get 2h, I don't use the phone to keep checking battery, I use the phone when I need and want, no undervolt, medium brightness, no task killers, no battery tweaks to low down performance. Some people here claim that battery life on my ROMs is good, but I can't tell you mine. Not because is bad, but because I just don't know
[Galaxy S II Android Development] ABHIII:
Fair enough... i agree that usage varies from user to user. i just had a poor experience on various roms other than the stock.
[Galaxy S II Android Development] :
Yes. Just create this file on the root of the internal storage: /sdcard/.nobootlogo

Don't write anything inside. Reboot and boot logo is gone.
[Galaxy S II Android Development] ABHIII:
I'm now using your CyanogenMod 9 lite. Though it is lite, it seems to be little sluggish....
[Galaxy S II Android Development] :
Full CM9 is even more sluggish

btw, I'll see If I can put fluxi kernel XX.02b5 next version. Much smoother than Siyah but very old.
[Galaxy S II Android Development] ABHIII:
No mate, CM9.1 stable is definitely smoother. That's why i requested you in the first place to make a lite version of it. I just got off that Rom and i immediately felt the difference. Appreciate your work.:thumbup:
[Galaxy S II Android Development] :
So use full CM 9.1.0, I don't care. I'll work on CM9 v3 if I want to work, not because someone asked me to. I'm using CM10 since a long time ago, and still worked on CM9 v2 because I have respect for the people who liked it. As I said, there isn't a lot of changes between the build on v2 and 9.1.0, so I have two options: a) there's some magic change that made it fly b) placebo

thanks.
[Galaxy S II Android Development] ABHIII:
I simply requested. Anyway its your choice and not the end of the world for me. Besides i found it sluggish so i wrote for you to see. :)
[Galaxy S II Android Development] :
Good for you.

btw, maybe I'll change devices tomorrow, I'll sell mine to get a Nexus, but until that, I'll be using an iPhone 4S [sad story, very sad story][unfortunately][I don't want iPhone!!!!][Hope I get my Nexus soon].

That means updates will be less frequents, but I'll try to still work on it, I promisse, as soon I feel the need for more updates. Well, before I change my device, I'll update CM 10 and 9, as a thanks to everyone who supported me [even if only a few, and every 33 people who thanked me here]. Not the last update, I'll update when I feel the need to. The good news: I'll also update my CM9 patches and include a CM10 version, so you don't feel the need to wait for me on every update.

A big thanks to everyone!!
[Galaxy S II Android Development] Nasty_z:
Enjoy your new phone ( No, not iCrap ) :)

Sent from my S II ( "Jelly Bean'd Monster" ) ;)
[Galaxy S II Android Development] :
Is anyone using my ROM? If three people are using I'll make v3/v8, otherwise, I'll just close the thread. I'm not with my i9100 anymore, I'm waiting for my nexus, so I can't waste my time in something no one is using.

Thanks, or sorry.
[Galaxy S II Android Development] prbassplayer:
Locked to OP's request
[Nexus 7 Q&A, Help & Troubleshooting] mtxx1:
I notice that i have incompatibility prompt when. Want to install these from the play store?

What could Bethe cause? Please help me...thanks...
[Nexus 7 Q&A, Help & Troubleshooting] veeman:
It's fine for me.
[Nexus 7 Q&A, Help & Troubleshooting] mtxx1:
I know its suppose to work.

But mine is not. So weird and annoying!
[Nexus 7 Q&A, Help & Troubleshooting] krelvinaz:
Fine for me as well... have you made changes to your build.prop?
[Nexus 7 Q&A, Help & Troubleshooting] mtxx1:
Yes, DPI to 175.

But after I restore back to 213 still same issue?

How to fully restore it?
[Nexus 7 Q&A, Help & Troubleshooting] krelvinaz:
Take the original file you saved in a safe place before editing it and put it back.
[Nexus 7 Q&A, Help & Troubleshooting] mtxx1:
I don't have it. I edit using ROm toolbox.

So how? The only value I change is the DPI.

Already set it back but no change.

Factory reset will restore build prop?
[Nexus 7 Q&A, Help & Troubleshooting] NIMBAH:
Set your build prop back to original. Then force stop and clear data for both market.apk and Google services framework. Then restart.
[Nexus 7 Q&A, Help & Troubleshooting] mtxx1:
thank you very much, it works. i am able to install those tegra 3 apps now.

wonder after i install and switch back to tablet mode will it work again.

i dont like the phone UI at all.
[Nexus 7 Q&A, Help & Troubleshooting] mtxx1:
Swap back to tablet ui

The market is good now. I can install tegra 3 games.

I think this issue started after I flash the battery icon mod. After doing the wipe data for play store and Google service, all is well. Thanks every one for replying
[Nexus 7 Q&A, Help & Troubleshooting] unique_red:
Noob here, rooted yesterday, same thing happened

I did this (changed dpi back to 213) but couldn't find a way to stop and clear data for market/playstore and google services framework. How do you do this? Please help?
[Nexus 7 Q&A, Help & Troubleshooting] NIMBAH:
Go to settings then apps and click on all. Find PlayStore and Google services framework, force close/wipe then restart.
[Galaxy Note GT-N7000 General] philip_rhoades:
People,

I get errors about the Android keyboard stopping working - just providing feedback here since I can't post to the development forum yet.

Thanks,

Phil.
[Galaxy Note GT-N7000 General] masiegel:
On which rom are you?

Clean or dirty install?

Wipes?
[Galaxy Note GT-N7000 General] antiochasylum:
Do not for one second think this belongs in development. IF YOU DID NOT CREATE "IT", THEN DO NOT POST IN DEVELOPMENT. Just to make that clear.
[Galaxy Note GT-N7000 General] philip_rhoades:
Daily driver: RocketROM v10

- Installed the cm-9.0.0-n7000.zip from recovery

- Reboot

- Installed the cm-10-20120814-UNOFFICIAL-n7000.zip recovery

- Install gapps

- Reboot

No WIPE DATA/FACTORY RESET - should that make a difference?

Thanks,

Phil.
[Galaxy Note GT-N7000 General] philip_rhoades:
How do developers get feedback on the functioning of the ROM they have created then? It would seem dumb to post responses in a different forum . .

Thanks,

Phil.
[Galaxy Note GT-N7000 General] AA1973:
The installation process clearly states Wipe data/factory reset and then reboot...

So how about trying this?

Btw devs do highly appreciate if you follow their advice (rarely and uncommon to be found in the first post) of how to install their ROM properly in order to get the ROM working and finding bugs afterwards. Which includes a clean install in most cases i.e. wipe data/factory reset.
[Galaxy Note GT-N7000 General] chasmodo:
You can always take your case to the Mods, Phil. Just tell them their rules are dumb, I'm sure they'll revise them.
[Galaxy Note GT-N7000 General] masiegel:
In that case it's only logical thatyou haveproblems. After changing a type of rom (stock, different cm, etc.) always make a full wipe
[Galaxy Note GT-N7000 General] emuX:
People often post about bugs, etc. in a developers ROM thread - you just shouldn't be creating new threads off topic.

In your case it would probably just annoy people as your problem is likely to be due to lack of research...

Read the installation instructions for CM9 on this forum. Its says you have to wipe after the install. I've gone from Rocket to cM9 (playing about with different roms) with a wipe after the cm9 install and mine works fine.
[Galaxy Note GT-N7000 General] reinbeau:
Thread closed

There is a thread for the discussion of CM10 issues, this discussion belongs there.

Development is for support questions, it's for development. Ask your questions in the appropriate area after searching to make sure your answer hasn't already been posted. The developers get the information they need, knowledgeable users will help you as long as you make it clear you have done your research first.
[Samsung Galaxy Nexus] schwartzman93:
I am running the Vicious-JB-4.1.1-V1 ROM alongside Franco Kernel. My phone stays in the Google screen for a really long time before it goes into the "X" boot animation. Someone suggested I flash the Jelly Bean bootloader, which I did. However the only one I could find was the bootloader for Android 4.1 and not 4.1.1 and it didnt seem to help any. Anyone else have any suggestions?

Or can anyone give me a link to the Android 4.1.1 bootloader
[Samsung Galaxy Nexus] bostonbassman78:
Try a different ROM I know my first boot on the ROM I'm using took a bit to boot up but after a while it boots right up I'm running pa toro 1.99 its nice real nice
[Galaxy S III Q&A, Help & Troubleshooting] Keymab:
Hello guy im having some issues installing omega v12 to my gs3 my phone is GT-I9300 model and rooted, I downloaded the room to my internal sdcard and install it via cwm, the installation secced every time but when it reboot it gets stuck at samsung logo and returns to recovery, whats wrong with my phone? or what am I doing wrong?
[Galaxy S III Q&A, Help & Troubleshooting] Keymab:
Anyone pls.!!!!!:crying::crying::crying::crying:
[Galaxy S III Q&A, Help & Troubleshooting] dave6018:
Have you wiped it before flashing the Rom e.g. factory reset wiped cache and delvik cache also they flashing it twice straight after each other
[Galaxy S III Q&A, Help & Troubleshooting] EnemyOfGlaDOS:
There should be no need to install it twice in a row. Try what was first suggested.. when in recovery, wipe data/ factory reset, wipe cache, wipe dalvik, flash ROM... reboot.

Did you make a nandroid backup before flashing?
[Galaxy S III Q&A, Help & Troubleshooting] Keymab:
Yup I did all wipe and flash ROM, the Rom flashes perfectly, when it reboots goes to samsung logo twice, than it send me again to recovery mode, and yes, I made a nandroid backup, but its not working, im flashing criskelo ROM to see if it works. Any other Ideas?

Thanks for youre reply!
[Galaxy S III Q&A, Help & Troubleshooting] EnemyOfGlaDOS:
Bummer. Yeah flash another ROM if you have it on your SD card.. try to boot into something. If it was a bad DL of the omega rom it shouldn't flash, and the fact that your getting successful is weird :o

Next step is maybe pushing a files onto your phone via ADB and try to flash again. You got recovery so your not too bad off ;)
[Galaxy S III Q&A, Help & Troubleshooting] Keymab:
Guess what? Ive just install Criskelo ROm and it worked!! maybe omega ROM is wrong, I really wanted to try it, About criskelo ROM I went here http://xdaforums.com/showthread.php?t=1714091 but no kitchen option appear, I installed normally and I rebooted, what do I have to do?
[Galaxy S III Q&A, Help & Troubleshooting] hisee:
chek ur md5 of omega rom .. it must be bad download .. its happens when u flash bad downloaded file so always chek md5 before flashing any rom .. nice habit to chek
[Galaxy S III Q&A, Help & Troubleshooting] Keymab:
Checked, and its the same md5, anout criskelo I downloaded the full ROM not the kitchen!!! LOL
[Galaxy S III Q&A, Help & Troubleshooting] hisee:
then try again. wipe data wipe cache wipe dalvik and flash omega it will work if its nt a bad download
[Galaxy S III Q&A, Help & Troubleshooting] Keymab:
Another question, I came from a Gnex and there I knew all ROmS, about gs3 I know nothing, so, whats the best room right now? Omega, Criskelo? I like touchwiz Rom.
[Galaxy S III Q&A, Help & Troubleshooting] hisee:
see its depen upon u what u want ...looks with good battery (omega)or stock exp (check rom)or very good battery(rgui)..
[Galaxy S III Q&A, Help & Troubleshooting] Keymab:
Damn phone, I just Install criskelo kitchen ROM and I got stuck on samsung screen!! Maybe something is wrong with my s3, i just could install criskol full rom and thats it!!
[Galaxy S III Q&A, Help & Troubleshooting] hisee:
u have gt i9300 only na. ??? or other version?

---------- Post added at 07:58 AM ---------- Previous post was at 07:57 AM ----------

insll latest cwm. or cf root .
[Galaxy S III Q&A, Help & Troubleshooting] Keymab:
Yup, GT-I9300.Ill try to post a video.
[Galaxy S III Q&A, Help & Troubleshooting] Arsaw:
Maybe you can try formatting your system partition.
[Galaxy S III Q&A, Help & Troubleshooting] Keymab:
Done. Still the same. It wont boot

Mi stock firm its XXXXALFE something, does it has to do with it?
[Galaxy S III Q&A, Help & Troubleshooting] hisee:
as I said try to flash latest cf root and flash rom
[Galaxy S III Q&A, Help & Troubleshooting] Keymab:
I root it with cf-6.4 is that the latest?
[Galaxy S III Q&A, Help & Troubleshooting] Keymab:
Also re-rooted again, and no luck.
[Galaxy S III Q&A, Help & Troubleshooting] hisee:
:confused: try to do wipe dalvik fix permission. wipe cache after flashing rom
[Galaxy S III Q&A, Help & Troubleshooting] Keymab:
Didnt work.
[Galaxy S III Q&A, Help & Troubleshooting] Arsaw:
Weird phone....

Can you try using Superwipe script to wipe your internal memory.
[Vibrant Q&A, Help & Troubleshooting] iKoolkid:
Can anyone port the inverted chimera rom theme to a flashable zip since when I was using it, it seemed really good looking. Any ideas on how to make one myself? Or any very similar themes?
[Vibrant Q&A, Help & Troubleshooting] shreddintyres:
(facepalm) use the search button, making flashable themes is ridiculously easy and has been enumerated countless times. Secondly go post on the TP forums or their facebook for help with that ROM, I can almost gaurantee you that next to no one on XDA is gonna be running it.
[Vibrant Q&A, Help & Troubleshooting] silvercrown266:
+1
[Vibrant Q&A, Help & Troubleshooting] iKoolkid:
Well then OK. BTW I have searched but nothing did come up for me, idk why
[Vibrant Q&A, Help & Troubleshooting] mikka06:
try that http://xdaforums.com/showthread.php?p=7377678#post7377678
[Vibrant Q&A, Help & Troubleshooting] iKoolkid:
Thank you
[HTC Rezound] antp121:
Folks, we are back in business thanks to Con! If you wanna unbrick, download the zip.

32bit md5: d7c934f7d1491bd5dc5d8dac2e670c62

64bit md5: 83663ba898eedd951d0003a4f3d86171

* not affiliated with Dexter and his team.
[HTC Rezound] dmeadows013:
Nice
[HTC Rezound] AshtonTS:
[*unbrick*] is definitely not one of the tags permitted in the naming requirements by YZ

I kid I kid, good job :good:
[HTC Rezound] antp121:
its bc noones as awesome ;)
[HTC Rezound] ufish2:
hey whats the " appropriate package for the device"..is that the download files at bottom....
[HTC Rezound] antp121:
yup. pick 32 or 64 bit and then, once you figure out your hboot, put the number in the V.VV in the final command.

also, it supports 2.21 and 2.25 hboot's. ill support the 2.27 when there is a JB/eng version
[HTC Rezound] wlmeng11:
You mean you'll let dmeadows support it for you?

:p:p:p

Sent from my NeoMax Rezound
[HTC Rezound] antp121:
no, i know how to put a hboot in a zip...
[HTC Rezound] con247:
I have known this for months lol.
[HTC Rezound] antp121:
aren't you cool ;) jk but i think people could use this. i needed it last night when i derped. and im NOT a n00b like people say
[HTC Rezound] yojoe600:
cool story bro!
[HTC Rezound] SynisterWolf:
Yep, Joel shared your method with me. :)

Sent from my iPhone...
[HTC Rezound] AshtonTS:
yes you are :p
[HTC Rezound] feralicious:
This looks fun! I'm going to try it as my last ditch effort to revive my phone.

My phone was on GB (was running what's listed in my sig). I don't know what my hboot was, I got the first GB OTA. Now, my phone was working fine until a few days after the ICS release. It rebooted itself and never came to life, but I think the battery was dead too. From what I've read I shouldn't have been able to take the OTA but I find the timing suspicious, and I have tried everything related to dead battery reviving that I have found and there is still no life. At all. So I think maybe I had some sort of interrupted OTA?

Questions:

- I do not have a linux box. I have Vista and tomorrow my new laptop with Win 7 is shipping. Does it matter which OS I use if I use the Live CD? I have one I grabbed at least a couple years ago, do I need to get a new one? Not sure if the new laptop with Win 7 will still have usb 2.0. I also have a Mac desktop running Snow Leopard.

- Does the RUU I use depend on the hboot version I determine or should I just go to the latest ICS RUU?

TIA
[HTC Rezound] wlmeng11:
I would recommend using Ubuntu 12.04.

You should probably use the official ICS OTA, which is the 3.14.605.12 RUU.

You can't upgrade directly the latest update from Gingerbread.

Sent from my NeoMax Rezound

EDIT: If it still has the 2.21 hboot I think you have to run the gb ruu.
[HTC Rezound] antp121:
The ruu should be the same. As for Linux you can run a live CD. Should work since the files are like 30mb

Edit: oh yeah. One of the commands tells you what hboot your on if you don't know / remember
[HTC Rezound] feralicious:
If my hboot is 2.11 will this still work or is it only for 2.21 or 2.25?
[HTC Rezound] antp121:
The zip includes the 2.21 and 2.25 hboot. Just put 2.21 in the flash command.
[HTC Rezound] feralicious:
Well this didn't turn out to be as fun as I thought it would be. :(
[HTC Rezound] derick03:
Any hope for Hboot 2.27?

I am needing these instructions because my device will not get past the 4G boot animation after updating to the global roaming update (4.03.605.1). I was previously on 3.14.605.10. I had tried to update to 3.14.605.12 but I couldn't so I thought it would be ok to skip it and go straight to the global roaming update. Apparently I was wrong. Up to that point I was still locked. Now, in my meager efforts to repair, I have unlocked and flashed a custom recovery using hansoon's all in one tool, simply because it seemed like all roads to recovery pointed in that direction. But that's where it all stops. I cannot find any way to flash a stock ROM while on an unlocked bootloader. I simply want this phone to be exactly how it would be if someone were to pick it up from a Verizon store (except with having a re-locked bootloader rather than locked). This route seems like my best bet except for the fact that I'm on Hboot 2.27 now with and this process only seems to work up through 2.25. Are there any things I can do to make this work?
[HTC Rezound] wlmeng11:
You should ask this in a QA thread.

Anyway, you can downgrade to the previous update if you're S off.

Are you able to flash a custom recovery in fastboot? You should be able to so long as your bootloader is unlocked.

Sent from my NeoMax Rezound
[HTC Rezound] antp121:
Did you flash the ruu twice?
[HTC Rezound] SynisterWolf:
Front page news on XDA

http://xdaforums.com/showthread.php?t=1833530

good job guys
[HTC Rezound] antp121:
Wow! I've been front paged!
[HTC Rezound] antp121:
Dexter, could you please contact me?
[HTC Rezound] con247:
NOTE: The unbrick ONLY WORKS if you bricked changing from S-OFF to S-ON with "writesecureflag 3"

You can do it without his auto script. Basically the script the dexter is b*tching about automates step 5 (as far as I can tell). emmc_recover is attached in the unbrick.zip. You will also need a stock, signed hboot that is the version that corresponds to what is bricked.

Anyway, this should work:

1.) Boot up to Linux

2.) Copy the emmc_recover file and the hboot file you want to flash to the linux box somewhere, just in your home folder will do.

3.) START ALL YOUR TERMINAL SESSIONS with sudo -s (enter your password and make sure you've got your root (#) prompt.

4.) Run the command chmod 0755 /path/to/emmc_recover (changing "/path/to" to wherever it resides)

5.) Now this is where it's a little tricky, because you don't know exactly what device it's going to show up as... (mine showed up as /dev/sdb12 one time, then /dev/sdc12 a second time) So, in order to cover for this, open several terminal windows (starting with sudo -s) and type in the following command in each one just changing the third letter from b to c and d and so on.

./emmc_recover --flash hbootName.nb0 --device /dev/sdb12

So the next one would be /dev/sdc12, and so on.

It will ask you "Are you sure" press enter, it will ask once more, press Enter again. It should say "Waiting device /dev/sdb12......." (or sdc or whatever)

Make sure you get all your terminal windows to show this waiting state. And make sure you can SEE all of their outputs...

5.) Now... Holding down the Volume Down key, (and hold it down the ENTIRE time) and Plug the phone in (keep holding vol-down), now watch your terminal windows, ONE of them will say "Foundit!" and then say the following:

511+1 records in
511+1 records out
1047808 bytes (1.0 MB) copied, 0.36689 s, 2.9 MB/s
Retun code is 0

Ubuntu's USB service will lock up, a bunch of windows will pop up as if it's trying to mount disk drives and the screen will go to a terminal screen (press ctrl alt del to get out of that)

Other notes: Remove SIM, microSD card and battery and connect the device using the USB cable. This procedure must be done without battery. Flash the RUU of the hboot version right after you recover! You also might not need to hold volume down when plugging it in.
[HTC Rezound] af974:
Ok, let's go step by step:

* It should be better for you to communicate via PM instead in a pubblic forum, even better because you are both Recognized Contributors.

* Probably OP did this in bona feath but you can't just simply copy & paste the entire first post without even contact the other user.

* No member of the other team requested this thread closed or deleted nor they made any report.

Since all the above, i'm not going to close this thread so you can fix it if you want.

And.....this http://www.xda-developers.com/annou...addition-to-sharing-policy-on-xda-developers/

@ all, please stay away to post no sense crap.
[HTC Rezound] SynisterWolf:
Thank you.
[HTC Rezound] Marine6680:
^^^ That... most definitely that.

Glad to see this back up and running.
[HTC Rezound] wildstang83:
ant, con, d, and everyone else that played a part in making this "project" happen, thank you. You all have greatly helped OUR community. #TeamRezound

Now if we could get those idiotic tags removed...
[HTC Rezound] dmeadows013:
But I didn't do anything lol
[HTC Rezound] apophis9283:
This wont work if you screw up a hex edit with the HBOOT.... LMAO
[HTC Rezound] antp121:
More then dexter trololol sorry back to the topic...
[HTC Rezound] dexter93:
I guess you havent seen my pm's antp121 ?
[HTC Rezound] antp121:
Well, we don't need the script. It works w/o it. Also, I put a disclaimer in the OP for ya.

EDIT: Oh yeah and in your pm, you said I made a mess. I feel you did, but let's not start anything, since everything is well again.
[HTC Rezound] nallyvaico:
Hi guys

I seem to have bricked my phone too, though for different reasons.

I have a rooted and S-off Rezound, that had just been reflashed with 1.2 Rezound Meister Sense 4 ROM (GSM). Before, I had installed ROM Manager to facilitate the process.

I had worked for about 30 hours on this new ROM before this happened.

Any ideas? Sorry - am not Linux-savvy if that matters
[HTC Rezound] drt054:
I'm going to stop thanking people since nobody seems to do anything around here.. Lol j/k :D trololol

sent from my CM9-kanged HTC ReZound
[HTC Rezound] yojoe600:
Do you have clockwork mod recovery installed?

Sent from my Dinc... I mean Rezound