yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] Jmick363:
tl;dr rooted S4 not detecting SD card after trying different cards, formatting them all differently, restarting, and cards work in another phone.

I just got this Verizon S4 (SCH-1545), current build MK2 Android 4.3, less than a week ago, and I came from an HTC sensation. Firs tthing I did was put my sd card from the sensation into the S4 just so my photos and music and everything else would be right there. If I remember correctly, Play Music might have saw a few songs at first, but I didn't pay much attention to it. The SD card is an Adata 32 GB class 10. The S4 is now not detecting the Sd card at all. My HTC sensation is detecting it just fine, and my computer is also detecting it just fine via usb to sd card reader. Another strange thing is that using a usb OTG adapter, the SD card is still detected. Meaning I plug in a cable to the micro usb port on my phone which has a female usb 2.0 port, which I then plug the sd card reader into. The S4 detected the sd card then, but not when it is plugged directly into the SD card slot. Other people have suggested other SD cards, I used a SAMSUNG 16GB SD card that came with a Samsung Epic 4G I had from a while ago. This SD card was detected by my HTC Sensation, and my computer, and neither have been detected by my S4. To format both of these SD cards, I have been right clicking them in windows explorer and clicking format. I have tried formatting both SD cards in format exFat, FAT32, and NTFS, and nothing has worked. I have the phone rooted and SafeStrap is installed, booting to Safestrap recovery also doesn't detect either SD card. There are other things that I have tried that I probably forgot to mention, but those were the primary fixes that I found and nothing has worked so far. If anyone can give any suggestions or link me somewhere where my exact problem has been resolved, I would very much appreciate it.
[Verizon Samsung Galaxy S 4] Jmick363:
Bump... Update, the other day the phone randomly detected my SD card, soon later it simply stopped. Not sure what it was that made it work though...
[Verizon Samsung Galaxy S 4] k1mu:
The SDcard slot on your phone is broken. What I'd do is to open it up, remove the SDcard, and try compressed air into the slot to see if something got stuck in there (like lint, etc) that's keeping the card from making contact. Other than that, it's warranty time.
[Verizon Samsung Galaxy S 4] Jmick363:
Okay and obviously rooting it would void the warranty, I have safestrap installed. Is there a way to return to stock? I actually bought the phone less than 2 weeks ago, and the verizon store is right down the street. If you bring it back within 14 days you can get a refund/swap it for something else, maybe I'll just see if they can throw me another one for a restocking fee or whatever, I don't know... Suggestions?
[Verizon Samsung Galaxy S 4] k1mu:
You can uninstall Safestrap pretty easily. I recommend uninstalling the recovery, rebooting, then uninstalling Safestrap, which will delete your ROM slots. Then, use the Terminal Emulator app to unroot using the info in the Saferoot thread. That should get you back to stock.
[Galaxy Note 3 Q&A, Help & Troubleshooting] csccsc:
Hi all,

I saw too many users are complaining about no imei unknown modem issues on note 3..I have to request you, can you please make a official thread in troubleshooting then users can easily seen how to fix their device and they will get more help..this is very common issue in note 3 . Write a solution in troubleshooting forum as well newbie will get help thanks in advanced..
[Galaxy Note 3 Q&A, Help & Troubleshooting] ZION959:
There is one in this forum, and many more if you used the search . Here is the link for the fixed my friend :

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

And I believe you post in the wrong forum. This is for Development.
[Galaxy Note 3 Q&A, Help & Troubleshooting] Clark Joseph Kent:
OP, first please read the Forum Rules on posting....thread moved here, as it does not belong in the Development Sections.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] boone8576:
Hi,

