Hi all
I hope that I am posting in the correct place
I need help with my Galaxy S3 SGH-T999
Recently the phone died on me, it was stock rom and with the updates through some of the apps, the phone stopped working correctly. I don't use the phone for making calls, etc, but need it for pictures and a few other apps. The phone is from T-mobile.
I tried to reset the phone and that worked until all the updates were back on and then back to the same problem.
So I decided to put on a custom rom on the phone.
I have tried the following roms:
cm-14.1-20161225-NIGHTLY-d2tmo
I9300XXUGNB6_I9300OJVGNB3_I9300XXUGNA8_HOME
RevolutionaryS5-V3
Slim-d2tmo-6.0.1.alpha.0.1-UNOFFICIAL-20160516-1346
I first installed CWM recovery and then transferred the roms over to the external sd car (also the internal card), went to boot manager (vol up) and installed the files.
It looked like the installation worked but when selecting reboot, the phone would not come back on.
I then loaded up Kies and reset the phone back to factory defaults and only then does the phone load back up after reboot.
Every time I try the custom rom - I run into the same problem
At first I thought the phone was bricked and found info about the jtag and then found something about using an SD card with the following image installed on it - tmobile-T999_4.3_debrick
With the SD card in the phone I can boot to either menus and also able to get the phone to boot to the slim-d2tmo rom. But when I pull the SD card, the phone won't boot. Nothing, no power, nada
I am not sure what I did wrong, followed the direction on the site and thought I did it correctly.
Not sure if I deleted some file, or partition needed or what. I would greatly appreciate some help with this.
Also I would like a custom rom that is stable and fast. I don't need all the bells and whistles but one thing I would like and that is for the camera to be able to take pictures using voice. I know the stock rom allows for this. Not essential but preferred.
Please help with detailed instructions.
Thanks in advance.
After writing this I just loaded up T999UVUEMJC_T999TMBEMJC_T999UVUEMJC_HOME.tar and managed to get the phone back up and running. Then tried the cm-14.1-20161225-NIGHTLY-d2tmo - which I kinda like but it will not boot up without the SD card in. I can manage to get the phone booted with the SD card and get into the new custom rom, but I have to keep pulling the battery, insert the SD card and then try to boot. Don't think it should work like this
Please help.
kouger1 said:
Hi all
I hope that I am posting in the correct place
I need help with my Galaxy S3 SGH-T999
Recently the phone died on me, it was stock rom and with the updates through some of the apps, the phone stopped working correctly. I don't use the phone for making calls, etc, but need it for pictures and a few other apps. The phone is from T-mobile.
I tried to reset the phone and that worked until all the updates were back on and then back to the same problem.
So I decided to put on a custom rom on the phone.
I have tried the following roms:
cm-14.1-20161225-NIGHTLY-d2tmo
I9300XXUGNB6_I9300OJVGNB3_I9300XXUGNA8_HOME
RevolutionaryS5-V3
Slim-d2tmo-6.0.1.alpha.0.1-UNOFFICIAL-20160516-1346
I first installed CWM recovery and then transferred the roms over to the external sd car (also the internal card), went to boot manager (vol up) and installed the files.
It looked like the installation worked but when selecting reboot, the phone would not come back on.
I then loaded up Kies and reset the phone back to factory defaults and only then does the phone load back up after reboot.
Every time I try the custom rom - I run into the same problem
At first I thought the phone was bricked and found info about the jtag and then found something about using an SD card with the following image installed on it - tmobile-T999_4.3_debrick
With the SD card in the phone I can boot to either menus and also able to get the phone to boot to the slim-d2tmo rom. But when I pull the SD card, the phone won't boot. Nothing, no power, nada
I am not sure what I did wrong, followed the direction on the site and thought I did it correctly.
Not sure if I deleted some file, or partition needed or what. I would greatly appreciate some help with this.
Also I would like a custom rom that is stable and fast. I don't need all the bells and whistles but one thing I would like and that is for the camera to be able to take pictures using voice. I know the stock rom allows for this. Not essential but preferred.
Please help with detailed instructions.
Thanks in advance.
After writing this I just loaded up T999UVUEMJC_T999TMBEMJC_T999UVUEMJC_HOME.tar and managed to get the phone back up and running. Then tried the cm-14.1-20161225-NIGHTLY-d2tmo - which I kinda like but it will not boot up without the SD card in. I can manage to get the phone booted with the SD card and get into the new custom rom, but I have to keep pulling the battery, insert the SD card and then try to boot. Don't think it should work like this
Please help.
Click to expand...
Click to collapse
You did the right thing with the SD card, the issue with it not booting with SD card removed is not an issue, that's the way its supposed to work. After restoring boot with the SD card you've got to do a few other steps to correct the device so that it boots without SD card and then you've got to return the SD card to normal function to use it as storage again.
There's a thread in the Verizon Galaxy S3 I535 forum for unbricking with the SD card and the further instructions to restore full functional boot without SD card.
Sent from my SCH-I535 using Tapatalk
I appreciate the help. This should work on my phone even thought it is a T-Mobile and it is a SGH-T999 ?
Any chance you know of the link to fix the booting issue?
I really need to get this sorted out. I am about to trash the phone and get some cheap $80 best buy special just to use the apps I need.
kouger1 said:
I appreciate the help. This should work on my phone even thought it is a T-Mobile and it is a SGH-T999 ?
Any chance you know of the link to fix the booting issue?
I really need to get this sorted out. I am about to trash the phone and get some cheap $80 best buy special just to use the apps I need.
Click to expand...
Click to collapse
The method is the same, you just use your debrick.img for your device instead of the Verizon debrick.img.
https://forum.xda-developers.com/showthread.php?t=2581166
Sent from my SCH-I535 using Tapatalk
So I feel like such a dufus.
I think I know what I did wrong. After going back and forth reading everything, which all looked like what I had originally, I realized that everyone was talking about loading the zip files from the sd card. Thought I did this, but what I was doing was loading them from the external SD card.
So after having put the stock rom back on the phone (and basically gave up) I decided this morning to try one last time.
I downloaded:
OCT-N-WEEKLY-20170127-2232-d2tmo
open_gapps-arm-7.1-micro
Connected the S3 to my PC and copied both files to the phone. Did not have the external SD card plugged in.
Then went to boot menu (vol up) and cleared the cache, davik and data. Installed from zip (local phone this time) and within 10 minutes (or less) the phone was up and running without any issues.
BAM - awesome.
Seemed too good to be true but worked like a charm.
I wonder if that was the problem with any of the other roms I tried?
Anyway, thanks to all for your help.
kouger1 said:
So I feel like such a dufus.
I think I know what I did wrong. After going back and forth reading everything, which all looked like what I had originally, I realized that everyone was talking about loading the zip files from the sd card. Thought I did this, but what I was doing was loading them from the external SD card.
So after having put the stock rom back on the phone (and basically gave up) I decided this morning to try one last time.
I downloaded:
OCT-N-WEEKLY-20170127-2232-d2tmo
open_gapps-arm-7.1-micro
Connected the S3 to my PC and copied both files to the phone. Did not have the external SD card plugged in.
Then went to boot menu (vol up) and cleared the cache, davik and data. Installed from zip (local phone this time) and within 10 minutes (or less) the phone was up and running without any issues.
BAM - awesome.
Seemed too good to be true but worked like a charm.
I wonder if that was the problem with any of the other roms I tried?
Anyway, thanks to all for your help.
Click to expand...
Click to collapse
I don't know what you were having issues with but I've always flashed my ROMs from extsdcard. Unless I'm missing your meaning.
Sent from my SCH-I535 using Tapatalk
Then maybe it were the roms I was using. All the roms I tried would not boot my phone after installation. I had to add the following file to my external SD card -tmobile-t999_debrick
This was the only way I could get the phone to boot back up after I installed the roms.
Or maybe I was using the wrong roms - I have no idea.
I guess my thought process was not correct and that you don't have to put the roms on the internals storage and can use the external sd card to install the roms?
kouger1 said:
Then maybe it were the roms I was using. All the roms I tried would not boot my phone after installation. I had to add the following file to my external SD card -tmobile-t999_debrick
This was the only way I could get the phone to boot back up after I installed the roms.
Or maybe I was using the wrong roms - I have no idea.
I guess my thought process was not correct and that you don't have to put the roms on the internals storage and can use the external sd card to install the roms?
Click to expand...
Click to collapse
Typically, you install custom recovery then root then place new ROM on extsdcard then flash the ROM in recovery from extsdcard. Its actually recommended to keep your ROM zips on external if you have it instead of internal because if internal gets wiped or corrupted then you've lost your ROM zip. It's also recommended to create and store your nandroid backups on extsdcard.
Sent from my SCH-I535 using Tapatalk
Related
I have been reading this site for awhile, even have the paid version on my phone, but have never posted before so I cant post in the dev forum. Anyways heres my issue, I used the NV flash to flash my G2X. Everythings been working great with weapon. Then tonight, I decided to install some fonts and boot animations. After like the third font, I got a low memory error. I took out the sd card and put in a bigger one. I moved my rom manager app from the phone to the larger sd card. Went to restart my phone and now it is stuck in a boot loop. I tried putting in the smaller sd card and the same thing is happening with it. I tried to use the nv flash to flash back to stock and still same results. Any suggestions?
Have you wiped before installing zips?
Sent from my LG-P999 using xda premium
yes
Should I be wiping the dalvik as well?
Im an idiot
I got it, since I had moved clockwork mod and everything to the other sd card, I didnt have a rom on the phone. I just downloaded one to the old sd card and it booted. Cant do nothing with the larger sd card as it is unwritable one that came with samsung epic
Just to let you know posts should like should not be in the dev forum and should not be in this forum either. This type of issue should be posted in the Q&A forum. That is what it is for.
Roms are not run off your sd card. They have to be flashed to the phone's NAND.
Long story about what's going on,
I had to get my first triumph replaced about 2 weeks ago. I had backed it up with a nandroid and titanium backup. I procceded to install the nandroid backup on the new phone. Everything went well for a while untill one day when the phone just shut itself off. When i turned it back on, there was no sd card mounting notification, and it said that there was no sd card in the phone. CWM recovery also wouldn't read it. After having done random combinations of repartioning the sd card, formating the sd card, using a different sd card, unrooting, factory restoring, i seem to be able to get it to work for a little. What happens, however, is that after i restore from nanadroid or titanium backup it works for a little, then turns itself off again and the card wont mount! This is really starting to suck any help is apperciated
Thanks,
A guy pulling his hair out. ._.
Extra info: Rooted with gingerbreak 1.20, not sure what cwm version but it is from the all things about root guide. Just factory restored again and it showed up for a little then i restarted and it was gone again. It seems to have fits on whether or not to recognize the sd card.
seeing as no one seems to have any help to give, I guess i will cave in and go through virgin mobiles support to give a repalcement =.= If i do ever find a fix myself, i'll go ahead and post it for anyone else who might have it as well.
dont know how to delete posts >.<
try to ask here http://androidforums.com/triumph-all-things-root/
Sent from my FIH-FB0 using xda app
Long time lurker first time rooter.
I finally got around to rooting my VZ GS3 this week, and all went well. However, moment I boot into CWR, my external sd card (micro 64g) dies horribly, and won't mount. I can pull it, and read it fine on my laptop. If I Odin back to stock, and re-format the external via the stock software, it works no problem. Once I try to flash into a new ROM, it dies. It does this on TWRP as well.
Are these the only two tools to flash ROM's?
Edit: The external card is formatted correctly. Even more, when I reboot into the stock rooted rom, I can access and use the external card, it is only during, flashing of a rom and afterwards that I cannot mount it.
Is it formatted to "Fat32"? Otherwise it will not work in recovery.
Sent from my SCH-I535 using xda app-developers app
Stormchylde said:
Long time lurker first time rooter.
I finally got around to rooting my VZ GS3 this week, and all went well. However, moment I boot into CWR, my external sd card (micro 64g) dies horribly, and won't mount. I can pull it, and read it fine on my laptop. If I Odin back to stock, and re-format the external via the stock software, it works no problem. Once I try to flash into a new ROM, it dies. It does this on TWRP as well.
Are these the only two tools to flash ROM's?
Edit: The external card is formatted correctly. Even more, when I reboot into the stock rooted rom, I can access and use the external card, it is only during, flashing of a rom and afterwards that I cannot mount it.
Click to expand...
Click to collapse
After much experimentation and loads of flashing and re-flashing, changing roms, changing recoveries, etc...I came up with the problem.
During the recovery/flash process, the external SD reader would not work at all, and any card in the reader would become corrupt. Rooted, flashed the new rom (LiquidSmoothJB) and then inserted the card afterwards, and formatted in phone, and voila, it works. Hopefully this helps someone else who comes across the same problem.
Ok so here's what's going on. I've been running an old ParanoidAndroid for a while and wanted to upgrade to a new version. I've been using TWRP as my recovery for a long time, and although I hadn't checked recently, I remember not being able to access my internal storage in recovery. So I downloaded the EZ Recovery app, flashed the TWRP from that, and went out to upgrade to the new PA.
In recovery, I was able to make a backup, factory reset, wipe system, and wipe dalvik. Then I went into the install menu, and I couldn't access anything on my external SD. Since I previously could ONLY use my external in recovery, all my ROMs and such were on that. SO I was stuck without a ROM, and without access to one to install. It was a *****, and took a lot of tries, but I was able to get my SD mounted enough to half-way restore the backup I made (as in, it restored the system and very little data, but was able to boot). So I figured it was some issue caused by the new TWRP, so I have un-rooted, and gone completely back to stock. Unfortunately, the problem still exists.
What could the issue be? Could it be something caused by flashing the new TWRP? If so, what could fix that? Or is it probably just a hardware issue that can't be fixed? I'm leaning towards that, and since I'm back to stock, I can just get a replacement from Verizon.
Thanks for any help!
It's likely not an issue with TWRP at all, but just an issue with external SD cards inherent to the S3 and some other Samsung devices. I had a similar problem, and within minutes of my micro SD card constantly unmounting itself, the card is now simply unusable. I haven't managed to find a solution, so yes, it's likely just a hardware issue that can't be fixed.
I've went through two sd cars with this phone. Most quality sd cards have a warranty, call and get that started. I called SanDisk last Monday and my replacement just came today. It sucks but they are fast. Good luck, losing an sd cars sucks.
This time around, my sd will only be for music and pics. I'll be taking it out whenever I flash something.
Sent from my SCH-I535 using xda app-developers app
Hey guys. Forgive my noobity but I could do with some help and might have a unique problem although I dare say someone has had this or similar.
Firstly, after putting a 64GB stick in my tablet the other day, it all went badly wrong. I had done it before with my previous 64GB that had been playing up so I sent it back and got a new one. The new one seems to be where it all went pear shaped. I might add, the 64GB is for my phone really but my phone cam was playing up so I was swapping it over and stuff... anyway the card itself seems fine in my phone.
Anyways... now my ampe tablet is suffering some strange effects that have changed. initially it would not boot up unless I redone it with the official firmware.. but then wouldn't boot up again, unless I did the same thing over and over. then one time it just refused to boot up past the initial boot screen. I gave up for weeks then picked it up again two days ago.
Now I give it the firmware installed using pheonix again and it booted up. Ahh I thought... lets play. Now I plug it into the pc but the pc says I need to format the 5GB internal partition. So I did. I then looked how to fix the fact that the tab still says it has 0.00kbs internal storage in settings. Then after a while it came up saying 5GB so i copied some files onto it.. great. But I still can't install apps as I found when trying to do this tested working fix http://www.youtube.com/watch?v=sJlpek6w624
I then read about using android commander to move busybox from xbin to bin in the system folder but mine is already there.
So now I am stuck. I can't test if my tab is rooted for the youtube link fix above although this is what I said to Nayeem on youtube:
================
Hi Nayeem. I'm really struggling with this. At first my tab was staying at the 2nd initial boot up screen after I put in a 64GB SD card. Using pheonix I managed to get it to boot by reinstalling the updated official rom from szampe but every reboot back to square one. I left it alone for weeks and came back to it, reinstalled the factory rom again and now it will boot up everytime but it has factory reset every time. I cant run the apps you supply for some reason. Everytime I have rebooted the tab, and connected back to pc it says I need to format the internal 5GB partition. I don't know if I have rooted it properly as I can't check. The commands you give above, work as it changes the location proven when I 'get' it. I'm really stumped. I'm trying out a method someone said about moving busybox from sys/xbin to sys/bin but it's already there (using android commander) so I am really stumped now. When I format the partition, it allows me to copy files to it.
================
So far I am stuck with boot up being a factory reset and the partition needs formatting and although the tablet seems a little laggy, everything I have tried works including wifi and incoming email alerts after logging into google account for playstore but no apps will install or update. the best warning I get is there is no memory to install anything and Nayeems method of moving the install location to the sd card seems to work but nothing will install still saying NOT INSTALLED when I try.
Sorry for the long winded thing but I am really new to all of this.
My hat is off to you if you read all of this and can offer a solution so i can give this tablet back to the kids.
Do you have an installed recovery
Try installing a recovery and wipe data and cache. If it does not work u have to repartition ur tablet
nelsontky said:
Try installing a recovery and wipe data and cache. If it does not work u have to repartition ur tablet
Click to expand...
Click to collapse
I am gonna look into this tonight and see what I can find out. I really don't know exactly what I am doing outside of getting pheonix up and sending a standard rom back to it as previously mentioned.
How would I repartition it ? Sounds stupid asking as i can build pcs... just want to make sure I am doing the correct method.