yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] g_money:
Cnexus built a recovery switcher that allows you to switch between cwm/cwm touch/twrp. I say install it, and try em all out:D

I know the first time I used twrp, I had an issue because if you have it set to check mdsum, it will fail if it can't find one. Simple, but it did kinda freak me out.
[Sprint Samsung Galaxy S III] Whiplashh:
I thought the same thing for a bit. Then I used TWRP 2.4.40 PR 2.4.2.0 or whatever that one was called, and I am loving it. Works perfectly fine for me. Used a flash able zip too.

------------------------

Sprint Galaxy S3 "Supernexus"

Whiplashh Rom

Look it up. :D
[Sprint Samsung Galaxy S III] noother84:
CWM doesn't let you queue multiple zips as far as I can tell, so I've been using TWRP.
[Sprint Samsung Galaxy S III] JoeFCaputo113:
TWRP all the way, plus you can theme it! The one and only thing that annoys me about TWRP is that the clock is always off -__-
[Sprint Samsung Galaxy S III] djconundrum:
Both are great and different roms need either to work right. But in my experience trwp backs up and restores without error. Clockwork never restored properly on any of my phones from og evo, evo lte or my sgs3. But clockwork flashes radio updates better, at least my reception bar level or data connectivity.
[Sprint Samsung Galaxy S III] CNexus:
Coincidence, the epic 4G has a bug that caused it to hardbrick when flashing certain roms (memory fault in the kernel or something like that). There was a workaround for this though.
[Sprint Samsung Galaxy S III] Ragnar:
Might as well put my 2 cents in. I have used both recoveries on my devices. I have no personal choice as to one is better than te other issue. I can tell that once cwm was actually fixed and built for the Epic it worked perfectly prior to that when it was first ported over to the OG Epic it was hit or miss, the orange cwm. Oh well my Epic did just fine on both. My Galaxy Nexus works better with TWRP for whatever reason it just does and my S3 prefers CWM again never had an issue with either on those devices but when I use the other recovery on each of those devices they become temperamental and start acting up. I know it's funny but that's what I know of my devices. They are both very good recoveries and they have come a long way since the early days.

Sent from the future via Xparent Green Tapatalk 2
[Sprint Samsung Galaxy S III] g_money:
So let me ask this: when a rom dev suggests a recovery, is that just because that's what the rom was tested with? Have you had an instance where you've *had* to use a specific recovery (other then one kind working better on a specific phone)?

Thanks
[Sprint Samsung Galaxy S III] socos25:
I'm not sure how themeing a recovery is useful? It's not like I'm showing my friends, hey look at this cool recovery. But which ever is fine.

---------- Post added at 10:26 PM ---------- Previous post was at 10:22 PM ----------

I flashed a lot of Roms on my epic, yes it could be coincidence, but like I said, shortly after flashing TWRP I was warranting my phone because it didn't make it through a flash. I tried everything including once when odining my epic my daughter yanked the plug out. I recovered from that even by removing my battery and plugging it into the computer. After TWRP, I couldn't even do that. And really I have no idea if it was the recovery, but yeah, I chose CWM.
[Sprint Samsung Galaxy S III] Ragnar:
No makes no difference, that's because that person has a personal liking for that recovery or like I said his device just responded better to that recovery. Makes no difference roms are not built for specific recoveries. Well not always there was an instance on the OG Epic where in order to flash cm9 the phone had to be re partitioned and a special recovery was necessary and the cm team built the recovery flash into the rom. That's another story for a different thread.

Sent from the future via Xparent Green Tapatalk 2
[Sprint Samsung Galaxy S III] CNexus:
Sometimes recoveries don't like certain roms...doesn't happen often, but it can

I know on my EVO Shift, Sense roms could be flashed ONLY with CWM for some reason, as TWRP wouldn't flash it properly.
[Sprint Samsung Galaxy S III] g_money:
So betweem you and ed, I should be able to flash a rom with either recovery unless posts show problems flashing with a specific one. And, if I *were* to have problems flashing, I may want to attempt to flash using a different recovery....

