yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] topherk:
It's been a long time since I've dealt with custom recoveries, but I believe that's just the normal background for it. It's like you're tinkering with the inner working of an Android (wiping cache, etc), so you've opened up the green robot.

That's what I recall from when I still had stock about 9 months ago...
[Sprint Samsung Galaxy S III] CNexus:
If it shows up like that, that means you have the stock recovery...use GooManager or Rom Manager to install a custom recovery while booted up.

Sent from my buttered S3
[Sprint Samsung Galaxy S III] internetpilot:
Hmmm...any other time I've been in a stock recovery, I remember the Android being standing with that spinning wireframe in front of him. that's what displays when I successfully wipe the cache. Maybe I'm just remembering wrong and I'm being paranoid since I'm still deep in issues with being able to install a working custom recovery.

Hey, I'd love to install a custom recovery via GooManager or ROM Manager, but none of the custom recoveries are working on my SG3's. Nothing will mount so I'm stuck with stock recovery until someone more knowledgeable than me figures outwhat Sprint and/or Samsung did with the latest SG3's.
[Sprint Samsung Galaxy S III] flastnoles11:
I don't know why you're having these problems but the newest update (md4) roots exactly like any other software on the s3... I and many have done it plenty of times, it roots exactly the same way... Not sure why your recovery won't mount anything but somebody else also had this problem just today... You could always try to Odin in an earlier build (lj7 maybe) and try to root from there

“It is said that power corrupts, but actually it's more true that power attracts the corruptible. The sane are usually attracted by other things than power."” ― David Brin
[Sprint Samsung Galaxy S III] internetpilot:
I think something changed on the newest batch of S3's. I'm sure the OTA S3's are still rootable with this method but for some reason the brand new ones aren't. I've found at least a dozen other people complaining about the same thing only with brand new S3's.

Unfortunately I had a limited window of time to root these two phones and get them set up before going on vacation, so the phones are in use now and there's no way to backup and restore the existing configuration, data, etc.without like a day of downtime and basically starting over. And even then it's not a sure thing that reverting to an older stock ROM will work. I'll just wait for someone to figure it out and then root the phones later.

But there's definitely something new going on here. Its happening to too many people now. At least my sanity is confirmed!
[Sprint Samsung Galaxy S III] flastnoles11:
When you decide to root again here is a prerooted Odin build for mc3, after successfully flashing via Odin you will be rooted and can flash up to md4 from there... There is a prerooted that wipes everything and one that wipes and restores, make sure you read carefully and flash the one you need http://www.sxtpdevelopers.com/showthread.php?t=207

“It is said that power corrupts, but actually it's more true that power attracts the corruptible. The sane are usually attracted by other things than power."” ― David Brin
[Sprint Samsung Galaxy S III] internetpilot:
Thanks for this. I'm not going to attempt root again until I can get a working custom recovery going.
[Sprint Samsung Galaxy S III] flastnoles11:
That build will do it all.. It is prerooted, includes the custom recovery... Just like flashing a custom rom with recovery except you do it with Odin
[Sprint Samsung Galaxy S III] internetpilot:
Hmmm...but I wonder if that will end up with a working recovery or if I'll be in the same boat I am now, but with an older stock ROM?

I'm just really hesitant to try anything until someone figures out what Sprint/Samsung did with this latest batch of S3's. It's probably something relatively simple to overcome, but I'm not mobile tech enough to even guess what that is. I can't really end up with sons' new phones bricked (even soft bricked).
[Sprint Samsung Galaxy S III] flastnoles11:
You may be waiting a long time then since most devs either already have the phone or have already moved to other phones... Unless a Dev happens to pick one up with the same problems you're probably S.o.l... And I'm 95%sure they didn't change anything, some phones just have issues on certain builds, there have been plenty of people the last month and even the last week reporting successfully rooting with the same method you used...

You really have nothing to lose, if it doesnt work you can just Odin full stock and be in the exact same place you are now
[Sprint Samsung Galaxy S III] internetpilot:
True. I always forget the Odin option for when recovery fails. But I'd be without the data and current configuration (basically starting from scratch).

In the last two days I've seen posts from over a dozen people now who are encountering this issue with brand new Sprint S3's. I'm kinda hoping more and more people encounter this problem increasing the chances of it being resolved... Haha
[Sprint Samsung Galaxy S III] Ragnar:
It doesn't matter once your rooted and booted all you do us download either rom Manager or goo manager and install the custom recovery of your choice from the running phone. Doesn't get any easier.