I am currently running stock rooted MDL with TWRP on my AT&T SGH-I337. I used Motochopper to obtain root. I'd like to get to the latest update released by AT&T and still have root. I will not be running custom ROMs in the future. Can someone point me to the process I should use? I've done a fair amount of reading but I am suffering from a bit of information overload. Thanks in advance.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] scott14719:
I'm saying this for your own good. If you don't understand what it is you are reading, don't do anything. Are you sure you want to do something that will brick your phone if you don't understand 100% of what it is you are doing to it? You said you have done some reading so you obviously know where to look for information. I suggest you take as much time as you need to re-read the information, research the parts you don't understand, and then when you know what is being discussed and what the possible complications are proceed. Taking shortcuts when you don't understand things will only mess your phone up.

If you decide to not take this advice, that's fine, just ignore it (no need to reply), but I highly recommend you take the suggestion. Good luck.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] DeadlySin9:
Definitely make sure you understand what you're reading. If you want a stick update without losing root, use the StockUp ROM. Read before flashing. You'll need a 4.3 kernel and loki. Make sure you know exactly what you're doing before you start to avoid bricks.

Sent from Black<3's I337 running Foxhound ROM
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] boone8576:
Thanks for the word of caution. I know you don't know me from Adam but if you did you'd know that I wouldn't attempt anything until I was completely comfortable with the process.

This gives me the direction I was looking for. I'll do the research on the items you mentioned and go from there. Thanks a million.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] popoinzaghi:
I have an issue with my i9305 as I can't flash Google toolchain-compiled kernel. But it works for me when i flash the same kernel compiled with linaro toolchain. I used Boeffla Kernel 5.1 stable compiled by P$T here http://xdaforums.com/showthread.php?t=2322893&page=54

but failed to flash latest boeffla kernel compiled by lord boeffla (starting 5.1-beta14 reverted back to Google 4.7 toolchain). Does anyone experience the same problem?any ideas?

The Galaxy Project rom v14.03 GT-I9305
[Nexus 5 Q&A, Help & Troubleshooting] jblazea50:
I just got the N5 for T-Mobile. I am having issues trying to send MMS (pictures or group texts). Data is enabled as well as Wifi. This setting the mms just hangs and never goes through. I have to turn wifi off in order for it to go through. This doesn't seem ideal as it should be able to switch automatically.

Is there a solution?
[Nexus 5 Q&A, Help & Troubleshooting] Z1cK:
You can try 8sms. It worked for me
[Nexus 5 Q&A, Help & Troubleshooting] havy15:
You try fixing your APN settings?
[T-Mobile, Samsung Galaxy SIII] Phil_Suz:
[updated 20150104]

version v2.2

migration to twrp2.8.3.0

quickfix for lzma initrd roms

fix baseband not recognized on some tw roms

added f2fs feature to multiboot kernel for future versions..

moved qemu tools to sdcard to free space

[updated 20150101]

version v2.13

lollipop support

[updated 20140401]

version v2.11