If that's the case, I just might pick one recovery, and stick with it!
[Sprint Samsung Galaxy S III] el6006:
I started out using CWM but lately I've been using TWRP instead and I like the large buttons and touch interface of it. I'm sticking with it I think.
[Sprint Samsung Galaxy S III] jeremiah.rs:
I was a longtime user of cwm, but switched to twrp around November last year and I haven't looked back. It's much more powerful and more options, at least my opinion.
[Sprint Samsung Galaxy S III] z28clark:
Used both, prefer twrp for the ability to flash multiple zips at once.
[Sprint Samsung Galaxy S III] Frostacious:
Twrp
[Sprint Samsung Galaxy S III] CNexus:
I live the features of TWRP...but I prefer the UI of CWM. There should be a version/splinter recovery that merges the two ;)
[Sprint Samsung Galaxy S III] Keith Patrick:
I have used both and I prefer TWRP because it plays nicer with the ROM I'm using.
[Sprint Samsung Galaxy S III] rando991:
TWRP because of the smaller backups, it's ability to name the backup, and most of all NO BLOBS. Would consider going back to CWM if a future version removed Blobs.
[Sprint Samsung Galaxy S III] wallythander:
I prefer TWRP but honestly not for any particular reason. I used neither on my Evo 4G, and I used both on my Touchpad. The features that TWRP has that CWM doesn't are kinda insignificant, but I like them, so I am going to stick with TWRP.
[Sprint Samsung Galaxy S III] tim5889:
Can you elaborate on what these "blobs" are? I've never had an issue with either, but I personally like TWRP a little better. I remember back in the og EVO days I had CWM because you could use it with ROM manager and flash from within android (i.e. you didn't have to boot to recovery first), but it seems that they're all able to do this now through one app or another. But whichever you choose, I'd go with the touch version... pretty nifty when you don't have to use volume rocker and power keys :)
[Sprint Samsung Galaxy S III] orlzzt:
My phone must be a "litter mate" to the one used by [MENTION=4169204]edfunkycold[/MENTION]. Didn't like TWRP. I personally like TWRP on my Nexus 7. I just couldn't get my GS3 to digest it.

Oh, and WTF is a "blob"?

Sent from my SPH-L710 using Xparent Skyblue Tapatalk 2
[Sprint Samsung Galaxy S III] Viper32:
TWRP all the way for me......... Enough Said ;)

Viper
[Sprint Samsung Galaxy S III] Whiplashh:
On the older clockwork mod recovery for the s3, you would make a backup.

