Develop Bugs

Help Needed for Roms on Wind Mobile S3 (SGH-T999v)

I recently purchased and rooted my galaxy S3 on Wind mobile (SGH-T999v) running on 4.1.1 and i have encountered issues installing roms onto the device let alone finding roms that are compatible with the phone. I am completely honest in saying that I have no experience in using android (I had an iphone before but it sucked ) but I am eager to learn the many additional features that are available by rooting. I have looked through threads on this site but I have had trouble finding roms to use. I tried installing cyanogenmod 10 by following the instructions for wind S3's on this thread: http://forum.xda-developers.com/showthread.php?t=1775616 but to no avail. I booted my device in recovery then cleared user data and cache before booting the zip file for cyanogenmod. After a few seconds it would say installation aborted. Since I am new to the rooting scene it might be a simple mistake that I am making. If anyone knows some way to fix this or anything that could help that would be great.
Besides that, if anyone wants to share any good roms/themes that I could use and that would work on Wind mobile it would be much appreciated. Like I said earlier I am brand new to rooting so please pardon my inexperience. Thanks

You're probably using an outdated version of CWM Recovery. If you are rooted, go into the Play Store, install GooManager, and install TWRP, boot into recovery, and try to install Cyanogen Mod 10 using that

adslee said:
You're probably using an outdated version of CWM Recovery. If you are rooted, go into the Play Store, install GooManager, and install TWRP, boot into recovery, and try to install Cyanogen Mod 10 using that
Click to expand...
Click to collapse
How do you preform an update for CWM, i used TWRP to boot in recovery mode but i dont think it did anything, then tried installing by running the Cyanogenmod zip file in recovery mode but it failed again

Cannot Install ANY cm/aosp/aokp Rom

hello all,
I'm having trouble understanding something with my SIII. I have a Canadian Rogers SIII currently running DJJOHNNYBLAZE's rom.
great rom, no problems at all!
But when I try to, I haven't been able to install any CM, AOKP or AOSP rom on my phone through TWRP or CWM recovery... only the stock based roms work when I install them..
is there something I'm missing? or doing rom? I'm quite familiar with the flashing process, I've done it a million times on my SIII and my previous Sony Xperia..
Any help, tips or direction to an answer is much appreciated

RoshanDoon said:
But when I try to, I haven't been able to install any CM, AOKP or AOSP rom on my phone through TWRP or CWM recovery... only the stock based roms work when I install them..
Click to expand...
Click to collapse
First question: what fails about the install process?
Second question: how did you install the recovery images?
Most of the time when I hear something like this on a Canadian S3, it's because of the different device code (d2can vs. d2att) of the Canadian model; the images you get through goomanager or ROM Manager or similar will see that you're trying to install a d2att ROM on a device it sees as a d2can, fails to get that the two are software-compatible, and aborts with a "status 7" error.
If that's the case, you can manually flash, say, the d2att TWRP image (look here for the image and instructions), which will happily flash d2att ROMs onto your device.

smelenchuk said:
First question: what fails about the install process?
Second question: how did you install the recovery images?
Most of the time when I hear something like this on a Canadian S3, it's because of the different device code (d2can vs. d2att) of the Canadian model; the images you get through goomanager or ROM Manager or similar will see that you're trying to install a d2att ROM on a device it sees as a d2can, fails to get that the two are software-compatible, and aborts with a "status 7" error.
If that's the case, you can manually flash, say, the d2att TWRP image (look here for the image and instructions), which will happily flash d2att ROMs onto your device.
Click to expand...
Click to collapse
thanks for the quick reply
to answer your first question: when i flash any of them, in recovery it just says "Failed" in red letters.. the funny part is I've installed a couple open source roms before and they worked (ie Liquid, Ktoonez AOKP rom), now i can't :S the ones i flashed were d2att, possibly my problem now, however, why did they work before?
to answer the second: i do a factory reset, wipe cache, flash rom, install gapps, wipe dalvik (as stated in most forums)
also, i've installed TWRP by installing GooManager on my phone and installing it from there, is that wrong? is it different than manually doing it with the command?
thanks again

