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
Related
I installed paranandroid and gapps but it was the wrong gapps which caused it to error out during install. so now I have the correct gapps on my SD card but do not know how to access it through my phone since I have no recovery. How do I get gapps back on phone so I can get into recovery?
damn....
PHUCK! ok now I'm really freaking out... flashed gapps and says framework as stopped. wont let me past the front screen saying touch android to begin...
1Android said:
PHUCK! ok now I'm really freaking out... flashed gapps and says framework as stopped. wont let me past the front screen saying touch android to begin...
Click to expand...
Click to collapse
OK, don't panic yet! Basic questions first:
Did you flash a recovery like CWM (Clockworkmod) before trying to flash the rom?
Are you able to get into recovery mode via volume up+power+home?
Why dont you reflash the ROM and then do the right Gapps? That way you wont have any screwed up files at all. If you really screwed it up just Odin back to stock and start again.
just flash the rom over the top then flash the right gapps
I went into panic mode and my head went cloudy. I kept olding down volume instead of volume up. Got into recovery and just doing a restore for now till I can make sure I have all the right files...
thanks guys for answering so quickly.
1Android said:
I went into panic mode and my head went cloudy. I kept olding down volume instead of volume up. Got into recovery and just doing a restore for now till I can make sure I have all the right files...
thanks guys for answering so quickly.
Click to expand...
Click to collapse
Good, now when that's done, lets get you up and running with paranoid. It is alot easier, and generally safer to flash through CWM on the phone itself then through odin on your desktop or even the odin app. What method were you using? And more importantly did you do a IMEI backup?
Haven't done the imei backup yet. Need to though asap. I always flash through cwm but once I installed the wrong gapps (didn't even think of grabbing a JB gapps until after I got my phone into recovery and restored) I had no idea how to get into recovery. Once I found the goo manager in system settings I was able to get into recovery. Tried flashing another gapps file (which again was the wrong file) which is where I really freaked out with my framework and setup no working. Was able to clear my head and remember the volume UP not down. I'm restored now and will leave it on synergy till I do my imei backup. Haven't even looked into it to be honest. Is it difficult? Is paranandroid really much better as far as battery life to worry about taking the time to do it?
Sent from my SCH-I535 using xda app-developers app
1Android said:
Haven't done the imei backup yet. Need to though asap. I always flash through cwm but once I installed the wrong gapps (didn't even think of grabbing a JB gapps until after I got my phone into recovery and restored) I had no idea how to get into recovery. Once I found the goo manager in system settings I was able to get into recovery. Tried flashing another gapps file (which again was the wrong file) which is where I really freaked out with my framework and setup no working. Was able to clear my head and remember the volume UP not down. I'm restored now and will leave it on synergy till I do my imei backup. Haven't even looked into it to be honest. Is it difficult? Is paranandroid really much better as far as battery life to worry about taking the time to do it?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
The IMEI is very easy to do, especially if your running Synergy. There are 3 methods in the link I'll attach. The first uses any terminal emulator app (free in play store) and simply typing in a code: su (enter) then: reboot nvbackup (enter)...done! Then there is the next way to create a second easier to install if something were to happen way using a Synergy recovery zip. You must do the first method first or the zip way will backup the wrong IMEI. On the link there is another link to the Synergy Key zip file (its right in the directions with HERE in bold as the link). Download zip, run it in recovery ONCE to create the backup, thats it! The synergy backup can then be used on other roms. Overall its super easy, I spent 2hrs researching and 5 min creating the backup. IT really is as simple as that, just do it in order. As far as paranoid goes, I don't have hands on with it, too many bugs for me to bother with it yet, but yes it generally should use less battery due to JB's unmatched efficiency.
Here's the link: (only need to read the first page for making the backups, read further to restore which hopefully won't be needed!)
http://forum.xda-developers.com/showthread.php?t=1852255
I will look into it tomorrow. Thank you so much for your help!! Very much appreciated.
I need/want a fully functional Rom without a bunch of bugs. Might stay with synergy till some bugs can be worked out.
Sent from my SCH-I535 using xda app-developers app
tried to root my Skyrocket, tried to put on latest cm10.1 nightly, got system 7 error, someone said to format. Did so, now it won't go past the samsung screen. Can someone help me fix my newb-ness?
Noobs have no business messing with nightlies.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
xcrazydx said:
Noobs have no business messing with nightlies.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
thanks for stoppin' by
lookslikescreech said:
thanks for stoppin' by
Click to expand...
Click to collapse
Np, enjoy the skyrocket!
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
lookslikescreech said:
tried to root my Skyrocket, tried to put on latest cm10.1 nightly, got system 7 error, someone said to format. Did so, now it won't go past the samsung screen. Can someone help me fix my newb-ness?
Click to expand...
Click to collapse
Start at the beginning. When you rooted your phone what ROM/build were you on? Stock? What Recovery are you running? Did you make a backup? In my experience, you usually get a system 7 error when the download is bad, (did you check the MD5?) or if you're trying to flash a ROM that doesn't match your current system (IE: trying to flash a JB ROM when you're currently on ICS.)
The more info we have, the better we can help you.
Fall of Enosis said:
Start at the beginning. When you rooted your phone what ROM/build were you on? Stock? What Recovery are you running? Did you make a backup? In my experience, you usually get a system 7 error when the download is bad, (did you check the MD5?) or if you're trying to flash a ROM that doesn't match your current system (IE: trying to flash a JB ROM when you're currently on ICS.)
The more info we have, the better we can help you.
Click to expand...
Click to collapse
Uh status 7 is assert protection so its a mismatch usually in device info typically model numbers, and has nothing to do with bad downloads.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Fall of Enosis said:
Start at the beginning. When you rooted your phone what ROM/build were you on? Stock? What Recovery are you running? Did you make a backup? In my experience, you usually get a system 7 error when the download is bad, (did you check the MD5?) or if you're trying to flash a ROM that doesn't match your current system (IE: trying to flash a JB ROM when you're currently on ICS.)
The more info we have, the better we can help you.
Click to expand...
Click to collapse
Thanks for helping
I had a stock rom on it and found a youtube video referencing the how to guide in this forum, walked everything through step by step but didn't do the twrp thing, only odin . Tried it, didn't work. Didn't checkthe MD5 as it wasnt referenced in the video (have since seen it in the thread).
I'm gonna try and flash a stock rom with odin if I can and start over and ignore the youtube video.
At the moment Odin is the only program on my computer that talks to my phone so I'm hoping that works, just gotta find how to do it...
lookslikescreech said:
Thanks for helping
I had a stock rom on it and found a youtube video referencing the how to guide in this forum, walked everything through step by step but didn't do the twrp thing, only odin . Tried it, didn't work. Didn't checkthe MD5 as it wasnt referenced in the video (have since seen it in the thread).
I'm gonna try and flash a stock rom with odin if I can and start over and ignore the youtube video.
At the moment Odin is the only program on my computer that talks to my phone so I'm hoping that works, just gotta find how to do it...
Click to expand...
Click to collapse
Yeah, stay stock until you have a clue on what you're doing.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
lookslikescreech said:
Thanks for helping
I had a stock rom on it and found a youtube video referencing the how to guide in this forum, walked everything through step by step but didn't do the twrp thing, only odin . Tried it, didn't work. Didn't checkthe MD5 as it wasnt referenced in the video (have since seen it in the thread).
I'm gonna try and flash a stock rom with odin if I can and start over and ignore the youtube video.
At the moment Odin is the only program on my computer that talks to my phone so I'm hoping that works, just gotta find how to do it...
Click to expand...
Click to collapse
In this section (q&a), read through "the ultimate newb guide" by vincom.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
btm fdr said:
In this section (q&a), read through "the ultimate newb guide" by vincom.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
thanks, on it now. Just need to get it back to stock with Odin then I'll try again when I understand what I'm doing more.
Anyone feeling charitable and want to tell me how to flash the stock rom with Odin? I'd appreciate it.
lookslikescreech said:
thanks, on it now. Just need to get it back to stock with Odin then I'll try again when I understand what I'm doing more.
Anyone feeling charitable and want to tell me how to flash the stock rom with Odin? I'd appreciate it.
Click to expand...
Click to collapse
It's in the guide bro
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Best of luck mate, reply here if you have any issues. And for pete's sake, next time, instead of watching a YouTube video, read read read and re-read the forums. Once that's done, read them again. Only then, start flashing.
Fall of Enosis said:
Best of luck mate, reply here if you have any issues. And for pete's sake, next time, instead of watching a YouTube video, read read read and re-read the forums. Once that's done, read them again. Only then, start flashing.
Click to expand...
Click to collapse
hahaha thanks
Now it says "firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." Far out, I can't win tonight!
lookslikescreech said:
hahaha thanks
Now it says "firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." Far out, I can't win tonight!
Click to expand...
Click to collapse
Bro, you're going to end up with a paperweight. That guide is step by step. Read it, read it again.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
lookslikescreech said:
hahaha thanks
Now it says "firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." Far out, I can't win tonight!
Click to expand...
Click to collapse
That's an alternate form of DL mode. Odin a stock ROM from that screen. Read the Noobs Guide. Odin is finicky so pay attention to the guide. Then read it again. Once you've read and comprehend it all spin in a circle saying "I deserve this" three times and Odin will grant your wish. lol
hechoen said:
That's an alternate form of DL mode. Odin a stock ROM from that screen. Read the Noobs Guide. Odin is finicky so pay attention to the guide. Then read it again. Once you've read and comprehend it all spin in a circle saying "I deserve this" three times and Odin will grant your wish. lol
Click to expand...
Click to collapse
hahaha thanks
Got it working, used TWRP to flash the latest RC CM 10.1
Got it all going now after a minor heart attack and a few more grey hairs. Just gotta figure out why the wifi isn't working at all now. Can't get it to turn on.
Your original 'system error 7' problem was most likely caused by trying to flash a newer ROM with an older version of CWM or TWRP. Glad you got the phone up, can't help you with the wifi problem, sorry. Although, what modem did you flash, if any? System Settings -> About phone -> Baseband version?
Tom
rpr69 said:
Your original 'system error 7' problem was most likely caused by trying to flash a newer ROM with an older version of CWM or TWRP. Glad you got the phone up, can't help you with the wifi problem, sorry. Although, what modem did you flash, if any? System Settings -> About phone -> Baseband version?
Tom
Click to expand...
Click to collapse
I flashed the UXUMA7 radio, didnt really do much, it worked before.
Still can't figure out the Wifi though :-/ just straight up won't turn on.
If you are on a newer CM 10.1 , the only supported radio is UCMC1, UXUMA7 is really old. That may be why wifi is not working.
UXUMA7 and UCMC1 are very similar. First one is the Rogers and second is att's release which is usually late by a month or so after rogers. Bottom line both will work.
Have your radiofile.zip, cm10.1.zip, and gapps from 20130301 all on your SD card.
Do you have a back up, nandroid? If not do it now.
Go to recovery and Clean up well:
Go to mounts and format data, system, cach twice or three times. Go to advanced and clean dalvik cache. Don't reboot
Now installing in this order:
- radio
-cm10.1
-gapps
Now reboot your phone.
Wait until it is finished and leave it untouched for 10 minutes to settle down and do its thing.
Then turn it off back on and enjoy.
Your noob status will start to fade if you do a clean install :thumbup:
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Is there such thing as a guide like this one but that is up to date and with working links? I want to flash a new ROM onto my phone, but the guides I've found here and elsewhere have broken links, or use language that I don't understand, or skip vital steps. I've been working on this for four hours straight and I haven't gotten a single guide to work, or get stuck, or something else that's really dumb. For someone who has worked on computers for the last 17 years this is extremely frustrating. I'm very new to the android modding scene and apparently it's not just a community, but an entirely different culture and I'm feeling a bit shocked and confused. I have like 30 tabs open with guides, info, different ROMs, different ways to do it, etc and the more I learn the less I understand how to do this :/ I just want to get my phone working with a ROM that's very similar to stock Sense but without the crappy bloatware and memory issues. Miktouch is the one I thought I wanted, but apparently hasn't been updated in almost a year, and bulletproof/doubleshot is confusing. I can't even figure out how to root and get S-Of... Gah!
Please help.
This guide is confusing and skips steps or lacks real explanations.
Thank you.
First thing you want to do is root your phone, this is done by unlocking you bootloader through the HTC dev website. There is a tutorial that is stickyed in the developer section called something like root from any bootloader. I suggest to read that a bit.
Once you followed those steps and unlocked your bootloader you can decide if you want to remove all security flags (highly recommend this, but some find it difficult) in the same guide it explains what radio s-off is and links you to the jbear site to do the wire trick (needs Linux) (or find weekendstoshort for a way to do it in windows)
Feel free to ask more questions but all answers should be found in these xda threads and jbear site, no need to Google anything for this
Sent from my Nexus 4 using xda premium
I hope so...I'll give it another go tomorrow. I'm still quite frustrated at it. I wish I knew someone who had done it and could show me in person.
GiftigDegen said:
I hope so...I'll give it another go tomorrow. I'm still quite frustrated at it. I wish I knew someone who had done it and could show me in person.
Click to expand...
Click to collapse
MikTouch is optimized stock... So updating it farther would take it a direction we wasn't going with it.
Bulletproof is even older. We don't have much here... But what's here is solid
Sent from my Nexus 4 using Tapatalk 4 Beta
First timer here as well (although long time computer user/programming familiar so I might have a better understanding of some things than you) and I was able to fully unlock, S-OFF, and load up a JB rom to my phone using the guide right on this site (http://forum.xda-developers.com/showthread.php?t=1801106) and some help from some online friends that have done this kind of thing before. I found all links to be working, and pretty much all steps to be covered. The I guess hardest part was the permanent S-OFF using the wire trick. I had to burn an Ubuntu live cd and boot a laptop with it, but I was even able to get that step done. A little frustrating with the timing, I think it took me about 8 tries until it finally unlocked. The only thing I think I initially missed was wiping all 3 caches, so I did a dirty flash that got stuck on the boot screen. After I wiped and loaded again, no problems. If you'd like any additional help, I get pretty bored at work, so find me on aim or gchat, or just shoot me a PM here, I think I should get notified
Good luck, it's not as bad as I thought it would be
Also I haven't personally tried it, but feel free to peruse this thread as well: http://forum.xda-developers.com/showthread.php?t=1696373
Note you'll need to have already achieved HTCDev unlocked and be rooted to use this (covered in that first link)
Hope that helps!
PsychoPhreak said:
First timer here as well (although long time computer user/programming familiar so I might have a better understanding of some things than you) and I was able to fully unlock, S-OFF, and load up a JB rom to my phone using the guide right on this site (http://forum.xda-developers.com/showthread.php?t=1801106) and some help from some online friends that have done this kind of thing before. I found all links to be working, and pretty much all steps to be covered. The I guess hardest part was the permanent S-OFF using the wire trick. I had to burn an Ubuntu live cd and boot a laptop with it, but I was even able to get that step done. A little frustrating with the timing, I think it took me about 8 tries until it finally unlocked. The only thing I think I initially missed was wiping all 3 caches, so I did a dirty flash that got stuck on the boot screen. After I wiped and loaded again, no problems. If you'd like any additional help, I get pretty bored at work, so find me on aim or gchat, or just shoot me a PM here, I think I should get notified
Good luck, it's not as bad as I thought it would be
Also I haven't personally tried it, but feel free to peruse this thread as well: http://forum.xda-developers.com/showthread.php?t=1696373
Note you'll need to have already achieved HTCDev unlocked and be rooted to use this (covered in that first link)
Hope that helps!
Click to expand...
Click to collapse
I'm following the first guide you linked. So far it's working I just flashed CWmod on and I loaded it according to the instructions in the guide "After fastboot finishes, disconnect your MT4GS, go into bootloader, and go to “RECOVERY.” You should now be in ClockworkMod Recovery 5.0.2.7. The first thing I would do in CWM Recovery is make a backup of your stock ROM for safe keeping. "
But I forgot to d/c my phone. It still loaded CWmod and I navigated to backup/restore and clicked it. Right now my phone has the clockwork logo in the middle but it didn't give me any prompts after selecting backup/restore. What's it doing? It's been doing this for like 5 minutes. Should I be worried that I forgot to d/c the cable and whatnot?
Thanks
GiftigDegen said:
I'm following the first guide you linked. So far it's working I just flashed CWmod on and I loaded it according to the instructions in the guide "After fastboot finishes, disconnect your MT4GS, go into bootloader, and go to “RECOVERY.” You should now be in ClockworkMod Recovery 5.0.2.7. The first thing I would do in CWM Recovery is make a backup of your stock ROM for safe keeping. "
But I forgot to d/c my phone. It still loaded CWmod and I navigated to backup/restore and clicked it. Right now my phone has the clockwork logo in the middle but it didn't give me any prompts after selecting backup/restore. What's it doing? It's been doing this for like 5 minutes. Should I be worried that I forgot to d/c the cable and whatnot?
Thanks
Click to expand...
Click to collapse
I wouldn't worry, and I'm not entirely sure what it's trying to do, perhaps the possibility of USB storage is throwing it off. At this point I'd say just try to disconnect it, pull the battery, and start back up into recovery, but without the USB attached this time. I imagine then you'll be fine and able to backup the stock image like they say for safe keeping.
One more dummy question (tech support for many years, always check the simple stuff first...) you do have SOME SD card in there right?
PsychoPhreak said:
I wouldn't worry, and I'm not entirely sure what it's trying to do, perhaps the possibility of USB storage is throwing it off. At this point I'd say just try to disconnect it, pull the battery, and start back up into recovery, but without the USB attached this time. I imagine then you'll be fine and able to backup the stock image like they say for safe keeping.
One more dummy question (tech support for many years, always check the simple stuff first...) you do have SOME SD card in there right?
Click to expand...
Click to collapse
Yeah, 32gb =)
booted into recovery, clicked on bacup/restore...still just showing the logo in the middle.
(PS any mods out there listening, I'd love to have that 5 minute restriction removed =D )
Okay, so the select button changes from power to the scroll pad once in recovery...good to know.
GiftigDegen said:
booted into recovery, clicked on bacup/restore...still just showing the logo in the middle.
(PS any mods out there listening, I'd love to have that 5 minute restriction removed =D )
Okay, so the select button changes from power to the scroll pad once in recovery...good to know.
Click to expand...
Click to collapse
NVMD....You got it now.
strapped365 said:
MikTouch is optimized stock... So updating it farther would take it a direction we wasn't going with it.
Bulletproof is even older. We don't have much here... But what's here is solid
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Using CWM to flash Miktouch now. Hopefully it works... =D
Just remember, if you are "S-On" you're going to need to fastboot flash boot boot.img after your ROM is thru flashing or you will hang up at the boot animation.
strapped365 said:
MikTouch is optimized stock... So updating it farther would take it a direction we wasn't going with it.
Bulletproof is even older. We don't have much here... But what's here is solid
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
K. First impressions:
When I restart the phone, the first thing it does is force stop Gmail and Youtube several times. Is this supposed to happen?
Also, I'm extremely impressed with the speed of the restart. It's at LEAST twice as fast as stock.
And, Genius button doesn't work even after installing the patch linked to on your website (universal.zip).
WeekendsR2Short said:
Just remember, if you are "S-On" you're going to need to fastboot flash boot boot.img after your ROM is thru flashing or you will hang up at the boot animation.
Click to expand...
Click to collapse
Thanks Weekends. I did that and it's installed, though I fastboot flash boot boot.img before I used CWM to flash the rom. Does that make a difference? Do you think doing it that way will fix the force close mentioned above?
If there's not a fix for the gmail/youtube force closes, is it possible to do bulletproof with s-on? Thoughts? I really want to stick as close to stock MT4GS but with as solid a system as possible.
Flashing boot image before ROM will overwrite kernel
Wipe all
Flash ROM
Flash boot
Reboot
Sent from my Nexus 4 using xda premium
demkantor said:
Flashing boot image before ROM will overwrite kernel
Wipe all
Flash ROM
Flash boot
Reboot
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Another noob question. How do I wipe all?
Also, when I use CWM to install Mikrom it atuo restarts and loads up. Then do I restart again and go fastboot the new kernal?
Thank you all for how much help you have given me.
At the end of the updater-script there must be a reboot command, but being this ROM is based of stock you may not need to flash the kernel anyway.
Best methods for wiping is one of bluex's superwipe scripts or with fastboot
fastboot erase system -w
But being you are s-on that command may fail.
But always do a wipe data/factory reset, wipe cache, and wipe dalvik in recovery.
It also good practice to make a nandroid of current ROM before you flash anything
Sent from my Nexus 4 using xda premium
demkantor said:
At the end of the updater-script there must be a reboot command, but being this ROM is based of stock you may not need to flash the kernel anyway.
Best methods for wiping is one of bluex's superwipe scripts or with fastboot
fastboot erase system -w
But being you are s-on that command may fail.
But always do a wipe data/factory reset, wipe cache, and wipe dalvik in recovery.
It also good practice to make a nandroid of current ROM before you flash anything
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Mmkay, working doing this now.
Quick question, hopefully someone can give me a link, but I'd love the install the depaginated app drawer, genius fix and menu wake up mods for this, but the links are broken (dev-host times out). Any help?
See weekends mirror thread
Sent from my Nexus 4 using xda premium
So I've been using an HTC MyTouch 4G for the past few years and had the rooting/flashing process down with that phone, but I recently switched to the Verizon variant of the Samasung Galasy S III and have run into an issue trying to root and flash an aftermarket rom to this device.
As per the CM Wiki for my device, I need to install and use Heimdall to downgrade the bootloader. I'm not new to using the terminal, so I figured this wouldn't be a difficult step, however I can't get Heimdall to work even after many attempts to download just the binary from the CM wiki, download the entire package including the frontend directly from the website Heimdall is hosted on, and even after compiling directly from source.
After trying to install it many different times/ways, I'm running into the same error every single time. After opening the terminal and trying to execute any command pertaining to Heimdall (Heimdall help, Heimdall detect, etc.) I get a response of "Illegal Instruction." I cannot get it to do ANYTHING other than to respond with "Illegal Instruction."
It's driving me mad because all I need Heimdall for at this point is to downgrade the bootloader.
I know I must be making some very minute error, but I can't figure it out.
Just a bit more information: I'm running OSX 10.6 so the current Heimdall Frontend is not compatable, so I have to use the Terminal (which I'd rather do anyways because I have more control that way.)
Any help or isight would be appreciated.
Thanks!
Just use the casual script instead of trying to downgrade
Sent from my SCH-I535 using Tapatalk 4 Beta
If I've helped, please hit the thanks button
tylerlawhon said:
Just use the casual script instead of trying to downgrade
Sent from my SCH-I535 using Tapatalk 4 Beta
If I've helped, please hit the thanks button
Click to expand...
Click to collapse
Casual script? Mind elaborating or guiding me in the right direction?
checkthisSH said:
Casual script? Mind elaborating or guiding me in the right direction?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2332825
You shouldn't need to do anything with the bootloader, use this to load a custom recovery, then flash the cm10 image for the Verizon sgs3.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
http://forum.xda-developers.com/showthread.php?t=2332825
You shouldn't need to do anything with the bootloader, use this to load a custom recovery, then flash the cm10 image for the Verizon sgs3.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for getting back to me so quickly.
According to the CM Wiki and a couple of other sources I can't think of at the moment, if I'm coming from stock/no root, I would need to load an older bootloader before flashing recovery and ultimately flashing CM10.
The Samsung root process is a bit different from some of the other phones I have worked with. Would you mind explaining to me why I wouldn't need to load an older bootloader?
Edit: After taking a look into the thread you provided for me I may have answered my own question. Loading the older bootloader is probably essential to getting the exploit to work with Heimdall, right? But not with the Casual exploit?
checkthisSH said:
Thanks for getting back to me so quickly.
According to the CM Wiki and a couple of other sources I can't think of at the moment, if I'm coming from stock/no root, I would need to load an older bootloader before flashing recovery and ultimately flashing CM10.
This process is a bit different from some of the other phones I have worked with. Would you mind explaining to me why I wouldn't need to load an older bootloader?
Click to expand...
Click to collapse
I've never seen those instructions before, but i would try posting this In the cm10 question and answer thread.
That could also be old instructions, find the cm10 development thread and see what the latest instructions are for installation.
I've never used heimdall and couldn't give you instructions how to use it, using odin to flash those would be significantly easier if you can get access to a window computer.
Either way, that process won't achieve root anyway. You're better off running casual first to get a custom recovery and root access, then run that process later if needed.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
I've never seen those instructions before, but i would try posting this In the cm10 question and answer thread.
That could also be old instructions, find the cm10 development thread and see what the latest instructions are for installation.
I've never used heimdall and couldn't give you instructions how to use it, using odin to flash those would be significantly easier if you can get access to a window computer.
Either way, that process won't achieve root anyway. You're better off running casual first to get a custom recovery and root access, then run that process later if needed.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
In theory, and please correct me if I'm wrong, but it looks like I should be able to use Casual up until I need to flash CM10. Which is as simple as throwing the .zip file onto my SD card and installing from recovery. That way I probably won't even have to touch Heimdall.
The only thing that concerns me is that following the CM wiki instructions has you flash an older kernel as well. Again, this appears to me like it could only be required to load the customer recovery using Heimdall, but I'm not entirely sure.
I'll have to look around for the CM10 dev thread around here because the one on the CM forum is a ghost town.
Thanks again for all of your help!
checkthisSH said:
In theory, and please correct me if I'm wrong, but it looks like I should be able to use Casual up until I need to flash CM10. Which is as simple as throwing the .zip file onto my SD card and installing from recovery. That way I probably won't even have to touch Heimdall.
The only thing that concerns me is that following the CM wiki instructions has you flash an older kernel as well. Again, this appears to me like it could only be required to load the customer recovery using Heimdall, but I'm not entirely sure.
I'll have to look around for the CM10 dev thread around here because the one on the CM forum is a ghost town.
Thanks again for all of your help!
Click to expand...
Click to collapse
That's exactly what I'm saying. However, the whole thing is confusing to me also. It seems weird that you'd need an older bootloader in order to run the rom.
Just make a backup before you flash in recovery, then if it won't run at least you have a way to get a working phone.
The kernel should have nothing to do with anything, as soon as you flash cm10 it'll get overwritten with the cm10 stock kernel.
Also make sure that the bootloader is unlocked before you flash, or you'd have to odin back to stock.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
That's exactly what I'm saying. However, the whole thing is confusing to me also. It seems weird that you'd need an older bootloader in order to run the rom.
Just make a backup before you flash in recovery, then if it won't run at least you have a way to get a working phone.
The kernel should have nothing to do with anything, as soon as you flash cm10 it'll get overwritten with the cm10 stock kernel.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I'm assuming it has something to do with using Heimdall, and if that's the case, I don't know why anyone would ever want to use that method when it is clearly more difficult. Maybe someone else can weigh in on the topic.
Thanks again for the solid advice. I'll take the Casual route and see where it takes me.
BadUsername said:
That's exactly what I'm saying. However, the whole thing is confusing to me also. It seems weird that you'd need an older bootloader in order to run the rom.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
FYI, every rooted and unlocked Verizon GSIII is using a pre-release unlocked bootloader so you're using an older bootloader already.
Sent from my SCH-I535 using Tapatalk 4 Beta
SlimSnoopOS said:
FYI, every rooted and unlocked Verizon GSIII is using a pre-release unlocked bootloader so you're using an older bootloader already.
Sent from my SCH-I535 using Tapatalk 4 Beta
Click to expand...
Click to collapse
You mean once you unlock the phone with an old aboot file right? The newer phones would have a newer bootloader until you change it.
The instructions are really confusing because they're instructing to downgrade the bootloader to inject an aboot file and custom recovery. I still think that entire step is unnecessary.
Sent from my SCH-I535 using Tapatalk 2
I've done some searching, finding similar things that have happened to others here, but nothing that specifically fits what I'm experiencing...
I'm hoping someone has a step-by-step that I can do to get this phone rooted properly... First, I've been on XDA for a while, Droid Eris and HTC Incredible 2, but this is the first Samsung phone I've owned... A few days ago, I tried the Casual Root method and went ahead and rooted, unlocked the bootloader (unsecure ABOOT) and loaded CWM touch as my recovery. All looked fine, but when I went in to recovery to try and backup the stock rom, it threw a ton of Not able to write/Cannot Mount errors... My phone came with the MF1 4.1.2 already running.
Since, I've tried EZ-Unlock 1.2 to check and unlock the bootloader (which it showed as "Unknown" until I clicked unlock) and I've tried installing different recoveries through EZ Recovery (TWRP 2.2.2, CWM variants, etc...). Still, no joy in getting this to work properly.
The last attempt kept the phone in Download mode until I rebooted using the Power, Vol. Down, Menu to bypass it (Not detecting ANY recovery now!?). I'm still able to get back to the original Rom (which is rooted now), but I'm concerned with bricking if I keep trying this.
So, I'm thinking now of just doing an Odin back to stock and reflashing all the original firmware so I can start over with Casual. Was wondering if anyone had any other input which might get the R/W issue fixed so I don't have to go through all the Odin stuff? Compared to HTC phones, this is quite different with Root/Flashing, so I'm a little confused with the whole process of things right now... Any help would really be appreciated! I'm looking forward to deving at some point, once I'm comfortable with the process...
Thanks,
Rich
Anyone?
Sent from my SCH-I535 using xda premium
Never mind...
Macrodroid said:
I've done some searching, finding similar things that have happened to others here, but nothing that specifically fits what I'm experiencing...
I'm hoping someone has a step-by-step that I can do to get this phone rooted properly... First, I've been on XDA for a while, Droid Eris and HTC Incredible 2, but this is the first Samsung phone I've owned... A few days ago, I tried the Casual Root method and went ahead and rooted, unlocked the bootloader (unsecure ABOOT) and loaded CWM touch as my recovery. All looked fine, but when I went in to recovery to try and backup the stock rom, it threw a ton of Not able to write/Cannot Mount errors... My phone came with the MF1 4.1.2 already running.
Since, I've tried EZ-Unlock 1.2 to check and unlock the bootloader (which it showed as "Unknown" until I clicked unlock) and I've tried installing different recoveries through EZ Recovery (TWRP 2.2.2, CWM variants, etc...). Still, no joy in getting this to work properly.
The last attempt kept the phone in Download mode until I rebooted using the Power, Vol. Down, Menu to bypass it (Not detecting ANY recovery now!?). I'm still able to get back to the original Rom (which is rooted now), but I'm concerned with bricking if I keep trying this.
So, I'm thinking now of just doing an Odin back to stock and reflashing all the original firmware so I can start over with Casual. Was wondering if anyone had any other input which might get the R/W issue fixed so I don't have to go through all the Odin stuff? Compared to HTC phones, this is quite different with Root/Flashing, so I'm a little confused with the whole process of things right now... Any help would really be appreciated! I'm looking forward to deving at some point, once I'm comfortable with the process...
Thanks,
Rich
Click to expand...
Click to collapse
If you were able to root your phone successfully, then what I would recommend what to do is download whatever image you want (for me, I downloaded twrp 2.6.3.0) and then flash it through flashify (free in play store).
If you want to get it an easier way, then use goomanager and then install open recovery script (you'll see it when you press menu). It should install the recovery automatically.
If you want clockworkmod touch, then if you want an image, use flashify to flash it. Doing either of the options will give you a working recovery.
david_hume said:
If you were able to root your phone successfully, then what I would recommend what to do is download whatever image you want (for me, I downloaded twrp 2.6.3.0) and then flash it through flashify (free in play store).
If you want to get it an easier way, then use goomanager and then install open recovery script (you'll see it when you press menu). It should install the recovery automatically.
If you want clockworkmod touch, then if you want an image, use flashify to flash it. Doing either of the options will give you a working recovery.
Click to expand...
Click to collapse
Ok, I've gotvtwrp 2.6.3.0 loaded, works... But, I cannot mount anything, backup totally fails. Any ideas? Twrp also asks for a password for some reason...
Btw, nice to see a familiar face on here! How's life treating you these days?
Sent from my SCH-I535 using xda premium
Try this. But download and use the correct and updated cwm recovery from somewhere else.
http://bestandroidtricks.com/how-to...covery-on-the-samsung-galaxy-s3-all-versions/
Sent from my SCH-I535 using xda app-developers app
stolo said:
Try this. But download and use the correct and updated cwm recovery from somewhere else.
http://bestandroidtricks.com/how-to...covery-on-the-samsung-galaxy-s3-all-versions/
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thanks! After going through Rom Manager and letting it update CWR on it's own, I finally got everything working now! Backup of the Stock Rom is done finally and I can start flashing some Rom's to get comfortable with things... Hopefully, I can start putting out some Rom's for this device soon!! Thanks for all the help, I really appreciate it!
I have been using kitkang cm11, so far really excited and loving 4.4. I have been updating daily.
Sent from my SCH-I535 using xda app-developers app
stolo said:
I have been using kitkang cm11, so far really excited and loving 4.4. I have been updating daily.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Got wicked loaded up! So far, so good. I might try pulling a repo on cm11 sometime soon...
Sent from my SCH-I535 using xda premium