Using a file explorer you could go to where your backups where, and clicked on one. There would be 2 folders inside the backup you chose. One would say something (I forgot, haven't used CWM in awhile) and the other said "blobs". When it backed up, it backed up into blobs which put like thousands of files in it. I don't know why but it did. It was needed for backup but took space and a longer time to delete because there was so many files.

------------------------

Sprint Galaxy S3 "Supernexus"

Whiplashh Rom

Look it up. :D
[Sprint Samsung Galaxy S III] spiderSWIL:
+1

And I don't know what blobs are, but it doesn't sound good.
[Sprint Samsung Galaxy S III] :
I like twrp but have had data issues with newer releases, have gone back to cwm
[Sprint Samsung Galaxy S III] NickTheFNicon:
I started off a while back on CWM but moved to TWRP on my Gnex and just stayed with it. The multi zip support is nice.

:good:
[Sprint Samsung Galaxy S III] J. Terrell:
I loved cwm when I had my Samsung admire. I got an Evo 4g, tried twrp and never looked back.
[Sprint Samsung Galaxy S III] thepennster:
I've had some bad flashes with CWM. TWRP has never done me wrong. As others stated, multi zip support is super nice!
[Sprint Samsung Galaxy S III] alaman68:
sounds like a job for Smelkus.

TWRP for me, and has been since it was released for the GS3.
[Sprint Samsung Galaxy S III] NickTheFNicon:
Completely spoiled on multi zip support.
[Sprint Samsung Galaxy S III] bigpappags3:
I use both. I downloaded the aroma installer that CNexus set up and just switch when I want.
[Android Q&A, Help & Troubleshooting] ryanspacef:
Hey guys,

This is my first time developing apps for a device, please don't be too callous.

Prior to the release of Android Studio I was having a crack at eclipse with the android SDK and attempting to utilise the AVD simulator rather than the actual Galaxy Nexus I have right beside me. My issue was in fact the same as to when I converted to Android Studio, a rather consistent error:

Waiting for device.
C:\Android\android-studio\sdk\tools\emulator.exe -avd GalaxyNexus -netspeed full -netdelay none

Device connected: emulator-5554
Device is online: emulator-5554
Target device: emulator-5554 (GalaxyNexus)
Uploading file
local path: C:\Ryan\Android\MyFirstApp\build\apk\MyFirstApp-debug-unaligned.apk
remote path: /data/local/tmp/com.example.myfirstapp
Adb Transfer Protocol Error.
No such file or directory

The AVD Simulator boots up, Android Labels displays then fails after a matter of seconds. i understand the issue is obviously not related to the IDE hence why both eclipse and Android Studio are doing the same thing.

I Created an AVD with the following Properties:

Name: GalaxyNexus
Device: Galaxy Nexus (4.65"...etc
Target: Android 4.2.2 - API Level 17
CPU/ABI: greyed out as "ARM..."etc
Keyboard enabled
Skin enabled
Front Camera None
Rear Camera None
Memory options
- Ram: 512
- VM Heap: 64
- Internal Storage: 8 GiB
- SD 128MiB
Emulation options both left unchecked
Greyed out button for "Override the extisting AVD with the same name"

The basic default hello world app actually runs fine on my galaxy nexus on 4.2.2.

Not sure of my issue, I would assume configuration, though couldn't be sure.

Thanks ahead.
[Android Q&A, Help & Troubleshooting] Remenic:
Go to SDK Manager and hit the Install button. Mine still had 5 missing packages, including the ARM ABI, which would also explain why the AVD didn't boot. Hope this helps.
[Android Q&A, Help & Troubleshooting] tes4p00ner:
Have you tried to push your apps apk manually using the adb push command? If that does not work its probably a driver issue. Also you may try changing the sdcard size to >200mb or removing it altogether and only using internal. I would also use a much smaller internal size unless your app needs it. My AVD has an internal of 256mb and no sdcard and runs fine. The AVDs are very picky and have strange issues sometimes.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] GNU:
Hi!

I've got a pre-production version of the Qtek 9090.

The ROM version was 0.9x something and I had some troubles with it so I figured I would just update it... Shouldn't have done that :cry:

Anyway, I got hold of a strange update file, called "HA_RUU_12100_112_00125.exe" and ran it on my PC. Not that bright, one might think :?

The device would not fully boot up. I then took out the battery and waited a coupple of minutes. After that it booted up nicely. However, the device is not fully functional and when I look in the "Device Information" it says:

ROM version: 1.21.00 WWE

ROM date: 07/28/04

Radio version: DM FAIL

Protocol version: DM FAIL

PRL version: N/A

ExtROM version: 1.21.112 WWE

I've tried upgrading it using all the tools and instructions that I could find on this great forum but with no luck..

The DeviceData app brings back a strange txt-file that looks a bit like this:

PH20A1 A 1 WWE E [and some strange characters] 1.21.00 0 0 1.21.112 DM FAIL

I would be VERY grateful if someone could help me back to a fully functional device!!
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] GNU:
Bump!

!!!Help!!!
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] Guest:
so, why don't you just try using a non-strange file to upgrade your device then?
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] GNU:
Help!

I am, you know! :lol:
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] Guest:
maybe upgrading the radio stack using the SD method would solve your issue, however, you'll need an SD backup of a working Radio rom for this.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] M4io:
there is a 1.06.01_sd_img.rar (german i think)