Sent from the future via Tapatalk 4
[Sprint Samsung Galaxy S III] internetpilot:
Until the custom recovery can't mount anything, which is the problem I'm having now. I've tried numerous versions of CWM and TWRP and none of them can mount anything on these phones so they're useless. I'm not sure how reverting back to an older stock ROM will change that...?
[Sprint Samsung Galaxy S III] Ragnar:
Because you yourself feel the bootloader is the issue. If you Odin the stock tar of a previous version then that loads a previous bootloader. Pretty simple huh? I rooted 2 S3 last week brand new and did not have a single issue both where on the latest md4 right out of the box. I don't understand how you and that other person both ran into the same issue on the same day. It's really weird and like everyone else said and I just experienced just a week ago thousands of people have rooted on the latest version on brand new devices. Unless you guys are getting refurbs which by accident the bootloader has been locked.

Sent from the future via Tapatalk 4
[Sprint Samsung Galaxy S III] deutscher3891:
Flashing back to an older stock rom doesn't work either. I flashed to a 4.1.1 stock rom and followed the method for CF-Root and The Easiest Way to Root and neither of them allowed a custom recovery to mount anything.
[Sprint Samsung Galaxy S III] internetpilot:
Thank you for trying that as I couldn't because I'm on vacation with the two phones in use. Well that sucks that it didn't work. I'm a retired career network engineer, so I'm not a non-tech, but I'm also not the most tech person with regard to mobile phones. Even so, I can't figure this one out so it's probably not something obvious. Also, on XDA and other forums I'm up to about 18 different people who have now encountered this on very new Sprint S3's.
[Sprint Samsung Galaxy S III] deutscher3891:
Did you purchase your phones from Sprint directly? I purchased mine through Wirefly. Thinking I may send it back for exchange and pray like heck I get one that works. I am definitely a Vanilla Android person. Touchwiz is not my cup o tea.

Enjoy your vacation, as much as you can. Us tech nerds can never get it off the mind when something isn't working. Lol
[Sprint Samsung Galaxy S III] lvpre:
I purchased two s3 phones from Amazon about a month ago and haven't had any issues. Both are rooted too. The root process is pretty simple. Have you tried the unified toolkit also? Another easy method.
[Sprint Samsung Galaxy S III] internetpilot:
Both directly from Sprint.

The problem isn't really root. Depending on the method, we can get root. It's the custom recovery that's the problem -- it can't mount anything so you can't flash anything, backup, wipe, etc via recovery.
[Sprint Samsung Galaxy S III] jakkyl:
same problem here. I was able to root it, but when I go into recovery, it can't mount anything.

tried CWM, TWRP, and stock recovery - all the same.

Just got this phone yesterday, came with MD4 loaded.

I tried flastnoles11's link; that gave me root, but no luck with the recovery working.
[Sprint Samsung Galaxy S III] milky1112:
[MENTION=4645794]CNexus[/MENTION] is working on a custom recovery to fix this issue. It's known that Newer S3's will not allow mounting of anything in TWRP or CWM. Here's the threads with more info.

http://xdaforums.com/showthread.php?t=1809307 FOR TWRP

http://xdaforums.com/showthread.php?t=2183910 FOR CWM ---Last couple post show info.. So far nothing yet, but have Logs on them.

It's being looked into. Just hang in there folks.
[Sprint Samsung Galaxy S III] jakkyl:
Thanks. Nice to know it is recognized and being worked on.

I just bought this phone off of eBay, thought maybe it was borked.

I'm now subscribed to that thread.
[Sprint Samsung Galaxy S III] internetpilot:
Do you (or anyone -- feel free to chime in here ;)) know if there is a prerooted Odin build for MD4 anywhere? I've searched but have only found flashable zips. The only Odin build I've found is for MC4 and I really don't want to downgrade with no means available to upgrade again.

I figured while I was waiting for the recovery debacle to get resolved, I might as well get my two sons' phones up and going with some rooted basics like Titanium Backup and get some of their game data restored over from their Nook Color "tablets".
[Sprint Samsung Galaxy S III] KennyG123:
Please follow CWM and TWRP threads in development for progress on this issue

Thanks