ubuntu touch support ( http://www.androidfilehost.com/?w=files&flid=13392 )

Important recommandations and details of working features can be found in this thread : http://xdaforums.com/showthread.php?t=2702692

[updated 20140316]

version v2.0

qcow2 support ( https://www.youtube.com/watch?v=LGoTb0u5oX0 )

[updated 20140311]

version v1.2

migration to twrp2.7.0.0

sizing of system/data/cache now possible

real internal/external sd mounted ( respectively in /storage/intsdcard and /storage/extsdcard )

new way to boot roms

new link to download : http://www.androidfilehost.com/?w=files&flid=12801

Hi,

This recovery image is based on twrp with multiboot feature on Galaxy S3.

I did this on Galaxy S3 Bell model but it as been reported to work on Tmobile Model ( by saranhai, thank's to him )

( original thread : http://xdaforums.com/showthread.php?t=2577211 )

Please

follow exactly the operations in videos examples

to avoid any risk.

Very important recommendations :

- BACKUP all your data first !

- Use only your internal if you have at least 4G available ( 7GB recommended because img files are sparsed but if you fill all the rom, it will take 7GB )

- Use your external sd card only if :

- you have at least 7 GB free

- your filesystem is vfat ( exfat,ntfs not supported for the moment )
​

-

Very very important

: when you use "set rom" option, you have to see "command succeded" at the end of the output.

If not, don't go further and reboot.

- start by playing with recovery roms ( check video ) before testing full rom

- creating rom on external vfat can take about 15 minutes (to create img files). Be patient...
​

The method used is an adapted kexec-hardboot method created by mkasic (http://xdaforums.com/showthread.php?t=1266827), but with a complete replacement of kexec by a new userspace program I did ( kload-hardboot ) and a very small kernel patch ( hardboot-reserve ). Note also that this adapted method is easily portable to any android devices.

I will publish sources when cleaned.

Booting multiples ROMs demo:

[YOUTUBE]_T_r4lsudH8[/YOUTUBE]

Playing with recovery roms:

[YOUTUBE]xeN7EIrZDy8[/YOUTUBE]

Creating a new rom, installing gapps ( if not done at first stage ) :

[YOUTUBE]j6GdvUfNppE[/YOUTUBE]

Multiboot android app ( early dev stage )

Download link : http://www.androidfilehost.com/?w=files&flid=12801

References / Credits :

mkasic

: kexec-hardboot creator - http://xdaforums.com/showthread.php?t=1266827

Tassadar

: MultiROM creator - best project - http://xdaforums.com/showthread.php?t=2011403 - bbootimg used

TWRP Team

: http://www.teamw.in/project/twrp2

saranhai

Philippe,
[T-Mobile, Samsung Galaxy SIII] saranhai:
I can personally confirm that this DOES indeed work! I currently have loaded up 3 different ROMs, and they eaach boot no problem, loving it! Great job and hats off to the developer! :good:

-Saranhai
[T-Mobile, Samsung Galaxy SIII] G1-evolve:
I assume this takes up a lot of space though?
[T-Mobile, Samsung Galaxy SIII] :
I was able to flash the recovery via Odin. Now what? Do I need to reinstall my ROM to have it work for multi-boot? Or can I have it recognize my existing ROM?

Also, if I make changes to the ROM, will the multi-boot functionality know that I've made changes or do I need to backup?

Thanks.
[T-Mobile, Samsung Galaxy SIII] armkreuz:
OMG ! Now mobile device becoming very interesting !!!
[T-Mobile, Samsung Galaxy SIII] Tomb77:
Amazing how booting back and forth is just like rebooting your phone, in terms of their responsiveness. I thought there would be some sort of noticeable lag on each boot. It does use about 7GB like OP says. Pretty cool though, to be able to go back and forth between stock tw to ASOB in so little time. App works like a charm too. This is great, thanks for creating and sharing.

---------- Post added at 01:55 PM ---------- Previous post was at 01:52 PM ----------

Multiboot rom keeps changes. The last rom you were running is your internal (it will boot on every reboot). Follow the third video exactly and you will see, and make sure to read the OP again.
[T-Mobile, Samsung Galaxy SIII] :
[/COLOR]

Multiboot rom keeps changes. The last rom you were running is your internal (it will boot on every reboot). Follow the third video exactly and you will see, and make sure to read the OP again.[/QUOTE]

Oh, I think I get it now. So, my current ROM (CM11) is still stored in the original ROM partitions, but selecting a different ROM to boot is pulling it from the internal SD card. So, I could boot a secondary ROM (say TW) or a third ROM (like SlimKAT) but then choose Reboot to get back into CM11. Am I correct?
[T-Mobile, Samsung Galaxy SIII] Tomb77:
Yes
[T-Mobile, Samsung Galaxy SIII] :
Tomb77: Thanks for the clarification.

This recovery ROCKS! Not only can I use a TW ROM for WIFI calling when needed, I can also test other ROMs without having to wipe/format/etc. Awesome work!!:good:
[T-Mobile, Samsung Galaxy SIII] Tomb77:
Will we have to create the multiroms again after updates for mulitirom twrp? And, can we flash over an already created multirom for an update on the rom?

Edit: So I was able to update my multirom rom. I got hung up on symlink... I did a battery pull, eventually booted the multirom rom and it was updated. been playing with it for a couple hours and there doesn't seem to be any instability issues. Thought I would through that out there.
[T-Mobile, Samsung Galaxy SIII] ivoe:
My try this tomorrow just to check out other roms an stuff so i know what is good with out wiping all my data c:

Seems to be getting great reviews from everyone
[T-Mobile, Samsung Galaxy SIII] Slypnslyde:
If you're a flash junkie, this is for you. I'm so excited
[T-Mobile, Samsung Galaxy SIII] zul8er:
VFAT, Same as FAT32? If not, how do I get the external sd in VFAT?
[T-Mobile, Samsung Galaxy SIII] zul8er:
Well I bought a 16gig sd and it appears to be corrupt of something. I can format it and then put it in my phone and it just freaks out. Put my original 2 gig card in and everything is fine again.

---------- Post added at 05:57 PM ---------- Previous post was at 05:55 PM ----------

Also another question. Each ROM will take 7 gigs, or is that just the image file that all the ROM's run on?
[T-Mobile, Samsung Galaxy SIII] Tomb77:
I am using FAT32. I think FAT32 is an extension of VFAT so it shouldn't matter. Could someone verify? It's working for me and I didn't change the format.
[T-Mobile, Samsung Galaxy SIII] zul8er:
I read it was the same... Just wanted to make sure.

I did buy a faulty SD card. Constantly disconnects corrupting files.

---------- Post added at 07:26 PM ---------- Previous post was at 07:24 PM ----------

But I did get Philz recovery, Slimbean, and Dandroid running.
[T-Mobile, Samsung Galaxy SIII] Tomb77:
I wiped everything and started over. Had some issues afterwards and eventually had to Odin stock. After setting everything up again, I am unable to flash a rom onto the multirom. It looks like the error starts where it is unable to connect to data. Any suggestion would be great, thank you.

Edit: Not until I full wiped with the phones original recovery have I been able to play again.
[T-Mobile, Samsung Galaxy SIII] tnt8902:
Working nicely, but your videos were kinda confusing and figured it out on first try. Nice work

Sent from a potato from the future.
[T-Mobile, Samsung Galaxy SIII] Phil_Suz:
Yes, ~7GB if installed on external vfat, a lot less if installed internally as img files holding filesystems are sparsed. Say ~2G max after installation

But I admit that 7GB hardcoded is too much.

Next version will add possibility to custom sizes of /system, /data and /cache. For example, a light rom like Dandroid4.7 can be installed on ~1.8G ( 1G system, 500M data, 200M cache).

PS : for people who want do do it now manually, it is easy : just connect shell with adb when in recovery and edit values (in hexa) /sbin/create_rom.sh of SIZECACHE,SIZESYS and SIZEDATA. Without rebooting, you will be able to create new roms with new size under twrp menus.

Philippe,
[T-Mobile, Samsung Galaxy SIII] Tomb77:
Been running this recovery for over ten days now. I have to say that this is very awesome, it works great. About the only issue I had once is a multiboot rom not deleting for a couple of tries. I am surprised that it seems like very few people are trying this out here.
[T-Mobile, Samsung Galaxy SIII] tnt8902:
I'm on aosp as primary also. Tried to put tw on secondary to no luck.
[T-Mobile, Samsung Galaxy SIII] :
It must be something with the later ROMs as I have a 4.1.2 TW ROM as my secondary.
[T-Mobile, Samsung Galaxy SIII] mcgrabowski:
The 4.3 Dandroid works.
[T-Mobile, Samsung Galaxy SIII] tnt8902:
Unfortunately I need a tw ROM to use WiFi calling, as dandroid states that its not implemented in his ROM.
[T-Mobile, Samsung Galaxy SIII] :
That's why I use z999 - it's an odexed TW ROM. It's only 4.1.2 but I use it when I travel for WI-Fi calling. Here's the link to the thread: http://xdaforums.com/showthread.php?t=2332365
[T-Mobile, Samsung Galaxy SIII] hasansabuz:
I dnt understand what to do..which steps I should follow..if any detailed instruction I get..it could be more helpful
[T-Mobile, Samsung Galaxy SIII] :
Take a look at this thread: http://xdaforums.com/galaxy-s3-t-mobile/help/how-multiboot-multirom-t2829406 There's a lot of discussion and a link to a "how to" video in the thread.
[T-Mobile, Samsung Galaxy SIII] hasansabuz:
At last i did it..i can boot my favourite roms without flashing again and again...|

thanks BASS man AND twrp
[T-Mobile, Samsung Galaxy SIII] hasansabuz:
one probs..i use tw as my primary and aosp rom is secondary..bt every time i turn on screen its brightness became maximum..i tried manual or auto bt cant find solution..i changed 2/3 roms bt every rom has same prob.. can anyone help??plzzzzzz
[T-Mobile, Samsung Galaxy SIII] :
I've had that happen with a number of KK AOSP ROMS, even as my primary ROM. You'll have to write in the ROM thread to see if anybody has a solution for it.
[T-Mobile, Samsung Galaxy SIII] ShernDog:
Try moving the slider to a little past the 0 mark so it's not exactly on 0, that seemed to work for me for a while but I ODIN'ed back to stock rooted 4.3 and it seemed to go away.

---------- Post added at 03:31 PM ---------- Previous post was at 03:30 PM ----------

My TW roms I use with Multiboot aren't saving the pictures I take to the gallery >.< anyone have a fix??

Regular Touchwiz ROM works fine.

---------- Post added at 03:36 PM ---------- Previous post was at 03:31 PM ----------

I've already ODIN'd to stock, and tried different ROMs. I'm using Dandroid 4.3 right now
[T-Mobile, Samsung Galaxy SIII] ktetreault14:
Can someone link me to the latest recovery. Link in op not Working. Thank you ahead of time

Found it!! :D
[T-Mobile, Samsung Galaxy SIII] cLogic:
I have been switching between latest CM 11 nightlies and Omni rom for a while

usually this involves:

titanium backup

reboot recovery (twrp 2.8)

nandroid backup current rom

wipe system, dalvik, cache, data (without wiping /data/media)

restore nandroid of other rom

reboot

titanium update/restore missing/updated apps

obviously this multi-boot would cut the backup+restore process (20-25mins) to simply reboot (30secs-1.5mins)

how does this affect (if at all) the CMupdater and Omni OpenDelta rom updater ability?

the updaters run addon.d scripts (backup mode), then auto-reboot recovery to install updated rom zip and whatever is in FlashAfterUpdate folder (Omni), then reboot system and run addon.d scripts (restore mode)

will it flash to current rom's area or does a reboot without app/manual selections fallback to default internal rom (thats bad if the update is for the secondary rom) ?

thanks in advance
[T-Mobile, Samsung Galaxy SIII] ShernDog:
Anyone know if this will work on 5.0 Lollipop runtimes since it is ART?

I love this for the Galaxy s3 it is why I'm okay with keeping this phone it is amazing.

Edit: Works for ART runtime but lollipop ROMs will not boot at all.

Maybe workaround would be flash a new recovery to flash the main ROM, and then flash multiboot for additional ROMs?

Not very friendly solution but might work.
[T-Mobile, Samsung Galaxy SIII] chalky7880:
[MENTION=5593099]Phil_Suz[/MENTION] is there any chance of an updated version that would allow lp roms to boot?
[T-Mobile, Samsung Galaxy SIII] Anthonol:
Great question...... Been thinking the same too
[T-Mobile, Samsung Galaxy SIII] Phil_Suz:
Hi All,

Sorry for long pause. Yes, I just updated multiboot to v2.13 to support lollipop ( img roms )

Philippe,
[T-Mobile, Samsung Galaxy SIII] Anthonol:
Thanks man and do have a very productive and blessed new year!
[T-Mobile, Samsung Galaxy SIII] ShernDog:
Thank you soooo much!!!!! Multiboot is amazing and keeps this phone alive for me. It is amazing.
[T-Mobile, Samsung Galaxy SIII] chalky7880:
Thanks [MENTION=5593099]Phil_Suz[/MENTION]! Really appreciate your work.
[T-Mobile, Samsung Galaxy SIII] phillipmckinnish:
It works great thank you
[T-Mobile, Samsung Galaxy SIII] ShernDog:
[MENTION=5593099]Phil_Suz[/MENTION] I can't get the most recent (January ROMs) to boot using MultiBoot. It just gets stuck in a boot loop.

Can someone else on the latest mutliboot try to flash the latest cm12 or cyanideL to see if its working or just my phone..? The one dated 01/02.
[T-Mobile, Samsung Galaxy SIII] Phil_Suz:
Hi ShernDog,

For cyanideL, I confirm that it is not working ( in fact, it is the first rom I see that uses lzma compression for initrd ) but the new version fix it.

I can not confirm for latest cm12 but I tested some of them on my d2att and It is working well.

The new version is ready and include following changes :

migration to twrp2.8.3.0

quickfix for lzma initrd roms

fix baseband not recognized on some tw roms

added f2fs feature to multiboot kernel for future versions..

moved qemu tools to sdcard to free space

Philippe,
[T-Mobile, Samsung Galaxy SIII] ShernDog:
Thank you so much. I was hoping this would happen! I'm going to test it out right now.

Edit: working perfectly now :) very nice and the command prompt entries are very nice simplified. Lollipop is the only img rom correct?
[T-Mobile, Samsung Galaxy SIII] $avage$3:
been forward to speaking to you mr phil_suz.... philippe....

absolutely love the multiboot and tried reaching out to you in the other thread

First of all, is this suitable for galaxy s3 d2ATT or D2LTE?

is this is the same version as the other multiboot thread with TWRP 2.8.3.0?

http://xdaforums.com/showthread.php?t=2684052
[T-Mobile, Samsung Galaxy SIII] ShernDog:
I'd say they are both fairly interchangeable, and the same thing except specific to the different models. Just get the correct one for your device.
[T-Mobile, Samsung Galaxy SIII] Gibson99:
Remembered seeing that some folks had issues and deleted the multiboot dir. so in twrp, i renamed it to multiboot.old, rebooted back into recovery and tried again. no difference.
[T-Mobile, Samsung Galaxy SIII] Gibson99:
may have found the problem... i tried writing a backup of the stock rom to the sd card and it failed. after that i couldn't read from the sd card in twrp. so maybe the sd card slot is bad on this phone. i know the card is good as i've been using it in my dashcam for a while, and it passed with flying colors in h2testw. gonna try copying the zips to internal (or just downloading them directly to the phone while running stock rom) and flashing again. will update this post if that works.

update: this did not work. in twrp when "internal" is the current ROM (at top of screen) and i go to file manager, the internal storage is at /sdcard. when i SET whatever rom i create so that it's listed in red at the top left, the internal storage changes to be /sdcard2. i can browse there just fine, but when i try to flash a rom from it, i get a MOUNT error - unable to find partition for path /sdcard2.

deleted all the roms i made, then re-flashed multiboot 2.2 from external sd and rebooted back into recovery. made a new rom for cm12, still having the same problem. guess i'll flash standard twrp, make a backup, and see if i can even flash a rom over stock from external sd. this is probably the most screwed up problem i've ever had trying to flash something.
[T-Mobile, Samsung Galaxy SIII] ShernDog:
[MENTION=2287913]Gibson99[/MENTION]

Never had this happen to me, it may be the 4.3 you have on there. Did you get knox? Also I don't know the way you put on a custom recovery. I used towelroot I believe and then used ROM manager to flash CWM, then used that to flash MultiBoot. It may be the way you installed the first recovery. Maybe try ODINing back to 4.3 and trying it again fresh? Also you can't flash an internal ROM with the ROM on that ROM partition, it'll have to be on your sdcard, and if that's bad then...