RoshanDoon said:
i've installed TWRP by installing GooManager on my phone and installing it from there, is that wrong? is it different than manually doing it with the command?
Click to expand...
Click to collapse
Yes - that means you have the d2can TWRP image and not the d2att recovery image, which causes the problem I described. You will probably want to manually install the d2att image in its place.

smelenchuk said:
Yes - that means you have the d2can TWRP image and not the d2att recovery image, which causes the problem I described. You will probably want to manually install the d2att image in its place.
Click to expand...
Click to collapse
ahhhh... gracias!
will do that now then, thanks

I'm having a similar problem.
I've rooted my s3 i747m (virgin), and I have backed up using TWRP.
Attempting to install Cyanogen mod from a .zip on internal sdcard. In recovery mode I've gone in and tried to install from the zip, but I'm getting status 7. Any ideas?

ultrashaun said:
I've rooted my s3 i747m (virgin), and I have backed up using TWRP.
Attempting to install Cyanogen mod from a .zip on internal sdcard. In recovery mode I've gone in and tried to install from the zip, but I'm getting status 7. Any ideas?
Click to expand...
Click to collapse
Exactly the same problem, exactly the same cause; read the earlier posts in this thread for an idea of what to do.

smelenchuk said:
Exactly the same problem, exactly the same cause; read the earlier posts in this thread for an idea of what to do.
Click to expand...
Click to collapse
Again! You've done it sir. This worked exactly right. Thank you so much.

[Q] I747 Galaxy S3 Clockworkmod Recovery Problem

Ok guys I am a noob (also new to these forums) and I'm having a lot of trouble with my phone. The other day, I rooted my phone using towelroot and confirmed it using root checker. then, I downloaded ROM manager as advised by a friend. i followed the instructions and installed Clockworkmod Recovery onto my AT&T Galaxy S3. Feeling I was finally ready to install a ROM, i tried to download Cyanogenmod 10.3.1 only to have it be "downloading" for over 14 hours without it completing. From there, i did some research and decided to utilize the Cyanogenmod Installer. it seemed to work perfectly, even showing the cyanogenmod logo under when my devicec turned on, until it told me to reboot my device. i entered clockworkmod recovery mode to officially reboot it. when i selected "reboot system now" it said "Root access possibly lost. Fix?". i was given the options to say "No" and "Yes - Fix root (/system/xbin/su). no matter which one i try, my phone boots to the stock touchwiz OS. I have installed and reinstalled both superuser, superSU, and ROM manager to no success. What am i doing wrong?

Try flashing Philz Touch via Odin and use that to flash a custom ROM.
From what I recall, CM ROMs are already rooted.

audit13 said:
Try flashing Philz Touch via Odin and use that to flash a custom ROM.
From what I recall, CM ROMs are already rooted.
Click to expand...
Click to collapse
CM is already rooted? What does that mean? I have a feeling that I will be unable to flash any ROMs due to my "possible loss of root access." Thank you for your patience as I am a noob and am very stressed out as this is my only phone.

I see two areas that are potential problems for flashing that rom. If it took 14 hours to download, its highly likely a corrupted download. But also, you may be on too new firmware. Cm uses asserts in the updater-script to check that you have the right base firmware/bootloader build. They dont update this so when newer firmware is released it will no longer flash because the script doesn't see it as allowed.
Anytime you have issues flashing something in recovery, you should copy the recovery log to sd. This will tell you what happened. I suspect it simply didn't flash, but without the log, theres no way we can tell what happened.
Also, you do not need to be rooted to flash anything from recovery. Just flash the recovery, then flash a rom from there. Nearly all roms you will ever see are already rooted. Non rooted roms are very rare and are generally only used as an alternate way to revert to stock.
I dont use cwm, but if im not mistaken, it seems to always ask to fix root. I dont know why, but I see people ask about it frequently.
I use TWRP, so try that, or philz as suggested by audit13. Just watch the flash progress for any errors and copy the log.