FNM
[Nexus S General] Ted Mosby:
There was no opened thread for stable release of CM 10.1, so i opened it. I haven't installed it yet, is there any major bugs? Has RAM management got any better since RC2?
[Nexus S General] Killasmoke:
Yes stable version CM10.1.2 is very good try it out! :)
[Nexus S General] Ted Mosby:
It's very good, i'm testing it right now, very fluid, nice faster animations. I really like new polished CM apps, like Apollo and Trebuchet. cLock and cLock widget are also awesome.
[Nexus S General] dark'em:
Default CM kernel?
[Nexus S General] nexususer:
flash latest devil kernel and u will know what fast is :P :D
[Nexus S General] Ted Mosby:
Yes, default kernel. I am going to try Devil kernel, I have heard numerous recommendations for it. Also I am running this ROM with Greenify like CM10.
[Nexus S General] nexususer:
you can also try marmite for it but if can compromise a bit of battery for awesome performance u can use devil kernel if no then marmite is a good balance between battery and performance
[Nexus S General] Ted Mosby:
I'm reaching 72 hours uptime mark and RAM manager has started to act up. I occasionally feel lag and unresponsiveness when switching apps. Battery time is very good, 2 hours and 45 minutes of Display time, mostly browsing on low signal 3G (l'm on vacation), That's around what I'm getting on CM10 so it's pretty good for me.

I wish I have stronger Nexus device to run this ROM to it's full potential :)
[Nexus S General] Gambler_3:
Its the best rom ever for the nexus S, for the first time ever I have been able to populate my homescreens with lots and lots of widgets and yet it doesnt lag at all with scrolling. And the atrocious ram usage of the RC roms has been fixed with the stable, I can keep my phone running for a few days without any serious issues. This really gives almost new life to the nexus S just make sure you are using greenify.
[Nexus S General] Xuzuno:
Has anyone else not been able to get some apps to connect via 3G with this rom? They all seem to work fine on Wi-Fi, it's just with 3G that I'm having problems.
[Nexus S General] rho57:
I experience crashes when playing videos using software decoding in MX player. The nightlies also have this problem.

