yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] CNexus:
Well to explain what I *think* is the issue, first I have to explain recoveries and boot.img

Now most people think that the boot.img = the kernel. Unfortunately that is a common misconception. The boot.img actually has the following structure:

boot.img:

--ramdisk.cpio.gz

--zImage

Now the zImage is the actual compiled kernel. The ramdisk is a compressed set of files and binaries that specify things like the services that should be run once the phone starts up and their order, the permissions on different device directories (when I say device I mean input device, such as sensors and leds, etc), and other misc initialization

Now, the recovery.img has exactly the same structure. It also contains a ramdisk (with a couple more and removed files because it's a recovery) and a kernel (zImage).

Now this is where the odd stuff comes in. Why is it that these new devices are unable to mount storage even though they are flashing recoveries that contain the same kernel as our recoveries? So, no offense to [MENTION=4325945]ktoonsez[/MENTION] because his idea definitely worked, but I don't think it's so much FLAGS in the kernel as it is certain sequences that are present in the original recovery kernels. My theory about this is that the stock recovery kernel (the kernel inside the recovery that the rest of us are able to use fine) was calling some sort of sequence before actually mounting the storage. My hunch is that in the original recovery kernels there was something like a "randomMethodABC" function, which was supposed to debug something or other or some other misc function that had no bad effects on older devices, but in these newer devices they are made aware of this execution and so mount the storage differently/to some other location/using some other method than the normally would. I think the reason that swapping the recovery kernel with kts kernel works is because he disabled some sort of unnecessary call that has no ill effects on older devices, but triggers some sort of sequence that mounts the storage differently/prevents mounting altogether on these newer devices.

Anyway, that's what I think, or something to that effect. Because if it were really flags in the kernel, it still doesn't explain why the rest of us are able to use the exact same recoveries without issue, which leads me to think that the mounting problems are executed on the devices side.

ktoonsez I tagged you because I'd like to hear your thoughts on this :thumbup:
[Sprint Samsung Galaxy S III] Whiplashh:
Thank you guys, I see now. I wonder why they would make a change now WITHOUT notifying people.

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

Sprint Galaxy S3

Need Help? PM

Hit the "Thanks" button if I helped!
[Sprint Samsung Galaxy S III] KennyG123:
Because this change does not affect their 99% userbase that do not root AND because they really look at us rooters as bad seeds. I am sure there is a rev somewhere (not the ARM rev) that can differentiate these devices and hopefully someone will find it so we have a means of knowing which they are without trial, error and then the posted thread in Q&A.
[Sprint Samsung Galaxy S III] metayoshi:
Haha... As a firmware guy myself, I know that manufacturers make changes ALL THE TIME without notifying their customers whether it's the general user population or even an OEM. It fools OEMs and users into thinking they are getting the *exact* same product as before, but really, there is a small firmware or hardware change that they don't know about, and for the most part, it usually doesn't matter.
[Sprint Samsung Galaxy S III] ktoonsez:
It could very well be a sequence thing since they are always after new ways to screw us out of having fun with our phones. But here is what I believe is going on. These flags restrict rooting and can restrict mounting of anykind based on what code is added to the kernel based on these flags:

# Add rooting prevention

# CONFIG_SEC_RESTRICT_ROOTING is not set

# CONFIG_SEC_RESTRICT_SETUID is not set

# CONFIG_SEC_RESTRICT_FORK is not set

# CONFIG_SEC_RESTRICT_ROOTING_LOG is not set

With these flags and code applied within "#" tags can enforce any amount of restrictions that they want to. With kernel source of course it is very easy to get around unless they get even more sneaky and hide the code, like we found in the S4 for camera firmware updates (was restricted to only official kernels). Hope that helps out for the explanation :D :good: :highfive:
[Sprint Samsung Galaxy S III] CNexus:
Yes, but my idea is that even if those flags are there, it doesn't make sense for that to be it since they are using the same recovery kernel as the rest of us. We would see the same issue, no? The only difference between them using those recoveries and us using them is that they have newer devices
[Sprint Samsung Galaxy S III] ktoonsez:
No problem buddy, always fun working together :D :good:
[Sprint Samsung Galaxy S III] ktoonsez:
What I was getting at is that the main zImage is in control of the whole environment so if the zImage is packed with code to inhibit those kind of things the problem that exists is the result.
[Sprint Samsung Galaxy S III] CNexus:
But that's not true. The recovery has it's own zImage specifically for the recovery environment. It doesn't use the zImage stored in the boot partition.
[Sprint Samsung Galaxy S III] Ragnar:
Whatever it is that was done is also preventing these new devices from flashing AOSP style roms. Even with your modded recoveries these users are able to flash now TW roms but are unable to flash AOSP roms. It stops at the Sammy boot screen and doesn't go any further.

Sent from the future via Tapatalk 4
[Sprint Samsung Galaxy S III] ktoonsez:
That is true, I was under the impression that it did use the main boot zImage though to set everything up, but you know more about the recovery img than I do, i thought that the recovery was just a "rider" that obeyed the main. Guess its still a mystery, lol.
[Sprint Samsung Galaxy S III] bthorne79:
Now I know a bunch of us are from the og epic I am to think it is almost just like the el29 to el30 issue where you had to downgrade to get proper root and recovery. Now maybe a drop to lj7 or something like that than upgrade baseband after proper root and recovery
[Sprint Samsung Galaxy S III] Ragnar:
No that doesn't work at all. The modded recoveries is the only thing working right now which allows storage to mount.

Sent from the future via Tapatalk 4
[Sprint Samsung Galaxy S III] CNexus:
We tried it, even firmware from a year ago. No dice :\
[Sprint Samsung Galaxy S III] AproSamurai:
I'm late to this issue, but for those suffering from it, what Revision is your hardware?

(Genuinely curious.)
[Sprint Samsung Galaxy S III] CNexus:
Mixed reports from those with issues...most of this went down in the TWRP thread so you can read through that for the "most up to date coverage"

One person said rev 0 and the rest said rev 4, iirc
[Sprint Samsung Galaxy S III] bthorne79:
Same here I just found out yesterday
[Sprint Samsung Galaxy S III] AproSamurai:
Much appreciated. I'll check there. Thanks man. :)
[Sprint Samsung Galaxy S III] black2rob:
thanks [MENTION=3125148]kennyglass123[/MENTION] for this....
[Sprint Samsung Galaxy S III] ShadyM80:
Ok so after usuing Odin to get CWM tar and the SD mount issue due to having a newer S3 i just purchased a few days ago, I tried the other options (mod2) and now all my apps are gone but a few. When i click my camera it tells me not enought memory, or when i click gallery it tells me it stopped working. Any idea how i can get back to stock or preferably a CWM that will let me mount and flash?

Edit: I see all my apps are still on the phone (I think) when i went into settings>applications. However all of them have lost their icon and are now just a little green android fella using 0.00B. Not sure if my internal memory was corrupted or not after using Odin to get a custom recovery.
[Sprint Samsung Galaxy S III] madbat99:
Cwm is pretty bad, most of us on the s3 use philz touch recovery. And if you flashed a lollipop ROM, if you plan to go back to KitKat you must wipe internal SD (data/media) or you get problems like the one you're describing.
[Sprint Samsung Galaxy S III] ShadyM80:
Yea I just went into Kies and restored basically like i just opened. My issue at the moment is I can't even root because I cant find Philz anywhere to download and the others are blocked from installing from zip or something.
[Sprint Samsung Galaxy S III] madbat99:
Blocked from installing zip? You can't flash a zip in stock recovery if that's what you mean.

But I saved a .tar of philz if it helps. philz
[Sprint Samsung Galaxy S III] ShadyM80:
Yea the newer T versions from Boost. I read that they are trying to stop people from rooting/flashing. I might be wrong as im not too wise with all this, but i did read that after installing CWM and tring to install from zip (even after checking to see if its primary and fat32) nothing appears and you get the Can't mount /sd card/. I'm going to download you Philz zip though and i greatly appreciate you doing that. Probably saved me countless hours of forum digging for a download after he took it off Goo.
[Sprint Samsung Galaxy S III] KennyG123:
Not at all...just the kernel has changed and TWRP cannot keep up with older devices...they rely on maintainers to build for them.
[Sprint Samsung Galaxy S III] madbat99:
They aren't trying to stop anything. The older non t model s3 doesn't mount anything in twrp either. There is a special build by lrs121 for virgin and boost.

But the philz I gave you is a tar not a zip. So Odin.

You can get the image file of the proper twrp here
[Sprint Samsung Galaxy S III] ScottsDesk:
Hello

First thank you for taking the time to create a solution. If it works for someone even If it wont works for everyone, at least you did something.

I too do whatever I can to fix whatever I am able to.

I NEED a few questions If you can.

Will this work for:

SG Note 3 NEO LTE SM-N7505 Germany Android 5.1.1 (carrier open)

What recovery is recommended for the same device.

I run as my file/admin these 2 apps for pretty much everything so if it meshed with them would be a +++

Rom Toolbox Pro

ES File Manager Pro

My device is rooted CF Autoroot (SuperSu)

Your advice and a little ideal install steps to take would be much appreciated
[Sprint Samsung Galaxy S III] KennyG123:
If you can build the recovery from a modified stock image, then yes. If you mean the recovery posted in this thread, no. I do not believe the same thing happened to the Note 3 as did the Sprint S3. This was a rare hardware revision that caused the original recovery to stop working.
[Sprint Samsung Galaxy S III] KennyG123:
It was a team effort. [MENTION=4645794]CNexus[/MENTION] made the recovery, the real hard part!
[Sprint Samsung Galaxy S III] black2rob:
[MENTION=4645794]CNexus[/MENTION] [MENTION=3125148]kennyglass123[/MENTION] thanks for all your hard work. Now that we have this recovery I can flash TW Roms?
[Sprint Samsung Galaxy S III] KennyG123:
Absolutely!
[Sprint Samsung Galaxy S III] black2rob:
[MENTION=4645794]CNexus[/MENTION] [MENTION=3125148]kennyglass123[/MENTION] EXCELLENT.
[Sprint Samsung Galaxy S III] KennyG123:
Well it works on Noobnl's CM 10.1 and it does flash which means it is accessing storage but you are correct that there is some slight incompatibility somewhere. If this was the OG Epic 4G I would say it is because of the built in recovery that AOSP ROMs had there which over wrote the recovery used to flash it, but that is not done on the S3 right?

They mostly show rev 4 on the processor, which has been out for months with no such problem and still MD4 in the OS.
[Sprint Samsung Galaxy S III] bthorne79:
They mostly show rev 4 on the processor, which has been out for months with no such problem and still MD4 in the OS.[/QUOTE]

OK I have the rev4 and I have no issues with normal twrp or cwm so what is the issue
[Sprint Samsung Galaxy S III] jdelano:
There was a terminal command going around a few months back that displayed some internal version data, maybe that would help distinguish something about the newer S3s?

I'm trying to find the thread ...
[Sprint Samsung Galaxy S III] black2rob:
So not sure what happend but I went into recovery did a nand like always and went back to my stock rooted rom did some things on the phone did not like it so i went back to recovery and restored my back up. Tried to go to recovery and it was gone.......reflashed recovery again......
[Sprint Samsung Galaxy S III] CNexus:
Strange. And you are one of the people that had the mounting issues with the original recoveries, correct?

If and when that happens again, can you open up terminal emulator and run the following command and then upload the file it creates? Thanks

android@android $ su
root@android # dd if=/dev/block/mmcblk0p18 of=/sdcard/recov.img
[Sprint Samsung Galaxy S III] Capn069:
I don't mean to sound like a noob but will these recoveries work with the Boost Mobile S3? I had an S2E4GT and all the sprint stuff would work. If any information about the device is needed I can provide it.
[Sprint Samsung Galaxy S III] CNexus:
What's the model number?
[Sprint Samsung Galaxy S III] black2rob:
Yes that was me and yes as soon as I get home I will do that.
[Sprint Samsung Galaxy S III] Capn069:
Here's a screenshot showing all the device info:
[Sprint Samsung Galaxy S III] black2rob:
Sorry forgot to ask what title will the folder say or what should i look for?
[Sprint Samsung Galaxy S III] CNexus:
That will created a recov.img file on your internal storage (/sdcard)

---------- Post added at 06:25 PM ---------- Previous post was at 06:25 PM ----------

Ok, you're good, same model number.
[Sprint Samsung Galaxy S III] flagcitysteelers:
Mount is invisible in TWRP

I have a rev 4. It was manufactured in November 12 & refurbed in June 13.

Both TWRP mods appear to be missing the 'Mount' option after clicking Mounts from the main screen. The partitions are selected, but I don't see the Mount button. I first tried using FlashImageGui & then using ADB, same result with both methods. I was going to try CWM, but a little concerned that FlashImageGui will not allow it to flash. It has a toast message pop up saying to choose a compatible Kernel blah blah blah even though I had recovery image selected. I do have the issue of not being able to EVER mount storage from recovery. I thought it might be a driver issue until I ran into this thread. I also had previously flashed a 'recoveryswitcher' from

http://xdaforums.com/showthread.php?t=2274796&page=4 but at the time the Aroma installer was messed up & blank as well. I cancelled out of the install since I couldn't see what it was going to do.. I reflashed TWRP & haven't had any issues. Thoughts anyone?
[Sprint Samsung Galaxy S III] black2rob:
[MENTION=4645794]CNexus[/MENTION] heres the info you wanted. http://db.tt/YQezvFRV I had to do it as a zip file just open the file and inside is the info......hope this helps.
[Sprint Samsung Galaxy S III] cahiatt:
Man I wish I saw this thread last night. Reveiced my wife's GS3 yesterday from Sprint and had this exact issue. Would not mount internal or external memory in TWRP or CWM. Bricked it doing an ODIN downgrade but got it restored back to the latest again through ODIN a second time. Ended up using the Samsung GS3 toolkit to root, SU and recovery which finally worked.

Will try it on the other phone that is supposed to be coming tomorrow.
[Sprint Samsung Galaxy S III] black2rob:
root it with the tool kit and then odin the recovery from here and your good im using the TWRP odin recovery.
[Sprint Samsung Galaxy S III] duhgly:
hi,

i registered primarily to respond to this.

i have an S3 on the Boost network.

i originally (unsuccessfully) tried the rooting procedure the first day (Aug 6) i had the phone.

it didn't work.

fortunately i tripped over this thread.

i have now successfully rooted the S3 on Boost using the "Odin Package"

with the "TWRP Recovery Mod" ...

first try .... just like you read about.

i did not try the "CWM Recovery Mod".

Thank You all very much for the time and effort that you expend to make this possible.
[Sprint Samsung Galaxy S III] KennyG123:
Welcome to XDA and glad we can help! Hope you find more things to mod your phone the way you like!
[Sprint Samsung Galaxy S III] jmills17:
Still only flashes TW Based Roms

tried CWM mod 2 and it worked and I was able to flash TW based Roms only. After reading other post went back and used TWRP Odin and after that i'm still stuck with only being able to flash TW based Roms. Any suggestions? Anything other than TW based just sits on the Samsung splash screen.
[Sprint Samsung Galaxy S III] KennyG123:
None at this time. Only Noobnl's CM10.1 is booting. So it is something in the writes when flashing the others. Mind you these recoveries were a workaround to get these new phones to access storage and flash. They are not official recoveries. It will take an AOSP developer to find out what is different with the CM10.1 flash/boot sequence causing the issue then maybe the recovery zimage can be modified to fix that.
[Sprint Samsung Galaxy S III] black2rob:
[MENTION=3125148]kennyglass123[/MENTION] I posted the link that [MENTION=4645794]CNexus[/MENTION] needed not sure if he got it....I posted on here. Thanks.
[Sprint Samsung Galaxy S III] CNexus:
That file you posted, that was dumped right after your recovery was missing, correct? Not after you reflashed one of the modded recoveries?

Because I need a dump of it right after the next time it goes "missing".
[Sprint Samsung Galaxy S III] black2rob:
[MENTION=4645794]CNexus[/MENTION] Oh ok. Next time it goes missing i will do it again. Hopefully it does not.
[Sprint Samsung Galaxy S III] CNexus:
Ok, awesome
[Sprint Samsung Galaxy S III] KennyG123:
Has anyone with one of these phones tried flashing another AOSP kernel like Ktoonsez immediately after flashing the AOSP ROM while still in recovery? Had a conversation with [MENTION=912474]Dees_Troy[/MENTION] at XDA DevCon and he said if the recovery needed a new Zimage then the AOSP ROMs would need one too.
[Sprint Samsung Galaxy S III] Ragnar:
[MENTION=3125148]kennyglass123[/MENTION] if you guys take up a collection i will buy a new S3 so that I can test everything for you guys and give a full system dump. :D

Sent from the future via Tapatalk 4
[Sprint Samsung Galaxy S III] bthorne79:
What revision is needed and how do we now what phones have the issue I don't have a issue with aosp roms but I can't mount recovery to computer for access to storage

Sent from my GT-P3110
[Sprint Samsung Galaxy S III] KennyG123:
They are showing up as rev 4 still...so the actual change is documented somewhere else. Flashing standard CWM or TWRP you cannot access internal or external storage to flash anything at all. With the modified recoveries access to storage is now granted, TW ROMs flash fine but all but Noobnl's CM10.1 get stuck at boot screen. There is no current way to identify these new phones other than trying the original recoveries.

Your issue sounds like a driver problem.
[Sprint Samsung Galaxy S III] Ragnar:
The revision is unknown as they did not mark anything different on these new S3's. But storage won't mount in recovery so it becomes a problem. The modded recoveries in the OP here provide for these custom recoveries to work and mount storage while in recovery permitting users to flash. Herein lies the problem that users on these new phones are also unable to flash AOSP roms they boot as far as the samsung logo but no further. If we could get one of these users to try and flash an aosp rom and then flash Kt kernel for aosp and then trying to boot.

Edit: ninjad by the FNM

Sent from the future via Tapatalk 4
[Sprint Samsung Galaxy S III] bthorne79:
Ah OK I understand now what's going on
[Sprint Samsung Galaxy S III] TexasLTE:
LOL ... really ? .... "splain it to me like a 5 year old" (I'm just thankful I got my SGS3 in June before these newer problem phones came around) ...
[Sprint Samsung Galaxy S III] rwilco12:
It's kind of like they took your car and switched it from unleaded to diesel without telling you. They left all the stickers on that say unleaded so you have no clue. You go to the pump and fill up with unleaded but your car has issues as it now needs diesel. Until you figure out you need diesel it will always have issues but once you put diesel in it will work like a charm.

That's what Samsung/Sprint did to us. :(
[Sprint Samsung Galaxy S III] bthorne79:
Hey now I didn't know what was going on I just found out a few days ago. Lol I thought that it just couldn't mount storage to push files. Not flash darn Texas4g you didn't have to go there :D

Big derp

---------- Post added at 10:01 PM ---------- Previous post was at 09:59 PM ----------

But hey that's what I get for not reading I NOOBed it
[Sprint Samsung Galaxy S III] nidpancho:
I'll do it!

can you provide a link to the exact kt kernel you would like for me to use?

====================================

I tried to flash this kernel, http://xdaforums.com/showthread.php?t=1800576

same result :(
[Sprint Samsung Galaxy S III] KennyG123:
You chose the AOSP kernel not the TW kernel, right?
[Sprint Samsung Galaxy S III] nidpancho:
Yep. I chose the aosp 4.2 /Linux 3.4 kernel

---------- Post added at 07:37 AM ---------- Previous post was at 07:36 AM ----------

Yep*
[Sprint Samsung Galaxy S III] KennyG123:
Thanks for trying. Looks like those AOSP ROMs will need a kernel change.
[Sprint Samsung Galaxy S III] nidpancho:
for sure.

Like I've said before, the only AOSP rom that has allowed me to successfully boot has been this modded December 2012 nightly by [MENTION=2682982]noobnl[/MENTION]...

http://d-h.st/ZuI
[Sprint Samsung Galaxy S III] noobnl:
Whats modded in this version?
[Sprint Samsung Galaxy S III] KennyG123:
The better question is why does that boot but no other AOSP ROMs on these new S3s? Is there something different in the kernel?
[Sprint Samsung Galaxy S III] nidpancho:
noobnl! :D

I can't believe I had finally reached you! lol

What's modded in this version of the recoveries? You're going to have to ask [MENTION=3125148]kennyglass123[/MENTION] or [MENTION=4645794]CNexus[/MENTION].

As far as your modded nightly, http://xdaforums.com/showthread.php?t=2030660&page=27 (post #269)

according to your post you "fix(ed) boot screen hang"
[Sprint Samsung Galaxy S III] CNexus:
I swapped the recovery kernel inside the img files with kt kernel

I'll try flashing the missed recovery and then CM in a sec to see if it actually is just the recovery that is being odd somehow

Also [MENTION=5356084]nidpancho[/MENTION] try flashing one of the MOD 1 versions. It still mounts storage but it uses a 4.2.2 AOSP kernel so it does the 0 folder thing and that's why people were thinking that it doesn't mount storage...

Anyway, flash that, reboot recovery, then flash a CM rom (make sure it's on your external sdcard or else the recovery won't see it since it's looking inside /sdcard/0/
[Sprint Samsung Galaxy S III] nidpancho:
it didn't mount storage for me before. I will try it though.
[Sprint Samsung Galaxy S III] CNexus:
I tested them and then noticed that it did mount storage but it did the 0 folder thing

Couple other people with these newer ones said the same
[Sprint Samsung Galaxy S III] nidpancho:
can't mount. Are the ODIN and one clicks using mod 1 or 2?
[Sprint Samsung Galaxy S III] CNexus:
Mod 2

Are you sure? That's odd..
[Sprint Samsung Galaxy S III] nidpancho:
yup tried both twrp and cwm mod, only mod 2 works for me for some reason.

does the kernel vary between them?
[Sprint Samsung Galaxy S III] CNexus:
Yeah, MOD 1 has the AOSP 4.2.2 kernel and MOD 2 has kt tw kernel
[Sprint Samsung Galaxy S III] nidpancho:
I wonder what kernel [MENTION=2682982]noobnl[/MENTION]'s mod has? 0_0

http://d-h.st/ZuI
[Sprint Samsung Galaxy S III] j00manji:
your Odin files didnt work out =/

Neither did your ADB/CWM download combo.

and whats all this about kernels in recovery? the hell happened?

on Liquidsmooth 2.9 (AOSP) with Ktoonz kernel.

I noticed I couldnt mount storage a long time ago. Still cant.
[Sprint Samsung Galaxy S III] nidpancho:
Try using cwm_mod2.img with adb commands on your pc's cmd prompt.