[Q] Device bricked after trying to change ROM

I just bricked my galaxy nexus by trying to install Shiny ROM. I've got a (europe) maguro galaxy nexus which ran PA before, but I wanted to update as it became extremely slow at times.
Using TWRP v2.5.0.0 I did a factory reset(data, cache and dalvik wipe). I then tried to install ShinyROM, but it gave the following error:
Updating partition details...
Formatting Cache using make_ext4fs...
Done.
Wiping data without wiping /data/media ...
Done.
Updating partition details...
Installing '/sdcard/modsnstuff/ShinyROM_maguro_a
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Warning: No file_contexts
Installing Shiny ROM build 062114
for maguro
set_metadata_recursive: some changes failed
E: Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/modsnstuff/ShinyROM_
Updating partition details...
Click to expand...
Click to collapse
I also put a new PA version on the phone, which gave a similar error.
I tried using the android toolkit to get into adb recovery and flash a new rom somehow. I did not succeed to install the drivers successfully, which is probably because I am not able to boot into android. I do not see how I can use the toolkit now, and since I barely know what it does and I would not know how to install the drivers.
What can I do to correctly install the new ROM, or at least get it to boot in any version of android?

inasm said:
I just bricked my galaxy nexus by trying to install Shiny ROM. I've got a (europe) maguro galaxy nexus which ran PA before, but I wanted to update as it became extremely slow at times.
Using TWRP v2.5.0.0 I did a factory reset(data, cache and dalvik wipe). I then tried to install ShinyROM, but it gave the following error:
I also put a new PA version on the phone, which gave a similar error.
I tried using the android toolkit to get into adb recovery and flash a new rom somehow. I did not succeed to install the drivers successfully, which is probably because I am not able to boot into android. I do not see how I can use the toolkit now, and since I barely know what it does and I would not know how to install the drivers.
What can I do to correctly install the new ROM, or at least get it to boot in any version of android?
Click to expand...
Click to collapse
Search for using fastboot to return to stock Google image(stock ROM). Then install custom recovery again and flash a ROM.
This phone is nearly impossible to brick

DR3W5K1 said:
Search for using fastboot to return to stock Google image(stock ROM). Then install custom recovery again and flash a ROM.
This phone is nearly impossible to brick
Click to expand...
Click to collapse
Thanks a lot for the reply, trying it now. Apologies if I misused the word brick btw.

inasm said:
Thanks a lot for the reply, trying it now. Apologies if I misused the word brick btw.
Click to expand...
Click to collapse
No need to apologize just didn't want you to think that you were stuck.
Also it will be very beneficial to study up on adb along with fastboot.
If you learn these two things you will be able to get out of just about any sticky situation you run into.
PS The most difficult part is getting the drivers installed.

DR3W5K1 said:
No need to apologize just didn't want you to think that you were stuck.
Also it will be very beneficial to study up on adb along with fastboot.
If you learn these two things you will be able to get out of just about any sticky situation you run into.
PS The most difficult part is getting the drivers installed.
Click to expand...
Click to collapse
Would you happen to have a link to a post of some sort? I tried downloading the drivers, then installing them using device manager which didn't work, since windows said they were up to date already. All other guides I found to install the right drivers were with a working android version. Even the soft brick guides assume you have installed the drivers already.

inasm said:
Would you happen to have a link to a post of some sort? I tried downloading the drivers, then installing them using device manager which didn't work, since windows said they were up to date already. All other guides I found to install the right drivers were with a working android version. Even the soft brick guides assume you have installed the drivers already.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1583801. Use this for driver issues.
http://forum.xda-developers.com/galaxy-nexus/general/how-to-return-to-stock-galaxy-nexus-t1626895 use this to return to stock.
With these guides you can fix it!