Sent from my Nexus S
[Nexus S General] itline:
One question, if i flash another custom kernel on cm 10.1, will i lose any of my data?
[Nexus S General] nexususer:
no .. but remember to clear dalvik cache before flashing
[Nexus S General] Nuclear_Geko:
The stable ROM has exactly the same problems as the previous nightlies (I've installed with full format of cache, data, system, dalvik, whatever):

- after few days it becomes laggish

- unreliable, happends to reboot itself. You can't even get to unlock screen sometimes; it happends even if somebody is calling you and you can't get to answer the phone

- do not use Chrome Browser otherwise it gets even worse

- if you use Swype keyboard the overall performance seems to be worse. With standard Keyboard it gets a little snappier but nothing that could be catalogued as "fine"

- people says it's cool because they keep the rom 1/2 days and then install nightlies or other stuff: when it's fresh from reboot it work fine, lots of free ram

- have more free ram by using Greenify but still the problems don't go away. It's overall heavier than a 4.1.2 (Which for some good reason Google made it as latest release for Nexus S)

- I've tried SlimBean with Thalamus Kernel and it's a little better for some stuff but basically the problems are much similar
[Nexus S General] Gambler_3:
What is the problem in giving it a reboot every few days? Nexus S has ALWAYS gotten slower even from the gingerbread days if you didnt reboot in ages.

I honestly think you should do a proper clean install because I really dont have that many problems as you say. 4.2.2 is the smoothest the nexus S has ever been, I am even running next launcher very smoothly and redraws are minimum. On 4.1.2 homescreen navigation was quite jittery with widgets and wallpaper scrolling, on 4.2.2 it literally fly's. That alone is enough reason for me to live with the slightly more ram usage.
[Nexus S General] Nuclear_Geko:
Never had these problems with earlier Android. The reboot proves what I'm saying: he can't be reliable for long run since its performances degrade automatically.

If you read what I wrote I said I made a full clean install: wiped data, factory, dalvik, formatted data, formatted system.
[Nexus S General] Killasmoke:
Everything running great only problem is the GPS bug with Google Maps after exiting the app & turning off GPS for some reason GPS won't turn off only a reboot fixes it but other than that 10.1.2 stable is really great :)
[Nexus S General] nolook:
running it has been really reliable but I do have ram issues even while using greenify... CPU on conservative mode too

is everybody's lock widgets OK? I seem to get a lot of wonkyness with pocketcasts,etc...

Sent from my Nexus 7 2
[Nexus S General] itline:
Here you are http://www.mediafire.com/?z9ch7hna57pm5ak
[Nexus S General] mariosg71:
i have it in htc explorer and i cant install play store..besides that it is very good
[Nexus S General] vitaumtb:
I've benn using it since the stable release so it's been almost 2 months. I had RC only twice. The lock screen for some reason bugs sometimes if I use marmite kernel, but with its own kernel I didn't have problems. The ram usage has got a lot better with facebook, fb messenger and google maps greenified, I didn't greenify whatsup, snapchat or viber but It's working flawlessly. For some unknown reason once in a while it bugs completely(maybe after 5-6 days) then I reboot it and its all gone. I'm totally sure this rom is more stable than rasbeanjelly and jellyshot, I used then for a while too. One of the best roms I used so far. 10.1.2 made it a lot more stable also. Battery life had better in the RCs but I find it ok, maybe 3 hours with screen on, for me is fine.
[Nexus S General] songwvq:
I have heard numerous recommendations for it.
[Nexus S General] rafaymalik:
You can give hellybean 4.2.2 a try its based cm10.1 and is rock stable. I personally used it for 2 to 3 months no reboots excellent performance with good mods.It uses devil kernal. good battery life to if not overclocked.
[Nexus S General] Gambler_3:
94 hours uptime and still going well.
[Nexus S General] cheeze.keyk:
download link of the cm10,1 please and what kernel best suits with this rom?

:angel:
[Nexus S General] mpw648:
http://get.cm/?device=crespo
[Nexus S General] hondysan:
WIFI issues

I installed this ROM yesterday and have quite some WIFI issues on it, in my house on places where all the other phones (Nexus $, Motorola DEFY and Tablets) have good wifi reception, the Nexus S has really very big drop outs in wifi...sometimes it has signal in few seconds it lsoes it to zero etc, very usntable, do you have problems like that too?
[Nexus S General] kick.apple.out:
Fix BT tethering

Bluetooth tethering Fix for Nexus S CM10.1.2 stable

Flash 2 attached files in recovery

Guide - [MENTION=4353291]steven676[/MENTION] (Huge thanks!)

http://xdaforums.com/showpost.php?p=44232711&postcount=123

http://github.com/steven676/android_device_samsung_crespo/commit/37dc5ba490ac3e1e61ff0c1b7a89fd2f5c3ad846
[Nexus S General] klusark:
The issue has been fixed in CM 10.1.3RC2. I would recommend that over this fix.
[Nexus S General] Dark_Eyes_:
Anyone tried latest cm10.2 nightlies? Then run great, especially with Marmite kernel. I would suggest to give it a shot!
[Nexus S General] esseti:
Hi all.

it's a couple of days that - randomly - the lock screen does not show the clock but a video (or at least the player of the videos).

see attached img.
[HTC Droid DNA] itzjen:
What radio version are you guys running ? I'm just curious to see if im running the same one as most of you vzw dna users ,kay thank you in advance :)
[HTC Droid DNA] finanandroid:
Base band or Radio Version for the DNA is 1.01.04.308 I suggest leave it alone, it work in all Roms
[HTC Droid DNA] rfarrah:
1.01.04.308 is the latest version. We haven't seen much movement in the radio department.
[HTC Droid DNA] itzjen:
I thought baseband and radio were the same thing silly me ,sorry guys
[HTC Droid DNA] rfarrah:
They are. We typically call the baseband version the radio.
[HTC Rezound] reallyneedshelp:
Hi everyone, I've seen you guys help out so many other people I figured I'd give it a try.

My HTC Rezound is not working. I can't charge the device while off. I can't start the phone (Flashes the HTC logo, screen goes dark for one second, then stays at the HTC logo. Luckily, I have an old Thunderbolt, I have been able to charge my battery through that, and access the bootloader using the power + vol down method.

I have never rooted my Rezound and have been using stock since I got it, here is what I see in my bootloader:

***LOCKED***

VIGOR PVT SHIP S-ON RL

HBOOT-2.28.0000

RADIO-2.23. 10. 0123R/2.23.10.0124R

OPENDSP-V14.6.0.7708.00.0507

EMMC-BOOT

SEP 20 2012, 17: 40: 22

Under that I see the regular Bootloader menu. I cannot use recovery, factory reset or clear storage, because it fails and I get the E: Can't mount /data/data/recovery/log error message. I tried downloading a PH98IMG.zip file, but when it tries to load it I get an error saying that the version on the phone is newer than the one on the SD card, and it won't update (Don't know if that's an issue with downloading things from before Sep 20 2012, but I havn't found anything post that). I can't use the RUU updater because my computer will not mount/ recognize my phone, I downloaded all the HTC sync stuff, and my computer beeps and says that there is something there, but it fails somewhere in the process and nothing sees it. I also tried to push it with ADB, but I get the same issues, CMD will ask me to attach the device and I can't get past it.

So that's where I am, I can get to my bootloader, but I can't do anything via the RUU exe, ph98IMG.zip file on an SD card, or ADB/Fastboot. I'm stuck.

I am willing to try anything, and will give any other information you guys need if you think you can help. Meanwhile I'm using my old cracked Thunderbolt that lost it's 4G capability, I feel dirty.

Please let me know if you can help! And thanks in advance!
[HTC Rezound] Flyhalf205:
If past your warranty or if you have no insurance on it. Go to the htcdev website and unlock the phone.
[HTC Rezound] mjones73:
The fact you've kept it stock and it won't let you get past hboot or the HTC screen and you can't do anything via hboot tells me it's dead.

You have the latest hboot, there is no RUU/firmware zip available to let you re-install everything clean.

You're probably gonna have to get it replaced.
[HTC Rezound] reallyneedshelp:
I was able to unlock it using the method on the htcdev website.... what can I do with it now? Bootloader looks the same, but says **UNLOCKED** at the top of the screen.
[HTC Rezound] Flyhalf205:
Download TWRP at http://xdaforums.com/attachment.php?attachmentid=2102623&d=1373341752

Extract the .zip and place the .img file in the same folder as fastboot. Use fastboot to flash it. The command is going to be fastboot flash recovery recovery.img

Once you done that. use command fastboot boot recovery.img

Go to backup and create a backup

After that finishes backing up. Download http://vp-zp.com/snuzzo/kernels/rezound/sense/Funky-Kernel-v3.7.3.zip and place it on your sdcard. You can mount your usb drive inside TWRP recovery.

After you have copied it over. Install that zip from the sdcard and it should go through the steps of being s-on since you are s-on. Then reboot phone
[HTC Rezound] reallyneedshelp:
When I ran fastboot boot recovery.img the phone when dark for a second, went back to the fastboot menu, but now at the top of the screen above ***UNLOCKED*** there is a *** TAMPERED*** but no recovery menu. Is this ok?

EDIT: I went into recovery and see the new menu. will update once finished.
[HTC Rezound] Flyhalf205:
That is fine saying TAMPERED. Just means you have something custom flashed. Hit the power button and go into HBOOT. Then select recovery in the list.

EDIT: Just saw you edited after I posted
[HTC Rezound] reallyneedshelp:
Ha! OK, now I'm done, but there was another problem. The installation failed. Here is what it said:

Funky Kernel

for

HTC Rezound

Funky-Kernel-v3.7.3

Linux upstream version : 3.0.87

Mounting /system

installing modules

file_getprop: failed to stat " /system/build.prop

E: Error executing updater binary in zip ' ?sdcard

Error flashing zip ' /sdcard/funky-kernel-v3.7.3

Updating partition details...

"E: Unable to mount" /cache

""/data

""/system

""/emmc

"" unable to mount internal storage

Am I done for?
[HTC Rezound] Flyhalf205:
You might be... :(
[HTC Rezound] reallyneedshelp:
Well, I sincerely appreciate the effort. It seems like the internal storage somehow got damaged, can't imagine how that happened. At least I have a thunderbolt to keep me until I find a new phone. It could be worse.

Thanks for the help!
[HTC Rezound] Flyhalf205:
Just out of curiosity. Did you try doing a Factory Reset in that white HBOOT screen before we started this process?
[HTC Rezound] reallyneedshelp:
Yeah, same as anything else, can't mount E.
[HTC Rezound] Uzephi:
In TWRP try to mount internal storage when plugged into a PC. See if formatting would work.
[HTC Rezound] reallyneedshelp:
Won't let me. Internal storage showing up as 0MB. :/
[HTC Rezound] Uzephi:
It doesn't sound like your internal storage is completely toast. You are able to boot into the hboot partition and the recovery partition, the others may be corrupt and reflashing the recent RUU may help. Try to s-off to be able to RUU recent and older RUU zips (stock IMGs)
[HTC Rezound] mjones73:
There's no recent RUU to flash, that's part of the problem, none came out for the OTA update and you also need a running rom installed to s-off.

OP - What happens if you try to format the partitions via TWRP?
[HTC Rezound] reallyneedshelp:
Won't mount anything to format, just will say can't read. I can however go through the file tree. Somehow the internal memory got semi-fried. I don't know what happened.
[HTC Rezound] E_Money915:
im having a very similar problem except none of my computers will recognize my phone so i cant re-unlock my bootloader any suggestions
[Samsung Galaxy Nexus] Dragn4rce:
Is there a modified version of it where its like the hangout app?

U can just slide out ur other conversation while ur in one instead of clicking that green happy face to ur ur list of conversationss?