and a NTRW_ImageQtec9090.rar (no idea which language)

on the ftp
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] GNU:
THANK YOU!!!

I'll give a try right away!

What does the "NTRW"-file do?

Can I upgrade the radio stack without any 120-errors?
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] GNU:
A quick question:

Do a use Winhex or some other tool to copy the data to the SD card?
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] GNU:
To be more specific:

What tools do you use to copy the .nb1 file to the SD card?
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] Guest:
Help!
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] cruisin-thru:
xdatools is used to program sd cards with rom image.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] GNU:
I've tried the version of XDATools that I found on Jeff Summers page. It says "Invalid file size" and that the image should be a certain size. The Radiostack is not that size..

Anyone?!
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] hampers:
Getting Image on XDA III / PDA2k from SD

Just use "ntrw.exe" - search forum for location. That runs in DOS and will copy the .nb1 image you can get from the ftp to an SD card in one command. Insert card/enter bootloader and it worked for me (but not the radio as it hung there - i also have a pre production model)

chris
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] GNU:
I've got the 2.03 version of the Bootloader and it will not detect the card...

Do you know how I can upgrade it?
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] hampers:
Strange - I had 2.03 too - but after I applied the 1.06....sd_img file from ftp it uploaded to 2.05 - so i was in the same position as you and got it working.

I am not 100% sure it was that file i tried first - it might have been

ntrw_imageQtec9090.rar also in the ftp archives.

Either way I do find some images dont work - so i also found and used psdwrite.exe and that seemed to work when writing images using ntrw.exe did not. I am sure there is something else wrong- but find that between these 2 I can create bootable Sd images that at least get the device up and running.

I am still struggling to upgrade the radio stack - as with the 0.9x version none of the "mainstream" upgrades work - they all fail complaining about the radio stack version.

Good luck - i think you must be close!
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] GNU:
Thank you Hampers!

Progress! I got the Bootloader to accept the Qtec.nb1. It takes about 40seconds before it reacts and after that it says:

"

SD Download

=========

Selection=1

Not allow

update!

"

Quite strange, don't you think?!
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] katsj:
Just make a copy of your 9090's ROM with romupdate.exe and ntrw and copy the firtst 416 bytes from that to the image file you are trying to flash by overwriting them. Then it will allow the update
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] GNU:
I would like to but when I give the command "d2s", it runs a checksum test, starts to copy and finally fails with the message "Add record is error!" (Even I speak better English than that :))

The SD card now contains a bit of information from my Qtek. When I try to re-flash it with this information it returns the same message as usual; "Sections=1 Not allow update!" :cry:
[HTC Desire S] rkumbhar:
please some one develop sony xperia rom for htc desire s ?
[HTC Desire S] rain987:
Doesn't anyone read the guidelines about posting nowadays?

From my DesireDS
[HTC Desire S] wildstang83:
Do not post question threads in development forums. Thread moved.
[HTC Desire S] zenesis:
not here. Ask someone from the FreeXperia Project.
[HTC Desire S] nikhilmulay:
Check it out here http://xdaforums.com/showthread.php?t=2336845
[Galaxy S 4 Q&A, Help & Troubleshooting] stevep:
Hi All

I know this has been discussed quite a few times before in other posts, but the offered solution doesn't seem to apply to my new S4.

I want to 'find' the music that I've downloaded from the Google Play Music app. I've clicked on the little map pin icon in the app and I can see the track downloading. However when I go to the 'Android/Data/com.google.android.music/cache' or 'Android/Data/com.google.android.music/files' (depending on which post you read), the track ISN''T there. I've repeated the download exercise a number of times, but still can't find the music.

Anyone know what I'm doing wrong?

Thanks
[Galaxy S 4 Q&A, Help & Troubleshooting] okty2k:
you are not doing anything. I assume our friends from google have hidden the file well. :)