DR3W5K1 said:
http://forum.xda-developers.com/showthread.php?t=1583801. Use this for driver issues.
http://forum.xda-developers.com/galaxy-nexus/general/how-to-return-to-stock-galaxy-nexus-t1626895 use this to return to stock.
With these guides you can fix it!
Click to expand...
Click to collapse
The driver still seems to refuse to work. It keeps saying the latest driver is installed. I am using Windows 7 in stead of 8, which is why the guide might not apply 100% to me.
When I use the Android ToolKit and I try to flash the google ROM, it does detect a device in ADB MODE, and it gets the serial number, but it gets stuck on "Waiting for adb Mode". Does this mean the drivers are already correctly installed?
EDIT:
I remembered that I downloaded an old version of PA a long time ago using goo manager, which was still on my phone. ADB drivers are also installed now it seems, now I just have to install the 4.4 version correctly.
Thanks a lot for your help!

inasm said:
The driver still seems to refuse to work. It keeps saying the latest driver is installed. I am using Windows 7 in stead of 8, which is why the guide might not apply 100% to me.
When I use the Android ToolKit and I try to flash the google ROM, it does detect a device in ADB MODE, and it gets the serial number, but it gets stuck on "Waiting for adb Mode". Does this mean the drivers are already correctly installed?
EDIT:
I remembered that I downloaded an old version of PA a long time ago using goo manager, which was still on my phone. ADB drivers are also installed now it seems, now I just have to install the 4.4 version correctly.
Thanks a lot for your help!
Click to expand...
Click to collapse
Your welcome but you should have been using fastboot instead of adb. For future reference they are two different things

[Q] Need help in solving "Unfortunately, settings have stopped working" error

