Introduction
This package will totally reset your Infuse 4G to UCKJ4 . This package is intended for use on AT&T, however it will work with any device if you reset APN.
This package includes:
Repartitioning: Repartition to stock KJ4
Reloading: IBL/PBL, PARAM, SBL, SBL2, Kernel, Recovery, FactoryFS and modem
formatting:Cache and DBdata
This package does not wipe:
EFS(Where your serial number and carrier information is stored)
Data(where your market apps are stored)
SDCard (where your pictures are stored)
You may use this code to reformat the Data and SDCard *2767*3855# There is no way to do this from Download Mode. The code will leave the EFS untouched.
Download:
Download Total Stock UCKJ4
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Instructions:
Get the latest version of java here: http://java.com/en/download/installed.jsp
Put your phone into "Download Mode"
Run the program once, and if it does not work, then check the "Flash Bootloaders" checkbox and flash again
Your device will end up as it came from the factory. You will be asked to set your device up again.
If you would like to install CWM on your device to restore or flash a custom ROM, I have prepared LinuxBozo's Defuse 1.5 kernel in a One-Click package here:
Download Defuse 1.5
To flash this package, follow the directions above.
Please note, this may not boot your device, but it will allow you to use CWM recovery. Hold the 3 button combo without USB plugged in to activate CWM mode.
How I created these package:
I obtained the stock 2.3 bootloader from a link LinuxBozo gave me
The stock part.pit came from my device using Heimdall(Download Pit option)
Uploaded the UCKJ4 firmware to my device
Performed "wipe data" in recovery mode
Exploited the root prompt at the battery charge sequence using UART and grabbed the stock, wiped dbdata/cache partitions and params.lfs partition
Created a Heimdall tar.gz package using Heimdall 1.3
Finally, I used my Heimdall One-Click *BETA* packager to generate these one-clicks
This procedure can be reproduced for any custom ROM in the future by using the dd command to obtain the factoryfs and kernels from any device. Bootloaders may be obtained from within this package as it is an executable JAR file which can be unzipped.
Thanks
Cranky...
Nice, I'll be using this when needed.
Also, you have a typo in your title, it's 2.3.6. :]
Sent from my phone. :3
AdamOutler said:
This is the current version pushed out on new Captivate devices today.
Click to expand...
Click to collapse
Wait, Captivate devices got an official update today? Wow.
Any downsides we should be worried about?
I copied the first paragraph from another post I made. That was a typo.
You might want to put the defuse kernel in another thread. Don't want people flashing 2.2.1 kernels on 2.3.6
Also might want to make a Hellraiser kernel version for people that Odin'd the leak or Rogers users that want a quick root/cwm without Odin
Dani897 said:
You might want to put the defuse kernel in another thread. Don't want people flashing 2.2.1 kernels on 2.3.6
Also might want to make a Hellraiser kernel version for people that Odin'd the leak or Rogers users that want a quick root/cwm without Odin
Click to expand...
Click to collapse
This package is posted as a method to get your phone back to stock and the defuse kernel provides easy access to cwm.. I had it around and it works. I tested before posting. Its there because it will give CWM. I will probly post a new one later with a 2.3.6 kernel but for now, this is how you get CWM on your device from Linux or Mac with one click.
I needed to flash the bootloader in order to get mine to boot up, but its been running for ~1 hour now and looks pretty nice. Offhand, do you know if HDMI is working for you? I'll go ahead and test after posting and I'll include my results here.
Edit: Nevermind, found cross-post with the results I needed. Stock kernel, HDMI works, rooted kernel (Entropy, etc.) breaks HDMI as they're based on Rogers roms.
HOw TO ROOT THIS ROM
cookieboy said:
HOw TO ROOT THIS ROM
Click to expand...
Click to collapse
Use defuse kernel, boot into CWM, then flash a rooted CWM zip. This ROM is very new.
nice work!
Only thing i noticed is that their is no stock ringtones with this rom.
Sent from my SAMSUNG-SGH-I997 using XDA App
Also want to add when you open facebook newsfeed, it wont let you select news, status updates, photos and etc. If you refresh the page while in app it will show you the list. Small bug i came acrossed. Let ya know if i find more.
Sent from my SAMSUNG-SGH-I997 using XDA App
After running stock UCKJ4 for a few hours, I seem to be having an issue where I get an error message saying my Google Talk authentication is not working, to make sure Chat is enabled on my account, as well as returning errors any time I try to install things from the Market. Anyone else running into this? Going to try removing and re-adding my Google account.
Edit: Crap, apparently you can't remove it without factory resetting. Damnsauce.
After factory resetting, things appear to be fixed. Thanks again for this package!
Sent from my SAMSUNG-SGH-I997 using xda premium
adalgiso said:
After factory resetting, things appear to be fixed. Thanks again for this package!
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
I had a similar problem. Downloading apps from market told me I had Insufficient space on the device. Clearing cache and Factory reset fixed the issue, Incase any others run into this.
Axiomkid said:
I had a similar problem. Downloading apps from market told me I had Insufficient space on the device. Clearing cache and Factory reset fixed the issue, Incase any others run into this.
Click to expand...
Click to collapse
Just to clarify, I was not receiving the insufficient space issue, I don't remember the exact wordage. 'There was an error' and nothing else.
---------- Post added at 12:30 PM ---------- Previous post was at 11:35 AM ----------
Attempting to root using zergRush exploit from here: http://forum.xda-developers.com/showthread.php?t=1321582
Will post results.
Edit: Check my thread here: http://forum.xda-developers.com/showthread.php?t=1332656
i was trying this everything seemed to work then it wouldnt boot so i did the flash bootloaders like it said, now nothing will work, not even the screen please help, im in dire need
steezinstangl said:
i was trying this everything seemed to work then it wouldnt boot so i did the flash bootloaders like it said, now nothing will work, not even the screen please help, im in dire need
Click to expand...
Click to collapse
oh boy, there is always a risk of permabricking when flashing bootloaders, (unless you did the unbrickable mod or have a jtag)
ok to start to see if you are actually permabricked;
1 pull your battery out
2 get a good micro usb cable, try this with more than one if you have to, if you had a problem flashing it may have been caused by the cable.
3 insert the cable into the usb port and into the computer.
4 hold both volumes with the phone face down, while the volumes are held slide the battery into position. see if the phone enters the download warning screen, it will ask you if you are sure you want to flash custom firmware, hit volume up. it may also go into a phone + computer screen or strait into download mode. all are good signs.
if you end up in download mode congrats! reflash!
if the screen is still black id recommend sending the device to connexion for jtag flashing or to adam if he is willing to repair it, these methods will void the warranty do to hardware modification (the repair may require soldering) . you may also atempt a warranty repair with samsung or insurance replacement with att but if they find that you are responsible samsung will charge you for the repair and im not sure what the insurance company will do.
Related
Close thread
charlieb620 said:
Ok. These are the only roms that load on my mytouch 4g.
RoyalThunder
IceGlacier
CM7
The rest of the roms just hang at the bootsplash and i have to pull battery and restore to previous rom.
Click to expand...
Click to collapse
Make sure tour using clockwork 3.0.0.6
Sent from my HTC Glacier using XDA Premium App
Do some reading. You are using the wrong recovery version for the roms you are flashing.....
Sent from my HTC Glacier using XDA App
Umm, well, he said icedglacier works (2.2) and cm7 (2.3) so I don't see how he can be using the wrong recovery.
lowandbehold said:
Umm, well, he said icedglacier works (2.2) and cm7 (2.3) so I don't see how he can be using the wrong recovery.
Click to expand...
Click to collapse
the problem exists between the phone and the couch.
op, review your process and try again.
mark manning said:
Make sure tour using clockwork 3.0.0.6
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
I have 3.0.0.6 loaded already. What should I try next?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my HTC Glacier using XDA Premium App
darinmc said:
the problem exists between the phone and the couch.
op, review your process and try again.
Click to expand...
Click to collapse
I really don't understand what my quote had to do with your post...but ok. Like I said, the poster (not myself) is on 3.0.0.6, and if the other people would have read his original post they would have realized that since he said both froyo and gingerbread ROM's are working.
Now, are you doing a full wipe before trying a different ROM, and if so, are you going into mounts and storage and formatting boot and system? It's not always a requirement of flashing a ROM, but might solve your problem.
ok i tried that after i flashed cm7 now when i try to restore back into my iceglacier or my thunderbolt rom my phone just hangs what do i need to do to restore my backups properly right now my phone only boots into cm7 do i have to downgrade my clockwork recovery in rom manager or something?
lowandbehold said:
I really don't understand what my quote had to do with your post...but ok. Like I said, the poster (not myself) is on 3.0.0.6, and if the other people would have read his original post they would have realized that since he said both froyo and gingerbread ROM's are working.
Now, are you doing a full wipe before trying a different ROM, and if so, are you going into mounts and storage and formatting boot and system? It's not always a requirement of flashing a ROM, but might solve your problem.
Click to expand...
Click to collapse
he could have used 2.5.1.x to flash his first two ROMs, upgraded to 3.0.0.5 and flashed CM7, then tried flashing other froyo ROMs to no success. But that's beside the point. I don't know why I quoted you other than to point out that you made a lot of assumptions about what he did or didn't do and yet questioned the assumptions of others. The biggest problem is that very little information was given, forcing people to fish for info like we are playing fix his phone pictionary. Usually when someone doesn't give a lot of information about a problem it's because they didn't take the time to learn about what they were doing like they should have...
to op, if you want people to take the time to help you, take the time to explain what you did and what went wrong.
darinmc said:
he could have used 2.5.1.x to flash his first two ROMs, upgraded to 3.0.0.5 and flashed CM7, then tried flashing other froyo ROMs to no success. But that's beside the point. I don't know why I quoted you other than to point out that you made a lot of assumptions about what he did or didn't do and yet questioned the assumptions of others. The biggest problem is that very little information was given, forcing people to fish for info like we are playing fix his phone pictionary. Usually when someone doesn't give a lot of information about a problem it's because they didn't take the time to learn about what they were doing like they should have...
to op, if you want people to take the time to help you, take the time to explain what you did and what went wrong.
Click to expand...
Click to collapse
phone was shipped to me with cm7 rc3 on it. i flashed thunderbolt rom made a backup and than flashed ice glacier and made a back up. i tested out another gingerbread rom and didnt like so i wanted to go back to my thunderbolt rom. i went into cwm and picked restore backup. the whole process went but now my phone just hangs at the mytouch screen. the only thing im able to do now is boot back into cm7. it seems like i can only boot into gingerbread now.
are you wiping data at all? wiping cache partition and dalvik cache? I've never seen ROM Manager show 3.0.0.6, and since I don't have RM Premium out of curiosity is that the lastest version? How did you get the 3.0.0.6 recovery on your phone? Have you done all backup/restore from Rom Manager, or did you manually go into recovery? Did you follow the directions in the op of the ROM you were having trouble installing or did you just flash? by "boot back into CM7" do you mean restore your CM7 backup? what do you mean by "another gingerbread ROM?"
Answer these questions and someone MIGHT be able to begin to understand your problem enough so that they can help you.
My understanding is CW 3.0.0.6 is just a modified version of 3.0.0.5 to allow us to flash both Ext 2 and Ext 4. It's readily available in this forum.
Sent from my HTC Glacier using Tapatalk
charlieb620 said:
phone was shipped to me with cm7 rc3 on it. i flashed thunderbolt rom made a backup and than flashed ice glacier and made a back up. i tested out another gingerbread rom and didnt like so i wanted to go back to my thunderbolt rom. i went into cwm and picked restore backup. the whole process went but now my phone just hangs at the mytouch screen. the only thing im able to do now is boot back into cm7. it seems like i can only boot into gingerbread now.
Click to expand...
Click to collapse
darinmc said:
are you wiping data at all? wiping cache partition and dalvik cache? I've never seen ROM Manager show 3.0.0.6, and since I don't have RM Premium out of curiosity is that the lastest version? How did you get the 3.0.0.6 recovery on your phone? Have you done all backup/restore from Rom Manager, or did you manually go into recovery? Did you follow the directions in the op of the ROM you were having trouble installing or did you just flash? by "boot back into CM7" do you mean restore your CM7 backup? what do you mean by "another gingerbread ROM?"
Answer these questions and someone MIGHT be able to begin to understand your problem enough so that they can help you.
Click to expand...
Click to collapse
I am not sure what you have going on but I too havent ever seen Rom Manager show 3.0.0.6 but I too dont have the premium version. I saw you posted in my thread but you left alot of stuff out of your post. Like that you were having trouble flashing roms. My suggestion would be to download the latest rom manager and then download and flash the zip from my thread. Then replace your recovery with that one and try flashing some roms. Also if you have tried flashing Royal Glacier and cant, you can also check and make sure that the MD5 sums match with whats in the OP of the thread and your downloaded rom. I will be happy to try and help in any way I can. If you still cant get it then we need to get you set up with adb and have you send a logcat so I can try and see whats going on during boot.
You are most likely not running 3.0.0.6.
3.0.0.6 should have orange text where as 3.0.0.5 has green text.
cw 3.0.0.6 is technically not released yet and would not show up in the rom manager as in your pic. Something just seems weird with that. I do have the premium version as well, and have never seen that. I attached a thumbnail below for you to reference.
If for some reason you do have 3.0.0.6 installed re-download it and re-flash the image. That should take care of your problem.
I figured it out.
charlieb620 said:
I figured it out.
Click to expand...
Click to collapse
Mind sharing the answer?
I have my friend's galaxy s 4g and he wanted me to root it then flash custom rom,
I didn't pay attention since it says galaxy s on the back, I just downloaded a rom and flashed it but phone already messed up.
right after flashed it, got this screen http://i.imgur.com/NIYK2.jpg (!) and somehow i was able to skip it and get galaxy boot logo then phone keeps restarting.. tried to put it into downloading mode, but no luck, computer say usb device cannot be recognized, I even tried different usb ports and different computer, noluck.
Tried to find solutions by using search but nothing.. I am thinking to buy usb jig.
Any advise?
Lol. That sucks. Maybe next time you will do a little searching and reading up.
Now would be a good time to learn to search. You are the 10000 person to do this.
Look and you will find your answer.
Also.. this should be in Q and A.
Sent from my SGH-T959V using XDA App
Well, this does happens a lot. It'd be nice if odin could recognize which phone does the ROM you're about to install belongs to, and what phone is connected. If they didn't match, odin could warn you before flashing. And this wouldn't be happening as often.
Sent from my SGH-T959V using XDA App
Please use the Q&A Forum for questions Thanks
Moving to Q&A
try this http://forum.xda-developers.com/showthread.php?t=1117990
but main problem is I can't go anywhere.
I get this when I plug into computer or to the wall charger.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and I get this if I power it on without inserting an usb, nothing more than that, phone keeps restarting without usb
Have you tried:
Remove the battery
Plug in the USB cable
Hold down the VOL UP & VOL DOWN at the same time while putting the battery in
That might get you into download mode.
stephen_w said:
Have you tried:
Remove the battery
Plug in the USB cable
Hold down the VOL UP & VOL DOWN at the same time while putting the battery in
That might get you into download mode.
Click to expand...
Click to collapse
Ok I did, I used odin and stock firmware to flash then this came up and wont go away,
BUT ODIN still can see the phone
You probably need to flash a good ROM with good bootloaders. If you're not worried about going to GB, you can do this:
Grab chadster's KG4 here: http://forum.xda-developers.com/show....php?t=1183413
It has 4 files:
Put CODE_T959VUVKG4_CL1385158_REV00_user_low_noship.ta r.md5 in PDA
Put Hawk_Sidekick_VibrantPlus_831.pit in PIT
Put SGH-T959V-CSC-TMB-VIBRANTP.tar.md5 in CSC
Put T959VUVKG4-Phone-CL1037720.tar.md5 in PHONE
Let ODIN decide what needs to be checked & flash.
link doesn't work
labrea said:
link doesn't work
Click to expand...
Click to collapse
Sorry about that
http://forum.xda-developers.com/showthread.php?t=1183413
stephen_w said:
Have you tried:
Remove the battery
Plug in the USB cable
Hold down the VOL UP & VOL DOWN at the same time while putting the battery in
That might get you into download mode.
Click to expand...
Click to collapse
stephen_w said:
Sorry about that
http://forum.xda-developers.com/showthread.php?t=1183413
Click to expand...
Click to collapse
I am downloading it, 10 mins left.
Last time when I tried to flash with odin 1.85, I got this error and it stucked, 1.70 didn't even work, failed in secs
Will try with yours
stephen_w said:
Sorry about that
http://forum.xda-developers.com/showthread.php?t=1183413
Click to expand...
Click to collapse
You know what.
YOU ARE THE MAN.!
It worked.
I cannot believe this crap works now.
Thank you so much,
now, next step is, root and custom fw (my friend wants to use hotspot, it's limited with custom fw)
can you help?
labrea said:
You know what.
YOU ARE THE MAN.!
It worked.
I cannot believe this crap works now.
Thank you so much,
now, next step is, root and custom fw (my friend wants to use hotspot, it's limited with custom fw)
can you help?
Click to expand...
Click to collapse
May I suggest doing some reading and research before you test the waters again?
Sent from my SGH-T959V using XDA App
stephen_w said:
Sorry about that
http://forum.xda-developers.com/showthread.php?t=1183413
Click to expand...
Click to collapse
camalus said:
May I suggest doing some reading and research before you test the waters again?
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
Well,
You are right, I'm also searching at the same time
labrea said:
You know what.
YOU ARE THE MAN.!
It worked.
I cannot believe this crap works now.
Thank you so much,
now, next step is, root and custom fw (my friend wants to use hotspot, it's limited with custom fw)
can you help?
Click to expand...
Click to collapse
Awesome, glad it's working If you're wanting root, the easiest way (for me) is to flash one of drhonk's kernels from here:
http://forum.xda-developers.com/showthread.php?t=1194032
Make sure you grab the one that matches the ROM you're on (KG4 in this case). Flash it via ODIN (put it in the PDA spot), and flash. Those will give you CWM, root, & voodoo.
Before you do that, though, I would update to a newer GB ROM. KJ6 is the latest & people have reported better wifi with it. I'm running the KJ6 ROM, drhonk's KJ1 kernel, with Adrenaline Shot v12 and my phone runs great.
stephen_w said:
Awesome, glad it's working If you're wanting root, the easiest way (for me) is to flash one of drhonk's kernels from here:
http://forum.xda-developers.com/showthread.php?t=1194032
Make sure you grab the one that matches the ROM you're on (KG4 in this case). Flash it via ODIN (put it in the PDA spot), and flash. Those will give you CWM, root, & voodoo.
Before you do that, though, I would update to a newer GB ROM. KJ6 is the latest & people have reported better wifi with it. I'm running the KJ6 ROM, drhonk's KJ1 kernel, with Adrenaline Shot v12 and my phone runs great.
Click to expand...
Click to collapse
I don't want to flash wrong kernel or something like I did many times today, can you provide a link for KG6? should I follow same steps as I did before with Odin?
Thanks
labrea said:
I don't want to flash wrong kernel or something like I did many times today, can you provide a link for KJ6? should I follow same steps as I did before with Odin?
Thanks
Click to expand...
Click to collapse
LOL, I don't blame you for being leery. KJ6 is here:
http://forum.xda-developers.com/showthread.php?t=1323521
All you have to do is put T959VUVKJ6-REV00-home-low-CL694130.tar.md5 in the PDA section, leave the check boxes alone, and flash it.
stephen_w said:
LOL, I don't blame you for being leery. KJ6 is here:
http://forum.xda-developers.com/showthread.php?t=1323521
All you have to do is put T959VUVKJ6-REV00-home-low-CL694130.tar.md5 in the PDA section, leave the check boxes alone, and flash it.
Click to expand...
Click to collapse
I just found one of your post and going to use it;
http://forum.xda-developers.com/showpost.php?p=18992345&postcount=4
labrea said:
I just found one of your post and going to use it;
http://forum.xda-developers.com/showpost.php?p=18992345&postcount=4
Click to expand...
Click to collapse
Cool deal. That will basically have your phone set up like mine. dsexton's Adrenaline Shot really makes a difference
UPDATE 8-18-12: OFFICIAL CYANOGENMOD NIGHTLIES ARE UP.
Hey Guys, I haven't seen anyone post this yet so I figured I'd give it a shot. First and foremost, I take ABSOLUTELY NO CREDIT FOR ANYTHING IN THIS POST. Let it be known that none of this is my work and the purpose of this post is to consolidate information into an easy-to-follow guide. Also, I take no responsibility for any damage you do to your own phone. It's your responsibility to understand the risks involved and do your research before you make ANY modifications. If you'd like to use this guide for a project you're working on or another thread, that's fine with me. All I ask is that you give credit where it's due.
BEFORE WE START. If you cannot follow detailed instructions, please don't bother using this guide as you're only going to waste your own time as well as mine. I won't be answering any questions or providing support for problems that are clearly covered in the guide.
Now that we've achieved an unlocked bootloader, Cyanogenmod's team is already at work and has a build of CM10 up and running. (It's technically an alpha, but for me EVERYTHING works perfectly: data, wifi, bluetooth, GPS, MMS, camera, camcorder, the whole nine. The only thing I've found to NOT be working is NFC). The post can be found on both Cyanogenmod and Austen Dicken's Google+ page. Those can be found here:
https://plus.google.com/117962666888533781522/posts
A word of caution:
Since I'm not a Cyanogenmod developer, I have no control on the stability of their posted builds. So if you go through the guide and your MMS isn't working, there's not a whole lot I or anybody else can do for you at the moment considering these are still alpha builds. Although I mentioned everything works currently for me, I can neither guarantee this nor help you troubleshoot technical issues as I am not the developer of the ROM itself. On the other hand, if you have any questions or problems following the guide, I'm happy to help you out to the best of my ability.
For this to work, you must be ROOTED and have an UNLOCKED bootloader. I'm not going to make a super-detailed write up on how to achieve both of these, but here's a general outline of steps for those that are new here. If you're already rooted and have your bootloader unlocked, you can skip straight to step 4.
Pre-install:
First, BACKUP EVERYTHING. Do a nandroid backup and backup your apps and data in Titanium if desired.
Install the latest Samsung USB drivers so your phone and your computer don't have any connection problems. Those can be found here:
http://www.samsung.com/us/support/owners/product/SCH-I535MBBVZW?
on the bottom under Manuals/Downloads and then Software.
I highly recommend backing up your IMEI incase something goes wrong. I'm not going to cover that here, all info can be found in this post:
http://forum.xda-developers.com/showthread.php?t=1791291&highlight=backup
You have been warned.
You need to have your SD Card formatted to FAT32. exFAT WILL NOT WORK. So if you're like me and have a 64GB SD card, neither Android nor windows will let you format to FAT32 natively, so you have a few options.
Using command prompt within windows:
http://www.xoomforums.com/forum/mot...-format-sd-card-especially-64gb-fat-32-a.html
Use a disk management program like Acronis Disk Director (I think they may have a free trial but don't quote me on that).
http://www.acronis.com/homecomputing/products/diskdirector/
Then, you may want to Odin back to stock using the latest Samsung firmware. Now, you DO NOT need to Odin back to stock for the rest of this guide to work. But it should fix any 4G/3G data problems you may have been having on custom k-exec ROMs and I thought it was a good idea to start completely fresh now that we have total freedom. So if you were having bad experience on any custom ROMs with a flaky data connection or GPS taking a long time to lock, give it a try and see if it fixes things for you.
If you're going to give it a try, both the Odin program and stock Odin firmware can be found in this post:
http://forum.xda-developers.com/showthread.php?t=1755386
Download the latest version of Odin and the latest stock firmware version. Extract the Odin zip and load it up. Click the PDA button, find the stock firmware you just downloaded. Boot into download mode on your phone by powering down, then powering back up while holding the home and volume down buttons. Click start in the odin window. This process should take a while. After your phone reboots, get through the setup and dial *2767*3855#. Your phone will reset and you'll be COMPLETELY back to stock and any radio/hardware connection issues should be fixed. If you're still having problems let me know.
Now, to the fun part.
1. Root your phone.
NoxiousNinja's GS3DebugFSRoot Tool is the easiest and most foolproof way I've found. Read the directions in the post and follow the instructions in the command prompt window. Very easy and lightweight.
http://forum.xda-developers.com/showthread.php?t=1792342
As you continue throughout this process, pay careful attention to the prompts as it will ask you for [y/n] responses that you must confirm. After finishing, go into the newly installed Superuser app and on the far left panel, click where it says "tap to check for updates." Then click "update" on the bottom EVEN IF YOU HAVE THE NEWEST VERSION. I don't know why it works, but it does.
2. Flash a custom recovery.
Download mmmeff's EZ Recovery flashing app from the play store. Just search for "EZ Recovery" and you'll find it. Once installed, make sure you allow root access, then select "CWM 6.0.1.0" from the dropdown (NOT THE TOUCH VERSION AND NOT TWRP . It just makes it easier on everyone if something goes wrong. I can personally confirm that the touch version is incompatible. Some users are reporting TWRP is working fine, so you can try that at your own risk but I can't provide any support if it doesn't work for you since I haven't tried it myself.), make sure you have the "Recovery" toggle selected on the left, and click "flash recovery". Don't worry about rebooting yet as we still have a few things to do. The thread for the app can be found at:
http://rootzwiki.com/topic/29698-72...-recovery-flashing-app-ya-dingus/page__st__10
3. Unlock your bootloader.
I've also chosen to use mmmeff's Bootloader unlocking app from the play store for this guide as it is universally acceptable no matter what operating system everyone is running. In the play store, search for "GS3 EZ Unlock". Once installed, again make sure you allow root access and then click the HUGE button in the middle. It only takes a few seconds and then you're done. Thread is here:
http://rootzwiki.com/topic/32456-app-ez-unlock-easiest-way-to-unlock-your-bootloader/
4. Flash Cyanogenmod.
First, you'll need some downloads. You can use the Cyanogenmod 10 Alpha build or a nightly CM10 build.
Cyanogenmod 10 ALPHA build:
http://goo.gl/RYzHT
MD5: 3662de3c8942f19dc95ca911207b1602
CM10 Nightlies can be found at:
http://get.cm/?device=d2vzw
Jellybean GAPPS:
http://goo.im/gapps/gapps-jb-20120726-signed.zip
Mirror:
http://www.mediafire.com/?63l7wtwlc09923c
MD5: f62cfe4a827202899919fd932d5246d7
Put both of these zips on the root of your SD card.
Before you get all trigger happy, we need to do some things first.
For those of you who are new at this, I'll say it again, BACKUP EVERYTHING. This next step will wipe everything on your phone.
INSTRUCTIONS FOR FLASHING A NEW INSTALL OF CYANOGENMOD:
Now, boot into recovery (power off and then power back on while holding the home and volume up buttons) and wipe SYSTEM, DATA, CACHE (all can be found in Mounts/Storage menu), and DALVIK CACHE (can be found in advanced menu). A system wipe is not technically necessary but I did it just to make sure I didn't have any problems. Then, go into "install zip from SD card," then "choose zip from SD card". First, flash the Cyanogenmod zip, and after that finishes flash the Gapps zip. Go back a couple levels, click "reboot system now," and you're done!
INSTRUCTIONS FOR FLASHING AN UPDATED BUILD OF CYANOGENMOD
Now that you have a working install of Cyanogenmod, it gets a lot easier. If you're currently on the Alpha build and are switching to the new nightly builds, I would HIGHLY recommend you perform a FULL wipe including system, data, and both caches. Some people moved from the alpha to nightlies and were having problems so if you do a full wipe the first time you'll be fine. If you want to update from a nightly build to a newer nightly, all you should need to do is wipe both caches.
I hope this helped at least a few people, I tried to arrange it into as easy of a guide as I could. Please let me know if you see any problems or necessary changes and I'll try to keep this thread updated as new builds are upped. TO EVERYONE THAT IS NEW HERE, PLEASE DO NOT BUG DEVELOPERS WITH STUPID QUESTIONS REGARDING RELEASE DATES OR PROGRESS. I can assure you that they're working hard, we got a full release the day after our bootloader got unlocked. So be patient, nightlies and beta versions of CM and AOKP will come soon enough.
If you're interested, after you're done you can try flashing a new radio and/or kernel. Unless you're having problems, I wouldn't recommend you try this unless you know what you're doing because you could make things worse. Consider yourselves warned. Radios and instructions can be found in Invisiblek's thread here:
http://forum.xda-developers.com/showthread.php?t=1788313
Do some research on kernels, but at the time of writing I can recommend imoseyon's Leankernel. That and instructions are here:
http://rootzwiki.com/topic/32286-kernel-aosp-jb-leankernel-minimalistic-kernel-v05-beta-81612/
N00bs, Both of ^these^ steps above are completely optional and if you do choose to try them THIS THREAD is NOT the place to ask for support. Realize that before you start messing with stuff you don't understand.
If this guide helped you out, please consider hitting the thanks button.
Thanks
As per request, here's some initial screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Are you shure nothing will go wrong if we follow the steps you described. By the way its a great step by step description to get cm10. Can you post some screenshots of your phone. Thank you
I am itching to try it lol
Sent from my SCH-I535 using xda premium
I tried the 8/15 yesterday but flashed back to stock mainly because the phone wasn't seeing my ext SD card. Also it died on me I had to do a battery pull to get it back. I may have to try this out. Also I could not get WiFi tether to work or the built in portable hotspot. It sucks too because I actually pay for the service
Sent from my SCH-I535 using Tapatalk
majmuni said:
Are you shure nothing will go wrong if we follow the steps you described. By the way its a great step by step description to get cm10. Can you post some screenshots of your phone. Thank you
I am itching to try it lol
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I'm in the process of getting some screenshots up, and I can't 100 percent confirm that it will work for you but if you follow the instructions I think theres a great chance
cell128 said:
I tried the 8/15 yesterday but flashed back to stock mainly because the phone wasn't seeing my ext SD card. Also it died on me I had to do a battery pull to get it back. I may have to try this out
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
What do you mean it "wasn't seeing it"? Didn't it show up in certain apps or recovery or what?
snoshreddax21 said:
I'm in the process of getting some screenshots up, and I can't 100 percent confirm that it will work for you but if you follow the instructions I think theres a great chance
What do you mean it "wasn't seeing it"? Didn't it show up in certain apps or recovery or what?
Click to expand...
Click to collapse
I think it was the music app and a bunch of photos
Sent from my Nexus 7 using Tapatalk
Do have a md5 for cm10 file please
Sent from my SCH-I535 using xda premium
Flashed and currently booting hopefully I keep it for a whole day lol. Do love the stock experience better than touchwiz
Sent from my Nexus 7 using Tapatalk
cell128 said:
I think it was the music app and a bunch of photos
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
You might try reformatting your card in your computer, but if that doesnt work I had a similar problem a while ago. For me I had to dig around in the preferences of my music player to direct it to the right folder (it would be mnt/extsdcard/[music folder]). It might be trying to find your music/pictures in the phone's internal memory rather than its SD card.
majmuni said:
Do have a md5 for cm10 file please
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
It was in the post on Cyanogenmod's Google+ page, OP updated. Sorry about that
hmmm idk if i did something wrong the first time but i got the big yellow ! saying to bring my phone to big red about unofficial software going on it and i had to odin back to rooted stock to have access to my phone.....ill try using CWR instead of TWRP in hopes that i didn't screw something up in TWRP since im so familiar w/ CWR
note: i did that before finding this guide, im following this guide to a T and will follow up results tomorrow on it, so not trying to scare anyone from trying it, just saying i used my own method compiled from a few guides on here which consisted of using the root method listed in this guide, TWRP recovery from the unofficial cm10 guide, the cm10 files from cyanogenmods g+, and the gapps file from the cm10 guide haha
digitalsynner85 said:
hmmm idk if i did something wrong the first time but i got the big yellow ! saying to bring my phone to big red about unofficial software going on it and i had to odin back to rooted stock to have access to my phone.....ill try using CWR instead of TWRP in hopes that i didn't screw something up in TWRP since im so familiar w/ CWR
note: i did that before finding this guide, im following this guide to a T and will follow up results tomorrow on it, so not trying to scare anyone from trying it, just saying i used my own method compiled from a few guides on here which consisted of using the root method listed in this guide, TWRP recovery from the unofficial cm10 guide, the cm10 files from cyanogenmods g+, and the gapps file from the cm10 guide haha
Click to expand...
Click to collapse
I'm almost postive TWRP is your problem. I first tried it with the CWM touch version and that didn't work for me either. I think CM10/CM9 are very picky about which recoveries are compatible. Let me know how it goes for you.
digitalsynner85 said:
hmmm idk if i did something wrong the first time but i got the big yellow ! saying to bring my phone to big red about unofficial software going on it and i had to odin back to rooted stock to have access to my phone.....ill try using CWR instead of TWRP in hopes that i didn't screw something up in TWRP since im so familiar w/ CWR
note: i did that before finding this guide, im following this guide to a T and will follow up results tomorrow on it, so not trying to scare anyone from trying it, just saying i used my own method compiled from a few guides on here which consisted of using the root method listed in this guide, TWRP recovery from the unofficial cm10 guide, the cm10 files from cyanogenmods g+, and the gapps file from the cm10 guide haha
Click to expand...
Click to collapse
Make sure you use the non touch recovery 6.something and that you are unlocked. It was probably because you were not unlocked properly
Sent from my Nexus 7 using Tapatalk
cell128 said:
Make sure you use the non touch recovery 6.something and that you are unlocked. It was probably because you were not unlocked properly
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
i used the unlock that was mentioned in the guide as people were reporting it was successful unlocks on the forums so i went ahead and used that.....im making my initial backup right now thru CWM non-touch and im gonna drop the zips for CM10 and gapps and will flash in the morn, im tired lol
one thing i did notice though is that for some reason my drivers are saying hardware id missing, and that only happened after root......i kept my imei but lost my hardware id lmao, i can still drag/drop files onto my phone but i have to switch from MTP to PTP mode for usb settings then switch it back to MTP to get access to the card/phone drives
digitalsynner85 said:
hmmm idk if i did something wrong the first time but i got the big yellow ! saying to bring my phone to big red about unofficial software going on it and i had to odin back to rooted stock to have access to my phone.....ill try using CWR instead of TWRP in hopes that i didn't screw something up in TWRP since im so familiar w/ CWR
note: i did that before finding this guide, im following this guide to a T and will follow up results tomorrow on it, so not trying to scare anyone from trying it, just saying i used my own method compiled from a few guides on here which consisted of using the root method listed in this guide, TWRP recovery from the unofficial cm10 guide, the cm10 files from cyanogenmods g+, and the gapps file from the cm10 guide haha
Click to expand...
Click to collapse
cell128 said:
Make sure you use the non touch recovery 6.something and that you are unlocked. It was probably because you were not unlocked properly
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Cell is correct, make sure you are using the "CWM 6.0.1.0" version. I'll update the OP so others don't get confused.
Thank you for your efforts OP.
Some friendly advice to you newer enthusiasts; be aware of bugs. If the CM team says this is an alpha build, you will more than likely hit some bugs regardless of what you read elsewhere.
Sent from my SCH-I535 using xda premium
jaj6503 said:
Thank you for your efforts OP.
Some friendly advice to you newer enthusiasts; be aware of bugs. If the CM team says this is an alpha build, you will more than likely hit some bugs regardless of what you read elsewhere.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
That's a very good point, and let's just clarify right now, I'm not a cyanogenmod developer and I don't have any control over how stable these builds come out. So if you flash and all is well except your MMS isn't working, I can't do anything for you and you're in the same boat as the rest of us. Thanks for bringing that up, jaj.
Sent from my SCH-I535 using xda app-developers app
I decided to flash tonight.....almost had a heart attack them woke everyone else up when i screamed when it flashed over lol.....great write-up man
Sent from my SCH-I535 using xda premium
digitalsynner85 said:
I decided to flash tonight.....almost had a heart attack them woke everyone else up when i screamed when it flashed over lol.....great write-up man
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Glad to hear it worked out for you
Sent from my SCH-I535 using xda app-developers app
since I have TWRP, how can I change it to CWM? I want to be able to flash this using CWM.
slick_shoes said:
since I have TWRP, how can I change it to CWM? I want to be able to flash this using CWM.
Click to expand...
Click to collapse
If you download the EZ Recovery app from the play store and flash CWM as mentioned in the guide, it will just overwrite the preexisting TWRP image and you can continue on from there.
I'm not understanding why the version or type of recovery matters. What does 6.0.1.0 do that twrp doesn't do except for supporting kexec?
Maybe I misunderstood what recoveries are all about. I had 6.0.1.0 for kexec support. Now that the bootloader is unlocked I'm thinking of going back to twrp.
Flashing the cm10 build should write to system and place a boot.img with the kernel on the phone. I don't see how a recovery would make a difference in doing this.
Forgive me if I missed something. I'm not questioning your intelligence or anything, just a curiosity as I only switched to cwm to use lean kernel with kexec.
Perhaps I missed even more, I see there is an alpha build of cwm that explicitly states it's for unlocked phones. Color me confused.
Sent from my SCH-I535 using xda app-developers app
Thanks to Shabbypenguin for his fastbootable partitions of the Photon Q and thanks to mhous for modifying parts of the Atrix HD .xml file into the Photon Q.
This RSD Package contains 2 xmls for use, one standard one named after the build number, and one that does not flash the stock bootloader and is named as such. Put the one you want for use into RSD Lite and fire away. Have plenty of battery power (or use a Motorola Factory-Style cable or converter from Team Black Hat and you don't have to worry about that) and ALWAYS have your email from Motorola including the unlock code (UNIQUE_KEY) for your device backed up or saved somewhere. Just in case the fastboot locks it without you wanting it do, you'll have that code.
Use this file with Motorola's RSD Lite 5.7 or higher, and with the latest Motorola USB drivers.
Photon Q RSD Files / FXZ files: http://crackflasher.com/dev/mattlgroff/PhotonQ/7.7.1Q-6_SPR-89_ASA-36_SIGNED_CFC.zip
MD5: D864AB70881AF86EB225F0BF1D0A911B
RSD Lite 5.7: http://rootingmydroid.com/FILESYSTEM/DEVELOPMENT/UDPATES/-RSD-LITE/RSDLite57.zip
32 Bit Drivers (5.9): http://rootingmydroid.com/FILESYSTE..._End_User_Driver_Installation_5.9.0_32bit.msi
64 Bit Drivers (5.9): http://rootingmydroid.com/FILESYSTE..._End_User_Driver_Installation_5.9.0_64bit.msi
Happy flashing!
oh if you needed the xml i have that too. in fact i need to talk with you privately about some of the files. i posted up enough to fix anyones phone, but not everything in the zip
Do not flash this, it has bricked my phone... the MD5 for the system image is wrong, and even if you update that in the XML, it still fails to flash and remains stuck at fastboot flash failure. :crying:
Does anyone have the correct system image? I have sent shabbypenquin a PM trying to figure this out.
Gave this a try w the newest drivers & can't get past the system img. Tried several times, decrompressing new each time with no success. Even tried different cables & ports, still no luck.
Anybody have any thoughts on this?
bump...
thats teh word on the street. unfortunately the system.img is pulled from sprints files i dont know what else i could do to fix it
fallnSaint said:
Gave this a try w the newest drivers & can't get past the system img. Tried several times, decrompressing new each time with no success. Even tried different cables & ports, still no luck.
Anybody have any thoughts on this?
Click to expand...
Click to collapse
What state is your phone in? I can try to replicate as long as you're not soft-bricked.
shabbypenguin said:
thats teh word on the street. unfortunately the system.img is pulled from sprints files i dont know what else i could do to fix it
Click to expand...
Click to collapse
Well... $hit...
KitsunePaws said:
What state is your phone in? I can try to replicate as long as you're not soft-bricked.
Click to expand...
Click to collapse
Thanks KP, I'm not bricked; this is how I got into my "sticky" situation (pun totally intended). After system img failed, I was left in fastboot I flashed my recovery & restored. Other than the sticky fastboot, running fine. Well, I still haven't fixed my original problem but, that's for another thread.
Is this the same issue we are having w system.img?
http://www.xda-developers.com/android/swing-and-miss-motorola-razr-i-kernel-source-almost-here/
-Saint
any updates on a working rsd file?
Maxpowersxp said:
any updates on a working rsd file?
Click to expand...
Click to collapse
hopefully Motorola will release one. they said in the FAQs that they are choosing not to at this time, but hopefully they will at some point.
in the meantime, i wish we could make one. at this moment it seems we don't have any way of downgrading back to the original modem? (it was mentioned that there was a new modem in the update?)
Modified FXZ file
yogi2010 said:
hopefully Motorola will release one. they said in the FAQs that they are choosing not to at this time, but hopefully they will at some point.
in the meantime, i wish we could make one. at this moment it seems we don't have any way of downgrading back to the original modem? (it was mentioned that there was a new modem in the update?)
Click to expand...
Click to collapse
This package does not contain system.img!
This is here in case you break something that recovery does not touch.
If anyone has a problem with this being posted, let me know and I will pull the link. Props to mattlgroff for the original.
I edited the original file so that the broken system.img does not flash, everything else is unchanged. I tested this and it works fine.
I offer no support for this & it will wipe your internal sd card, you have been warned.
Modified 7.7.1Q-6_SPR-89_ASA-36_SIGNED_CFC.zip
md5: 851D8157D2A5ADE91E60ACCA0F04EA15
No problems whatsoever. I wanted to personally thank everyone on this forum for all of the dev help. When I unlocked my bootloader, I couldn't get CWM to flash properly, and I wound up erasing my ROM (don't ask lmao) and after 2 frustrating hours the posted boot.img & system.img files saved my phone. I am in everyone's debt, and I am willing to try out anything experimental for y'all now that I have TWRP and two good Nandroids. Thank u again for all of your help and hard work.
Sent from my XT897 using xda premium
I do have an issue each time i install the moto/sprint 77 update, my phone does nothing but reboot. I have a nandroid that is pre-update, but am I missing out on anything by not installing it? I rooted, installed arrgh's kernel and deodexed system before the update. Should i do an odexed system, stock kernel then update?
Sent from my XT897 using xda premium
I encourage all of you to
Sent from my XT897 using xda premium
drakeheart77 said:
I do have an issue each time i install the moto/sprint 77 update, my phone does nothing but reboot. I have a nandroid that is pre-update, but am I missing out on anything by not installing it? I rooted, installed arrgh's kernel and deodexed system before the update. Should i do an odexed system, stock kernel then update?
Sent from my XT897 using xda premium
Click to expand...
Click to collapse
That's what I hear... You would probably get a better response and more help if you posted in the correct thread tho. The update thread is here: http://forum.xda-developers.com/showthread.php?t=1966998
-Saint
Ooops sorry thanks for the correction!
Sent from my XT897 using xda premium
fallnSaint said:
If anyone has a problem with this being posted, let me know and I will pull the link. Props to mattlgroff for the original.
I edited the original file so that the broken system.img does not flash, everything else is unchanged. I tested this and it works fine.
I offer no support for this & it will wipe your internal sd card, you have been warned.
Modified 7.7.1Q-6_SPR-89_ASA-36_SIGNED_CFC.zip
md5: 851D8157D2A5ADE91E60ACCA0F04EA15
Click to expand...
Click to collapse
This kind of worked for me. I was able to get out of the bootloader screen, but now it's stuck on the initial screen with just the red Motorola circle.
Any ideas on what I'm doing wrong?
Stefenatefun said:
This kind of worked for me. I was able to get out of the bootloader screen, but now it's stuck on the initial screen with just the red Motorola circle.
Any ideas on what I'm doing wrong?
Click to expand...
Click to collapse
Without more details as to what caused your problems originally I am kinda in the dark. I would guess that you have a problem with your system img, this RSD package should revert everything except system to stock. The bad news here is that if you did have a custom recovery, you don't anymore. If you have a good backup you will have to fastboot flash recovery again before you can use it. If you don't have a backup see here: http://forum.xda-developers.com/showpost.php?p=33391825&postcount=9
-Saint
fallnSaint said:
Without more details as to what caused your problems originally I am kinda in the dark. I would guess that you have a problem with your system img, this RSD package should revert everything except system to stock. The bad news here is that if you did have a custom recovery, you don't anymore. If you have a good backup you will have to fastboot flash recovery again before you can use it. If you don't have a backup see here: http://forum.xda-developers.com/showpost.php?p=33391825&postcount=9
-Saint
Click to expand...
Click to collapse
What I did was I went into the bootloader, flashed the zip, and rebooted after it finished. Now I am unable to access the bootloader, as the phone won't boot. By now, the battery's dead, anyways. Whenever I turn the device off, it turns on a couple seconds later. I would rather not take it apart, but if I have to, I'll do it.
The only thing I can access is the recovery, which just results in this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hey guys. First I'd like to aplogize for posting so many help threads but I'm trying my best to figure it out on my own.
I was using one-click to stock when my mother dropped something and needed my help urgently, so I told my brother to start it up for me as my phone was already plugged in and connected. I am running the T959W rather than the T959V and my brother clicked on the option to flash bootloaders. The download was completed normally I think. However, my phone will not leave the recovery mode.
Could you guys please help? Thanks.
When flash bootloaders was hit on T959V back to stock, my brother said it said "MODEM UPLOAD FAILED ENDING SESSION". My guess is that it cleared my boot loader and then since it failed while trying to upload the modem, it ended the session without readding a boot loader? It continously says "MODEL UPLOAD FAILED" Whenever I attempt to use the T959V back to stock.
Edit:
I have tired the back to stock for T959W from: http://forum.xda-developers.com/showthread.php?t=1956025
However, I get these error messages.
Kernel is missing because I removed it out of the package hoping maybe it'd solve the problem since it was also failing, but so is recovery...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WayTooGosu said:
Hey guys. First I'd like to aplogize for posting so many help threads but I'm trying my best to figure it out on my own.
I was using one-click to stock when my mother dropped something and needed my help urgently, so I told my brother to start it up for me as my phone was already plugged in and connected. I am running the T959W rather than the T959V and my brother clicked on the option to flash bootloaders. The download was completed normally I think. However, my phone will not leave the recovery mode.
Could you guys please help? Thanks.
Click to expand...
Click to collapse
Try instilling a new ROM
Sent from my SGH-T959V using xda app-developers app
Cooptx said:
Try instilling a new ROM
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
I have tried installing AOKP Milestone 6 by team acid unofficial (ICS) and CM10 (JB) but the same thing keeps occuring.
I think you should look here if you haven't already
http://forum.xda-developers.com/showthread.php?t=1956025
TwitchyEye said:
I think you should look here if you haven't already
http://forum.xda-developers.com/showthread.php?t=1956025
Click to expand...
Click to collapse
Yes I was trying that but for some reason it just kept failing "KERNEL UPLOAD FAILED" "RECOVERY UPLOAD FAILED"
WayTooGosu said:
Yes I was trying that but for some reason it just kept failing "KERNEL UPLOAD FAILED" "RECOVERY UPLOAD FAILED"
Click to expand...
Click to collapse
Sometimes heimdall is finicky so if you know for sure you got the drivers working and you followed instructions properly trying it a couple times in a row might do it....although I guess if you say it keeps failing that would imply more than once...
TwitchyEye said:
Sometimes heimdall is finicky so if you know for sure you got the drivers working and you followed instructions properly trying it a couple times in a row might do it....although I guess if you say it keeps failing that would imply more than once...
Click to expand...
Click to collapse
Yes it has failed every attempt (I''ve tried about 10 times).
At this point you should really start fresh maybe even a different computer and see if you get anywhere. Typically if it's not working it's a driver issue and you gotta get rid of all the drivers related to the phone and reboot, then re-install them using zadig...and maybe reboot again.
TwitchyEye said:
At this point you should really start fresh maybe even a different computer and see if you get anywhere. Typically if it's not working it's a driver issue and you gotta get rid of all the drivers related to the phone and reboot, then re-install them using zadig...and maybe reboot again.
Click to expand...
Click to collapse
I think the driver is being recognized fine because it is being recognized by ZDiag, T959V back to stock program, Hemidall. I am not quite sure what the problem is :|.
WayTooGosu said:
I think the driver is being recognized fine because it is being recognized by ZDiag, T959V back to stock program, Hemidall. I am not quite sure what the problem is :|.
Click to expand...
Click to collapse
Maybe the gods will chime in about now...?
I suggest using a new pc too. Sometimes its a simple conflict that is causing the problem and a different pc will fix it every time.
Try a different cable/port combo? Sometimes cables die at the worst times....
Sent from my SGH-T959V using xda app-developers app
eollie said:
I suggest using a new pc too. Sometimes its a simple conflict that is causing the problem and a different pc will fix it every time.
Click to expand...
Click to collapse
Hmm, I just tried it on my laptop, back to stock T959V flashs just fine however I still ahve the issue of being stuck in recovery mode but I can't get T959W to work still.
WayTooGosu said:
Hmm, I just tried it on my laptop, back to stock T959V flashs just fine however I still ahve the issue of being stuck in recovery mode but I can't get T959W to work still.
Click to expand...
Click to collapse
When flash bootloaders was hit on T959V back to stock, my brother said it said "MODEM UPLOAD FAILED ENDING SESSION". My guess is that it cleared my boot loader and then since it failed while trying to upload the modem, it ended the session without readding a boot loader? It continously says "MODEL UPLOAD FAILED" Whenever I attempt to use the T959V back to stock.
The problem is you are using the V HOC's there is a package for W phones on the forums.
eollie said:
The problem is you are using the V HOC's there is a package for W phones on the forums.
Click to expand...
Click to collapse
Yes I realize that however, I checked the T959W thread and they said there were no bootloaders. And that is likely the thing that is messed up right now. Thanks for your help!
I think there's no way to flash bootloaders on W's and the package that's specifically for the W was designed just for this purpose, to bring back a phone that's messed up from attempting to flash V bootloaders. Have you tried downloading it again? If that's the only one you have trouble with maybe it's just a bad download.
---------- Post added at 11:54 PM ---------- Previous post was at 11:52 PM ----------
Oh also you can go in and uncheck flash modem on the one-click and the rest of it should work just fine. I think.
TwitchyEye said:
I think there's no way to flash bootloaders on W's and the package that's specifically for the W was designed just for this purpose, to bring back a phone that's messed up from attempting to flash V bootloaders. Have you tried downloading it again? If that's the only one you have trouble with maybe it's just a bad download.
---------- Post added at 11:54 PM ---------- Previous post was at 11:52 PM ----------
Oh also you can go in and uncheck flash modem on the one-click and the rest of it should work just fine. I think.
Click to expand...
Click to collapse
How do you disable things from being flashed on the V back to stock?
WayTooGosu said:
How do you disable things from being flashed on the V back to stock?
Click to expand...
Click to collapse
This might help me just get the boot loaders fixed!
here is the deal unless you worked some weird voodoo magic you never flashed the V's bootloaders. There is a partition in there that will not allow it to work properly.
Rereading getochkn's instructions you should not be flashing the bootloaders as he DID NOT include them. Follow his directions to the letter. Dont use the one clicks for the V. I remember chatting with him in IRC while he was trying to figure this out and he could NOT flash a hoc for the V with bootloaders successfully I dont even think it worked without bootloaders.