I have the same issue: the pin is orange (so the file should be on the phone), but it is nowhere to be found. music player does not find it either..
[Galaxy S 4 Q&A, Help & Troubleshooting] stevep:
The bizarre thing is I *can* see the track in the Google Play Music app
[Galaxy S 4 Q&A, Help & Troubleshooting] okty2k:
Also, if you search the file, is nowhere to be found....
[Galaxy S 4 Q&A, Help & Troubleshooting] stevep:
Yes, searching for it doesn't find anything either - weird!
[Galaxy S 4 Q&A, Help & Troubleshooting] Xxul:
i can see the files (their names are numbers) but i cant play them in ANY player (unsupported format, even if it clearly says .mp3) and on the pc aswell. Ideas?

I have All Access n google music
[Samsung Galaxy Nexus] jack_light:
Do you think that the galaxy nexus will still be updated to android 4.3 and 5.0?
[Samsung Galaxy Nexus] slayr76:
Definitely get 4.3 with gnex as its still jellybean an its not exactly a major update just a couple of tweaks here an there, why would they discontinue the jellybean updates with the gnex while we are already on jellybean that's just stupid as for android 5 i seriously doubt we will get it.
[Samsung Galaxy Nexus] rrohanjs:
i think we will get 5.0 also since majority of the phones in the market are still on gb and ics and single core phones, ours is still dual core and i feel its got enough juice to run the future os versions
[Samsung Galaxy Nexus] Bozosniper:
I think the nexus 4 and 7 will get the 5.0 update, for the galaxy nexus probably only 4.3 hopefully also 5.0

Sent from my Samsung Galaxy Nexus i9250 with Tapatalk 2
[Samsung Galaxy Nexus] Gangstaboyjr:
Hey man, how are you? I'm kind of new to this thread so I'm sorry if this question already exists. Ok so I bought my galaxy nexus in South Korea and now I'm in Mozambique, In Africa and I am on android 4.1.2 and I don't get notifications to update to 4.3 and when I go to check for update it says your phone is up to date, could you please help me? Thanks :fingers-crossed: oh and I got the phone like 3-4 months ago
[Samsung Galaxy Nexus] mrgnex:
Flash the Factory image via fastboot. Search for a way to do it with not losing your data.
[AT&T Samsung Galaxy S II SGH-I777] Gluesuf:
I really prefer to use my menu button as recent apps (long press for menu), and just have the 3-button overflow menu in app. At the same time, I'd much rather use a stock Samsung rom. It seems the only way to get this feature is to flash a CM based rom. Is there anyway around this?

Alternatively; is there a way to disable capacitive buttons in a rom completely? (Makes it easier to use PIE)
[Verizon Samsung Galaxy Note II] h311sdr0id:
[ROM][ODEX]☆★ProjectOdex★☆| NEW 350MB | For You ODEX Lovers Who Want MODs!! | ☆

ProjectOdex VRAMC3

​

For All You ODEX Lovers​

ALTERNATIVE

NEW STRIPPED DOWN 350MB ROM NOW AVAILABLE

(SEE BELOW)

[CENTER][B][SIZE="4"][COLOR="Blue"]PLEASE RATE THE THREAD "5 STARS" AND "NEWSWORTHY"[/COLOR]
[SIZE="4"]TO SUPPORT[/SIZE]
[COLOR="Red"][SIZE="5"]ProjectOdex[/COLOR] and it's further [COLOR="Red"]Development[/SIZE][/COLOR][/SIZE][/B][/CENTER]

Features:

- Stock-Rooted Odexed ROM

- Built from new sources created by h311sdr0id

- Lidroid/Wanam 23-Toggle MOD

- LidroidSettings/AdvanceOS App (for 23-Toggle MOD)

- CRT-OFF Animation

- 4-Way Reboot Menu

- Init.d Support

- Unsecure boot.img

- Stock International Boot Animations

- Busybox

- Bash and Nano

- Nothing Else Removed

ProjectOdex "RallyStock" (De-Bloated 400-500MB ROM coming in the next few days)​