[Q] Need help in solving "Unfortunately, settings have stopped working" error
Problem: My unrooted SGH-I747 model AT&T GS3 recently gave me this error whenever trying to access the settings. The error shows up even after a full factory reset and I can no longer access my phone. Stuck a little after the language selection in the beginning stages of the setup.
Attempted fixes: Obviously, the initial factory reset. Then clearing the cache + factory reset.
After those failed to work, I tried to flash to a AT&T stock rom from this forum (http://forum.xda-developers.com/showthread.php?p=33570269#post33570269) using Odin. I tried to use the first row of downloads but the first row but it did not have a MD5 file, so I used the second row of downloads instead but this rom failed to install. My guess is that it may be too old of a version.
I would appreciate any help.
[SOLVED]
The problem may have arose from a critical error in the phone's software that had affected the OS system of the phone. I resolved the issue by flashing a new custom OS (cyanogenmod) to my phone. These are the steps that I took:
1. Installing Odin (http://forum.xda-developers.com/showthread.php?t=1722686)
2. Rooting my cellphone with CFAutoRoot using Odin (http://forum.xda-developers.com/showthread.php?t=1725839)
3. Installing a custom recovery TWRP -- highly recommended very user friendly (http://forum.xda-developers.com/showthread.php?t=1793224)
4. Installing a new custom rom through TWRP-- used Cyanogen (http://forum.xda-developers.com/showthread.php?t=1778270)
5. Installing gapps (http://opengapps.org/?api=5.1&variant=nano)
6. Identifying the correct bootloader by downloading and installing Samsung Phone Info by vndnguyen through the Play Store.
7. Installing the correct bootloader and modem (http://forum.xda-developers.com/galaxy-s3-att/general/rooted-ucufnj1-stock-rom-t2985006)
Please refer to respective installation guides for more instructions regarding installation of any new software.
I hope this helps anyone who may have run into the same problem.

Before attempting to flash anything, confirm the bootloader on your phone. An easy way to determine if the bootloader is 4.3 or newer, boot into download mode. If you see anything about warranty bit, your phone has at least a 4.3 bootloader and no attempts should be made to flash anything from sammobile.com.
If you have a 4.3 or newer bootloader, I recommend flashing a custom recovery such as TWRP, and then flashing a stock ROM from recovery.

First off, thank you for the reply audit!
Now I have officially rooted my phone using CF-Autoroot and have installed TWRP. I have also confirmed that the bootloader is at least 4.3 because it does show the warranty bit.
Which of the stock roms are compatible with this bootloader?

Do you want to stay on a stock ROM? If not, you could flash a custom ROM such as cm12.1 using TWRP. Once you have flashed a custom ROM, you can look under settings to determine the baseband on the phone which is another clue as to which bootloader is on your phone.

audit13 said:
Do you want to stay on a stock ROM? If not, you could flash a custom ROM such as cm12.1 using TWRP. Once you have flashed a custom ROM, you can look under settings to determine the baseband on the phone which is another clue as to which bootloader is on your phone.
Click to expand...
Click to collapse
Just to be clear, cm12.1 is the cyanogenMod nightly?

Yup. If you flash it, your baseband may be unknown which tells me you are probably not running a 4.4.2 bootloader and modem.

audit13 said:
Yup. If you flash it, your baseband may be unknown which tells me you are probably not running a 4.4.2 bootloader and modem.
Click to expand...
Click to collapse
I'll try it out and see if I can get past the language screen this time.

Got the latest Cyanogenmod Zip file onto my phone. Tried flashing it through TWRP with the install option but it failed.
Log reads that no MDS file was found, detected filesystem ext4 for /dev/block/platform msm_sdcc.1/byname system. Can't install this package on top of incompatible data.

CM12.1 won't have an md5 file. You're trying to install cm12.1 for the d2att or d2lte? You're running the latest TWRP which I believe is 2.8.7.0? or 2.8.7.1?

5K posts.
"all i can really do , is stay out of my own way and let the will of heaven be done"

I'm pretty sure that CM de-unified the variants for CM 12.
From: https://wiki.cyanogenmod.org/w/D2lte_Info
Note: Unified device
Between the release of CM 11 M3 and CM11 M12, all Qualcomm-based variants of this device were merged into a single build: d2lte. The device information pages for the individual variants should be used to reference any device-specific unlock instructions, download recoveries, to build CM 10.2, or to install CM 12.1: d2att, d2cri, d2mtr, d2spr, d2tmo, d2usc, d2vzw.
Click to expand...
Click to collapse
I think this was just to make searching a bit harder/ more complicated.

audit13 said:
CM12.1 won't have an md5 file. You're trying to install cm12.1 for the d2att or d2lte? You're running the latest TWRP which I believe is 2.8.7.0? or 2.8.7.1?
Click to expand...
Click to collapse
For d2att and running 2.8.7.0 for TWRP.

You should be good then.

The file should be left unzipped/unrared when using it right? I'm using it as such but it keeps returning the same error message saying that it won't install it.

Yes, leave it zipped. What is the TWRP error message?

The error log:
detected filesystem ext4 for /dev/block/platform msm_sdcc.1/byname system.
Can't install this package on top of incompatible data.
Please try another package or run a factory reset
E: Error executing updater binary in zip '/sdcard/Download/cm-12.12015913-NIGHTLY-dtatt.zip
Error flashing zip '/sdcard/Download/cm-12.120150913-NIGHTLY-D2att.zip

Weird, did you do a full wipe before trying to install?

Can't believe it was that simple. I thought I had already made the wipe when I did it with the original recovery but making a second wipe through TWRP actually helped make it happen. I finally got through and have full access to my phone.
Unfortunately, the cell service doesn't seem to work but I'm guessing that I need to do more for the set up?
Edit: Not recognizing the sim card for some reason

Sounds like you need to update the bootloader and modem to the older KK version which I think is ne4.

Sorry for the late reply I've been busy the past week. I'm guessing the modem won't work without the proper bootloader? I've tried flashing the latest and original modem from the Modem list (http://forum.xda-developers.com/showthread.php?t=1831898). While they installed successfully I still don't get a signal.
I was worried which bootloader to take because it may lead to bricking. Which one are you referring to and are they in the Bootloader updates topic here? (http://forum.xda-developers.com/showthread.php?t=2321310)