Directions:

- Download

- Wipe Data/Cache//Dalvik/Factory Reset

(Make Sure To Wipe Everything.. ESPECIALLY When Coming From A DEODEXED ROM)

- Flash

- Reboot

ProjectOdex is committed to preserving the Odex's Reliability and Speed, but also giving you the MODs that you want from a Deodexed ROM.

Source is on Github under "h311sdr0id"

More info tomorrow. Internet went out, and I only have 2G where I am at currently :(

Enjoy

Credits:

- lidroid for creating the Toggles

- wanam for porting the toggles to the N7100

-

ALOT OF HARD WORK AND HOURS WENT INTO THIS

PLEASE

HIT MY THANKS BUTTON (ITS FREE)​

-

-
[Verizon Samsung Galaxy Note II] ganggreen777:
Reserved?
[Verizon Samsung Galaxy Note II] andrewjt19:
Awesome. Love the speed of odexed ROM s but usually it's a trade off for mods. This looks promising.
[Verizon Samsung Galaxy Note II] h311sdr0id:
Please give it a whirl and let me know. I use it as my daily driver and have been for a couple weeks. I just

decided I would share it last night, but have had it for awhile. Thanks Brother.

-h311sdr0id
[Verizon Samsung Galaxy Note II] gnex0422:
Ill definitely give it a shot when I get home from work....curious to see how it goes!
[Verizon Samsung Galaxy Note II] andrewjt19:
Likewise.... Will definitely report back.
[Verizon Samsung Galaxy Note II] littleguevara:
This looks very promising. I'm definitely flashing the lightweight version when that drops
[Verizon Samsung Galaxy Note II] killa408shark:
I'll flash it when I get home :D
[Verizon Samsung Galaxy Note II] kisypher:
definitely going to try this.
[Verizon Samsung Galaxy Note II] andrewjt19:
Is anyone else having issues downloading? I've tried twice and it's some sort of file that's only 147kb. Will try it in the computer...
[Verizon Samsung Galaxy Note II] dawiseguy77:
Would love to try but I love real icon theme too much. Thanks for the ROM though maybe someday I'll try it.
[Verizon Samsung Galaxy Note II] h311sdr0id:
I uploaded it to my site. No ADs or wait-time ;)
[Verizon Samsung Galaxy Note II] Jimjk1968:
Booted up, running great, gps working what more can a guy want in a rom that just posted today. :)
[Verizon Samsung Galaxy Note II] h311sdr0id:
Just an FYI about the CRT-OFF Animation. Like most of the other CRT-OFF MODs, it is a little tricky for some users. From what I see, you need to have Auto-Brightness OFF for it to work properly. I also heard that sometimes you need to be connected to WiFi as well for it to work. I never use Auto-Brightness, nor am I ever disconnected from the internet (thanks to Verizon forcing us all to give up our unlimited data plans---> is there an emoticon for a middle finger?), so I never have issues with the CRT-OFF.
[Verizon Samsung Galaxy Note II] Jimjk1968:
I never use auto brightness either and I always just choose to tell Verizon "to go **** themselves" and then I pay my bill and move on. :D
[Verizon Samsung Galaxy Note II] onemotodroid:
Adding native tethering to this ROM and removing bloat would be great.

Trying to wait for the reduce size build of this ROM.
[Verizon Samsung Galaxy Note II] andrewjt19:
Downloaded with no problems- flashing now (wet pants).:silly:

---------- Post added at 01:36 PM ---------- Previous post was at 01:35 PM ----------

+1
[Verizon Samsung Galaxy Note II] franklin270h:
Out of curiosity does this one remove the WiFi nag notification as well? Just didn't see it mentioned in OP
[Verizon Samsung Galaxy Note II] LexusBrian400:
Downloading and flashing now. Thanks.

Love odex roms. I don't theme anything so I never cared about deodexing.
[Verizon Samsung Galaxy Note II] h311sdr0id:
Suggestions are what I need for the next release. I will make sure to include this.