Related
I would love some help, can someone tell me how to install a rom using Rom Manager. I've install clockwork recovery downloaded CM7.2 for my ascend. Can I install this, using Rom Manager? I have premium, but I have ruined 2 zio m6000 , 1 samsung moment, and 1 ascend. Up really dont want to loS another phone. Could I get a hand, here? I havE nO clue whaT half the things talked about on here are. But, its starting to cosT to much $ learning.
Sent from my M860 using XDA Premium App
As we are speaking about ROMs, any wrong operation can turn your phone in a simple book holder. I am not expert (bought my first HTC 3d ago), but already have good experience to help you A BIT.
- enter ClockWork (reboot your phone, press volume-down as it starts, navigate and enter RECOVERY mode: clock-work is installed in the recovery zone; some ROMs may have a reboot-to-recovery feature)
- navigate and wipe system, user-data, and cache zones
- navigate in menus a either perform a restaure, or apply-patch-from-zip depending on your type of ROM (IMG, zip ... )
You can also try to install your ROM without wipe, BUT, if you see CW does NOT says it will erase or format the partition first, then you are going to have troubles (small troubles: it will boot, but not work properly). You can start by this operation, and when you have found how to flash, then you wipe ... this will avoid having an empty system, and have your phone unusable for a time.
If you have a broken system, you can always put the SD card into computer and push a working rom using SD (then CW) or fastboot.
After successfull flash, you may want to wipe user and cache zones. Again, it just helps having a clean system, and is not mandatory; keeping old user-data usually works, but CAN make bugs trigger.
At your own risks. Good luck.
- how to flash my Samsung Galaxy S Fascinate CDMA. using Rom Manager. with file name .ota .? huhuh. sorry, i'm noob in this kind of thing.!! i;m begging you guys.!! help me , i'm stock to Eclair 2.1 and i hate it,! thanks.!!
-help me guys.!!! thanks.
kakroch99 said:
-help me guys.!!! thanks.
Click to expand...
Click to collapse
Learn to help yourself. You are not asking a new question.
1. Use the search function.
2. Use Google.
3. Research!
4. Read, read, read!
5. Don't actually try any modifications until you're confident you know what you're doing and willing to accept the consequences if you screw up.
6. If you fail, do more research and reading so you can...
7. Try to fix it yourself before asking for help.
8. Ask intelligent questions if you do still need help.
Sent from a HTC G2
**this was a very early guide and most of the files and methods referenced in it are long outdated, sounds crazy I know as the phone has barely been out, but i recommend finding more recent guides at this point. I wanted to leave this up for archival reasons though. As of 7-22 I am running dhackers CM10 build with great results. Just don't forget to set max cpu clock back down to 1500 mhz if you don't want it over locked out of the box **
As per the usual disclaimer....at your own risk, be aware of IMEI loss issues and whatnot...basically cover your own butt.....and enjoy.....
7-15 2:46pm **As of right now voice and SMS are not working on my phone while other people report they are working fine. While you can still play around and see just how amazingly fast CM is on this phone, YMMV. If it doesn't work you need to know how to go back to stock before trying this.
7-29 this guide is very old, it pre-dates kexec and is only here for historical purposes
For clarification: The question was asked if one is supposed to follow the original Team Epic Kexec kernel instructions or these steps and the answer is two fold. If your goal is to install the UNOFFICIAL CM9 built by Invisiblek (which is the purpose of this thread), then you follow the steps in THIS THREAD ONLY. There are a couple steps and a couple files linked to in the original Kexec page that will not allow you to install CM9. That page was made for those wanting to try out their Kexec Proof of Concept KERNEL, not install a ROM of any kind.
This thread makes some assumptions, such as you already have a working install of the Android SDK and ADB, you already have the drivers installed, you are using the original USB cable that came with your phone, you know how to move around DOS to get to the directory where you downloaded the files, etc.......those lower level tasks are for another thread.
To Try Our Proof-of-Concept Kernel <<<The base of these instructions was the Team Epic Kexec Kernel page seen at this link, Many Thanks to them
Thanks to Invisiblek for clarifying and helping me get steps just right.
The following is an adaptation of the CM Kexec kernel proof of concept with the changes in files and steps necessary to load the latest CM9 work in progress. Be advised I take no credit at all. This is the work of Team Epic and Invisiblek. I just put this together for myself and for others who would like to try it with one caveat. DATA doesn't work! Voice and SMS only....and maybe 1xRtt data.....so you will be relying on WiFi for data! You've been warned!
Also, I highly suggest you use a free MD5 Hash checking utility to verify the integrity of the files you are downloading. That is why the MD5 hash is provided, so you can be sure you didn't get the wrong file or a corrupt download that could cause a BRICK!
If you don't follow the directions carefully you can end up with a brick! Ask questions after reading the OP if you still aren't sure. I probably won't know the right answer for sure. You may have to wait on someone with more experience in this to answer your question.
DO NOT ACCEPT AN OTA UPDATE WHILE RUNNING THIS SETUP
1. Download the recovery.img (MD5: f1c01ad20e02751a73188f173eb412ca), which combines our source-based kernel with our previously released CWM v4.
2. Flash the recovery.img following these instructions, that is:
Code:
adb push recovery.img /sdcard/
adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 bs=256k
sync
3. Reboot into recovery (using volume up, home power buttons), wipe data, install one of invisibleks CM9 roms>click here for all of his CM9 roms< which do not have boot.img integrated, then continue with the steps below:
4. Download these additional files:
(required download)boot.img (MD5: db058f4b15df0fa1b9ee04a5c17cf103), which is invisibleks custom boot.img
It would be good at this point to read ahead and determine where you will be loading the next file. Keep in mind if you are in stock recovery and choose to wipe data, this will wipe the internal memory.
if you plan to load onto internal memory download this file boot_emmc_boot_img.zip (MD5: 84a3f98c194f6dedc583dbc75ccc34c2)
or
if you plan to load onto sdcard (ext) memory download this file boot_sdcard_boot_img.zip (MD5: 88904d7e69d455ff88756b4d1ad79aac), which are applied in recovery to kexec (boot) the custom boot.img.
5. Place boot.img either on the internal SD card (the /sdcard/ folder), or on the external SD card (the /mnt/extSdCard/ folder).
The boot.img kernel boots directly out of one of these folders, it will not (and should not) be flashed to the device.
6. If you're using the internal SD card, place boot_emmc_boot_img.zip in /sdcard/ as well. If you're using the external SD card, place boot_sdcard_boot_img.zip in /mnt/extSdCard/.
7. Reboot into recovery.
8. If using the internal SD card, select "Install zip from sd card" and then "choose zip from internal sdcard", then "boot_emmc_boot_img.zip". Alternatively, if using the external SD card, select "choose zip from sdcard", then "boot_sdcard_boot_img.zip".
At this point, the device should reboot "in the middle" of applying the update, temporarily booting boot.img. If the update "completes" and returns to the CWM menu, kexec has failed or the wrong recovery was loaded in the beginning. Please check the locations of boot.img, and boot_emmc_boot_img.zip or boot_sdcard_boot_img.zip and verify recovery.img file used was the correct one, verify using an MD5 hash checker.
9. Once booted, the custom kernel can be confirmed by checking "Kernel version" in "Settings", "About device". It should report:
3.0.8-gdefeb6f
[email protected] #1
SMP PREEMPT Sun Jul 8 04:27:58 EDT
2012
10. To reboot into the stock kernel, select "Restart" from the Power menu, which will actually reboot into CWM recovery. Press the Power button to select "reboot system now" and leave recovery.
11. You cannot simply power on your phone with this setup! In order to power on your phone you will have to hold volume up, home and power to boot into recovery and load the zip file you chose at step 4 where you chose either internal or external memory, so either "boot_emmc_boot_img.zip" or "boot_sdcard_boot_img.zip". If you do accidentally boot up by just hitting power, no big deal, it will give you all sorts of force closes, simply pull battery and boot back up using the Vol up, Home, power method.
If anyone would like to suggest further clarification, please do. To get the stock Google apps such as Play Store get the package HERE and install in recovery
Alternatively a more condensed version of this install procedure has been posted by nbsdx and can be found HERE.
7-15 2:46pm **As of right now voice and SMS are not working on my phone while others are working fine. While you can still play around and see just how amazingly fast CM is on this phone, YMMV. If it doesn't work you need to know how to go back to stock before trying this.
If you want to return to bone stock, simply go to THIS THREAD to get STOCK ROM IMAGE and then put your phone into Odin Download mode by following THIS THREAD and be sure to flash it using the PDA button. It will take a while, probably 20 minutes or so, it will take forever to boot up the first time but you will be on bone stock like new.
Very informative. Would read again.
Sent from my Transformer Prime TF201
dual boot
Being that we have to use kexec anyhow, it would be nice (especially with the state of current cm9 rom) if we could fully dual boot so as to keep stock system and data for stock kernel.
Like here,
http://www.epiccm.org/2012/07/dualboot-cm9-on-sgs3-lte-sprint-t.html
I just installed successfully using the instructions in the OP so I can confirm it works correctly. Holy crap it's fast.
Anybody want to put up a video of how well it runs for us that aren't brave enough to put it on our own phones?
Sent from my SCH-I535 using xda premium
dakalter said:
Anybody want to put up a video of how well it runs for us that aren't brave enough to put it on our own phones?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I'll leave that part to someone who doesn't sound like a retarded redneck on video.
silasrye said:
I tried to install the vzw cm9 (with with invisiblek's boot.img put back into the zip) via this method exactly.
http://www.epiccm.org/2012/07/dualboot-cm9-on-sgs3-lte-sprint-t.html
fake cwr works, and everything went fine, but when i try to flash boot_cm9.zip i stay in cwr.
I am using the cwr from this post
http://forum.xda-developers.com/showthread.php?t=1773514
I had started with the twrp from that post, but it didn't recognize my internal sdcard.
So, I don't see why this shouldn't be a doable thing. But something probably needs to be redirected somewhere.
The good news is, I boot into my normal rom without problem.
Click to expand...
Click to collapse
If you follow the steps in this thread, including using these links for your files, it will work without a problem.
I can't comment on why other guides on other sites using other files don't work.....and not really sure how it applies to this thread. Lets try to keep it on topic. If you have issues with the dual booting instructions, you might start a new thread to address that or jump in irc.freednode.net/verizons3 and graciously ask the people for help
When you flash the the CM9 rom built by Invisiblek it will come back out to CWR menu. At that point in the process I realized I hadn't copied the boot.img file into the root of my sd card, so i left it on the CWR menu, popped out the sdcard, copied the boot.img file over (already had the boot_sdcard_boot.img file on the root of sdcard), and popped the sdcard back in, chose advanced->reboot recovery, then followed the steps in this guide, worked perfectly.
silasrye said:
I tried to install the vzw cm9 (with with invisiblek's boot.img put back into the zip) via this method exactly.
http://www.epiccm.org/2012/07/dualboot-cm9-on-sgs3-lte-sprint-t.html
fake cwr works, and everything went fine, but when i try to flash boot_cm9.zip i stay in cwr.
I am using the cwr from this post
http://forum.xda-developers.com/showthread.php?t=1773514
I had started with the twrp from that post, but it didn't recognize my internal sdcard.
So, I don't see why this shouldn't be a doable thing. But something probably needs to be redirected somewhere.
The good news is, I boot into my normal rom without problem.
Click to expand...
Click to collapse
You need to add one line to Invisiblek's updater-script that "flashes" the boot.img to the bootloader partition in the multi boot folder. Check out the sprint cm9 install for the line to add.
I have tested dual booting to work perfectly.
is the data not working due to the ril??
suzook said:
is the data not working due to the ril??
Click to expand...
Click to collapse
yes, will update OP once we have working 3G/4G data
as of right now my voice and SMS isn't working while others is.....trying to figure it out
I flashed back to stock, simply because I need to have voice and SMS working. I could deal without 3G/4G data for a little bit and use WiFi, but no SMS/Voice was a deal breaker on my phone. I have to be easily gotten in touch with for work and such. It was fun while it lasted.
Will these same instructions work for the CM10 build that is in the server list?
17akota said:
Will these same instructions work for the CM10 build that is in the server list?
Click to expand...
Click to collapse
No. Different files used, probably a different step or two also. I plan to edit this once CM10 builds are ready for public consumption. These instructions also don't include the automated kexec scripting work done recently that allows your device to cold boot into CM9.
Sent from my SCH-I535 using xda premium
neyenlives said:
No. Different files used, probably a different step or two also. I plan to edit this once CM10 builds are ready for public consumption. These instructions also don't include the automated kexec scripting work done recently that allows your device to cold boot into CM9.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I figured that.
Could you point me in the direction of the new Kexec? I read about it somewhere and would like to try it out.
17akota said:
I figured that.
Could you point me in the direction of the new Kexec? I read about it somewhere and would like to try it out.
Click to expand...
Click to collapse
irc.freenode.net #verizons3
Sent from my SCH-I535 using xda premium
i came from a thunderbolt, and know how different a RIL can be from phone to phone, so i ask this quite seriously...
How different is the RIL from the Gnex to the SGIII?
seang said:
i came from a thunderbolt, and know how different a RIL can be from phone to phone, so i ask this quite seriously...
How different is the RIL from the Gnex to the SGIII?
Click to expand...
Click to collapse
Completely different processors.
Is there anyway to get the TouchWiz Camera on CM9? I really like that camera app.
I tried just putting it in /system/app and changing the permissions to rw-r--r-- and rebooting and nothing
Then i tried just installing it like a normal apk and it failed.
I would love CM9 if i could just get the stock camera app too work.
BTW im using DHacker29's CM9 and its amazing. So much easier to install.
17akota said:
Is there anyway to get the TouchWiz Camera on CM9? I really like that camera app.
I tried just putting it in /system/app and changing the permissions to rw-r--r-- and rebooting and nothing
Then i tried just installing it like a normal apk and it failed.
I would love CM9 if i could just get the stock camera app too work.
BTW im using DHacker29's CM9 and its amazing. So much easier to install.
Click to expand...
Click to collapse
It probably requires touchwiz frame work. It will take significantly more work than just dropping in an apk
Sent from my SCH-I535 using xda premium
DHacker's CM10 is awesome!! I've been running it all day and Jelly Bean is really smooth on the S3.
http://www.droidhive.com/forums/index.php?/files/category/26-sgs3/
Check it out guys.
Any advantage over one from the other
Sent from my GT-N8013 using xda app-developers app
I Rio Wonder about that
Sent from my GT-I9100 using xda premium
this will be interesting hearing everyone's imput ... tho its all based on personal preferenceim sure .. i like cwr
I have used both in the past and still prefer CWM....no reason other than its what I learned to use when i was a noob....now Im a noob veteran.
droidstyle said:
I have used both in the past and still prefer CWM....no reason other than its what I learned to use when i was a noob....now Im a noob veteran.
Click to expand...
Click to collapse
I will second this, I like them both, in fact I still use TWRP on my Nook Tablet, but I've been using Koush's stuff for so long, over 3 or 4 phones now, that it just seems natural for me to use CWM.
TWRP for me. Its much faster and has nice features.
I use to be a CWM fan, that was until I started using TWRP on my Rezound. From then on I use TWRP, but I don't mind good ole CWM every once in a while.
TWRP because it's faster and the UI is easier to use simply because the tiles are large.
I like Amon Ra best of all. Oopps...wrong thread LOL!. I use TWRP on my Bionic and CWM on the Galaxy. Like mentioned above, CWM is what I learned on and for some reason it feels like more hands on.
Let me say this. My friend was running CM10 all the way from like september. I tried updating it in CWM but it gave me assert errors. Reflash TWRP on it, and flash latest nightlies no problem. Dirty flash too, just wipe dalvik and cache.
There isn't an objective answer that I can give. I'm biased towards pretty much anything that is alternative to what everyone else is using. Also, I have no data that would indicate one recovery is better than another. So here's my purely subjective answer.
I prefer TWRP over CWMR for several subjective reasons:
Coming from the original Moto Droid on vzw, I ran RZrecovery (a moded version of SPrecovery, which had an OC'd kernel and lots of options as well as charging while in recovery way before I had seen it anywhere else). Basically, I'm not accustomed to CWMR.
I'm not a fan of the differential backups that CWMR defaults to. I know it takes up more space to have an IMG or TAR for each partition I choose, but I'm a crack flasher and go back and forth between TouchWiz and AOSP based roms all the time. I need to be able to keep my backups completely seperate. No blobs. I need a golden master for each ROM I flash. With a 64GB externeal SD card and a 32GB internal card, I rarely run out of space.
I can name backups while booted into TWRP before you create the backup. The whole date being wrong in every recovery thing is indeed annoying.
I like the terminal. I prefer to root, flash, hack, etc etc on my own without help from apps and or pre-built tools (except for dsixda's android kitchen, which is so bloody easy to use it blow my friggin mind). So I don't need or want ROM Manager to do much of anything for me. I even flash TWRP via the terminal. GooManager always runs in the background, and hasn't really ever had the most up to date versions of TWRP, so I ditched it pretty fast. I hate apps that run in the background when I'm not using them.
I like the look and feel of TWRP. Its feels like a teeny version of android with a small but very functional UI. Only thing missing is a terminal emulator that I could use from within TWRP itself. (Choosing a command file to run just isn't the same, but it has come in handy)
I also like having backups go to a folder that is labeled with the device's SN. Seems like a really fantastical feature in the making, like a cloud based storage for TWRP could be somewhere off in the future, where you could backup multiple devices to one online storage space.
Its the only "alternative" in town. I like "alternative" aka not so main stream stuff, which is odd cause I'm not a fan of Alt Rock. More of a Hendrix, Zepplin "classic rock" (aka blues based rock n roll with lots of riffs on the minor pentatonic scale) kind of person.
Um, I don't really have an 8th reason. But I would like an OC'd kernel in TWRP to help speed up backups, but I dunno how viable that is.
Ta,
ALQI
alquimista said:
Um, I don't really have an 8th reason. But I would like an OC'd kernel in TWRP to help speed up backups, but I dunno how viable that is.
Click to expand...
Click to collapse
Tempting, but with backups/flashing/recovery, I think slow and steady wins the race.
I used to use cwm, but with the change to blobs all of my backups stopped working. Even ones I just made.
so I stopped trusting it.
I switched to twrp. The backups are larger I think, but I trust them more.
Sent from my SCH-I535 using xda app-developers app
Haven't had any problems with TWRP, and it was the first I used. So pretty much just became acquainted with it and haven't seen a reason to switch.
I use CRW on my phone and TWP on the Kindle Fire. The best advice I can give is use what ever method the dev tells you to use, if he goes out of his way to mention it there is probably a good reason behind it.
One thing about CRW I wish would get fixed is the file name date being wrong (When it saves a file it gives the file a name based on the date but all current versions save it with an incorrect date (it thinks its 1970 lol) If i dont change it right away I end up with a bunch of mystery backups.
Another thing to remember about the latest CRW's is the blob. To save space during the saving of a backup a file (blob) is created that has any redundant info shared by backups in it. So all the info for your latest backup file isn't all in the file with that backups name some or most of it is in the blob file. So if you want two or three backups from your phone saved to your home computer make sure you take the entire clockworkmod file because if you take just the individual CRW backup file (1970 -blah-blah-blah) you will be missing all the info on the blob. CRW will let you restore with the partial file and that can get ugly fast.
I've always used cwr but I will give twrp a shot, love trying new stuff. And the date issue with cwr is really annoying. I'm sure it could be renamed but I don't want to change anything and get an md5 mismatch.
Sent from my SCH-I535 using xda app-developers app
Well, It seems we are having a rash of new users obtaining used and refurbed G2x(s). A lot of these guys are jumping into rooting and flashing and as the XDA G2x community shrinks, the remaining "senior G2x members" are trying to help as much as possible. I have decided to write up this tips and install help guide so the new users have updated information. You may ask how I may be qualified to write this guide? I can say I've been on XDA shorter than the time I've owned and modded this phone. I think I've had this phone 15 months now. These are the procedures I follow to a T every time and always produce a solid and stable setup. I have flashed everything for this phone, literally, and find CM7 is the only stable choice for custom ROMs.
POST 1: INSTALLING CM7 via ClockWorkMod
POST 2: <reserved>(CM7 Setup Tips)
POST 3: <reserved>
I am writing this guide assuming a few things:
1. You are already running ClockWorkMod Recovery that was installed properly via NVFlash, NOT ROM MANAGER. If you used ROM Manager to install CWM, STOP, and follow this guide to properly flash CWM using NVFlash.
[RECOVERY][APP] 4-28 One-Click NvFlasher ClockWorkMod Touch 5.8.1.3/5.0.2.0/4.0.1.5
2. You want stability and have decided to flash CM7. This guide will always support the night-lies, although I am sure the stable CM7 release can be used in place, I have ran into troubleshooting issues that were resolved by moving them over to the updated source... night-lies! (or monthlies now? lol)
3. You will be flashing a custom kernel, meaning you will not be using the stock CM7 kernel, which sucks anyways. I will only offer support in this thread for users who have flashed Faux 054 or ANY Mazout360 (v0130 and up, OC variants only) kernel.
4. You are on the March 11, 2012 BASEBAND (LG Stock Android 2.3.4)
5. You have basic knowledge of file extensions (.zip,.apk,etc.), and have basic knowledge of how to manipulate and navigate files and file directories.
6. That you have an External MicroSD card and a MicroSD card reader for your PC.
7. That you have backed up any personal data from the phone as you will LOSE EVERYTHING on the phone.
8. Phone is fully charged and/or plugged in.
9. You are fully aware that using any ROM other than LG Stock 2.3.4, or a rooted LG stock 2.3.4 variant on the March 11, 2012 baseband WILL BREAK BLUETOOTH CALL AUDIO, MEDIA AUDIO (music, games, movies etc) WORKS 100%
That said, now for the fun stuff.
You will need the following files:
The latest CM7 release for our P999 from Cyanogenmod The latest release as of this guide: 3-1-2013
Gapps Pack (Required for Playstore etc..)
Kernel (if not using CM7 stock kernel, find in link in my signature or over in the development section.
The Fix for the March 11 2012 baseband, newbaseband.zip
So now you should have 4 files, ROM, kernel, Gapps, and newbaseband. And they should all be in .zip format. You will need to place these on the ROOT DIRECTORY of your MicroSD card.
And now we flash your new setup!
1. With your phone off, boot into CWM (I use CWM 5.0.2.0) by pressing and holding the Power & Vol - buttons until you see the second LG logo with the blue streak and release. Welcome to CWM.
2. You need to wipe the phones previous data. To do this use the Vol +/- keys to scroll up and down, and tap the power key to select options and than select:
-wipe data/factory reset
-wipe cache partition
-select advanced-->wipe dalvik cache
-GO BACK to CWM Main Menu
-select mounts and storage
-format /system
-GO BACK to CWM Main Menu
That's it for wiping.
3. Let's flash this so we can play with our new shiny toy.
-select install zip from sdcard
-choose zip from sdcard
-scroll and select your ROM from the file list
Now you will repeat this process and flash
-Custom Kernel
-newbaseband.zip
-Gapps Package
That's it! Go back to CWM Main if not already there and "reboot system now".
-First boot can take up to 10mins depending on kernel used.
-After the phone boots, LET IT SIT FOR 10MINS, DO NOT USE IT.
-Reboot
-Wait 5 mins and than proceed with inital phone setup.
-Reboot and wait 5 mins and than proceed with using the phone as you see fit.
I will be adding in some CM7 and kernel related setup tips tomorrow in post #2, as well as re-formatting post #1. It's 4:33am as of this writing, I need to go sleep!
rrserved
Sent from my LG-P999 using xda premium
reserved in case
Sent from my LG-P999 using xda premium
Your an animal dude. And you rock. Our community rocks!
Also, on a side note. Its should be said that you can use your soft keys in CWM 5.0.2.0, to navigate and select your options. Menu and home are up and down, and the search button selects.idk abt you guys but I got sick of button mashing all the time...anywho happy flashing!
sent from my"blessed"g2x
twrp
rg2x miui
mazout360 v.323
grantusmantus said:
Your an animal dude. And you rock. Our community rocks!
Also, on a side note. Its should be said that you can use your soft keys in CWM 5.0.2.0, to navigate and select your options. Menu and home are up and down, and the search button selects.idk abt you guys but I got sick of button mashing all the time...anywho happy flashing!
sent from my"blessed"g2x
twrp
rg2x miui
mazout360 v.323
Click to expand...
Click to collapse
Ill add that info tonight. I've just always used the hard keys to be safe.
Sent from my LG-P999 using xda premium
Excited to read up on the tweaking guide later
Sent from my LG-P999 using xda app-developers app
Pain-N-Panic said:
Excited to read up on the tweaking guide later
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
hopefully tonight. but today is already lookin like its gonna be as bad as yesterday. bleh...
Sent from my LG-P999 using xda premium
Sorry to hear man either way looking forward to it. Primarily under clocking as I'm too scared to over clock my device lol
Sent from my LG-P999 using xda app-developers app
Hey Guys,
I know there are several posts out there that exist which ponder upon how exactly to root the Samsung Galaxy S Blaze 4G, but majority of the threads reference to Gingerbread, and not the ICS. I previously owned a MyTouch 4G, and had rooted it, and had upgraded to this phone few months ago, as it was on a nice sale, and I would like to install CM10 on it once again. I am not familiar with the instructions as to rooting this device either, as I am completely lost.
Can someone please provide me a step by step instruction for rooting this phone so I can install ROMs? I would really appreciate it, and would love to contribute back by creating my own (updated) how-to for rooting this device.
As for specifics, this device is running Android Version 4.0.4.
Thanks!
This is the guide you need for ics:
http://forum.xda-developers.com/showthread.php?t=1919228
Let me know if you have questions. First and foremost, get rid of kies on your computer, kill it with fire. Then plug in that Blaze so drivers download. Then start the guide.
Sent from my GT-P5110 using XDA Premium 4 mobile app
njstein said:
This is the guide you need for ics:
http://forum.xda-developers.com/showthread.php?t=1919228
Let me know if you have questions. First and foremost, get rid of kies on your computer, kill it with fire. Then plug in that Blaze so drivers download. Then start the guide.
Sent from my GT-P5110 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the reply!
I got all the way upto Step 3, where Odin had given me the green box. When I reach to Step 4, it mentions to go on the ADB command, what exactly am I supposed to do? Can you happen to make that entire step more noob-friendly?
Additionally, how would I flash the SuperUser zip file? I am assuming I would run this through ClockWorkMod?
Sorry for all these silly questions!
darkgiant said:
Thanks for the reply!
I got all the way upto Step 3, where Odin had given me the green box. When I reach to Step 4, it mentions to go on the ADB command, what exactly am I supposed to do? Can you happen to make that entire step more noob-friendly?
Additionally, how would I flash the SuperUser zip file? I am assuming I would run this through ClockWorkMod?
Sorry for all these silly questions!
Click to expand...
Click to collapse
No, don't worry about adb, use the other method to get into recovery. Holding the volume and power buttons. Hold all three (volume up/down, power) slow count to ten, let go of the power button (keep holding the volumes) and keep holding until you get into recovery! Then once there, go to install zip, select superuser zip, flash! Rooted bro.
Some words for you. I think you'll be able to find cm10 "stable", it's not the one you want. Look through the last few pages of the cm10 thread to find the best one. Last I checked @thomas.raines 4.1.2 (cm10) version of ParanoidAndroid is available to flash, it's super stable, and super awesome. If you go above 4.1.2, there are small bugs (do a bit of reading in the op's of those ROMs), a side effect of a great piece of hardware being left behind by Samsung. If you want to go above 4.1.2, you'll need to update your recovery. Read through the development forum, that thread is in there. Any questions, feel free to ask! Happy to have another active member!
Sent from my GT-P5110 using XDA Premium 4 mobile app
njstein said:
No, don't worry about adb, use the other method to get into recovery. Holding the volume and power buttons. Hold all three (volume up/down, power) slow count to ten, let go of the power button (keep holding the volumes) and keep holding until you get into recovery! Then once there, go to install zip, select superuser zip, flash! Rooted bro.
Some words for you. I think you'll be able to find cm10 "stable", it's not the one you want. Look through the last few pages of the cm10 thread to find the best one. Last I checked @thomas.raines 4.1.2 (cm10) version of ParanoidAndroid is available to flash, it's super stable, and super awesome. If you go above 4.1.2, there are small bugs (do a bit of reading in the op's of those ROMs), a side effect of a great piece of hardware being left behind by Samsung. If you want to go above 4.1.2, you'll need to update your recovery. Read through the development forum, that thread is in there. Any questions, feel free to ask! Happy to have another active member!
Sent from my GT-P5110 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You mentioned about CM10 by a different dev. Is the CM10 ROM offered throuh CM's site itself (http://download.cyanogenmod.org/?device=t769) good enough? I was intending to download the most stable ROM offered.
Thanks for the great support!
darkgiant said:
You mentioned about CM10 by a different dev. Is the CM10 ROM offered throuh CM's site itself (http://download.cyanogenmod.org/?device=t769) good enough? I was intending to download the most stable ROM offered.
Thanks for the great support!
Click to expand...
Click to collapse
The ParanoidAndroid build is my personal opinion. The "stable" CM10 isn't that stable (I only know this by reading through the development thread for that rom). If you're dead-set on using Cyanogen the stable build isn't great (again from what I read) and there's a much better build somewhere in the development thread. The ParanoidAndroid I mentioned is CM based (very similar) and, imo, a better rom. But it's your choice, don't let me sway you. Try them both and see which one you prefer, really. But I do know the stable one posted isn't the one you want. And FYI, CM10 = 4.1.2.
Sent from my SAMSUNG-SGH-T769 using XDA Premium 4 mobile app
njstein said:
The ParanoidAndroid build is my personal opinion. The "stable" CM10 isn't that stable (I only know this by reading through the development thread for that rom). If you're dead-set on using Cyanogen the stable build isn't great (again from what I read) and there's a much better build somewhere in the development thread. The ParanoidAndroid I mentioned is CM based (very similar) and, imo, a better rom. But it's your choice, don't let me sway you. Try them both and see which one you prefer, really. But I do know the stable one posted isn't the one you want. And FYI, CM10 = 4.1.2.
Sent from my SAMSUNG-SGH-T769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Haha, should of taken your word on that earlier. I installed the ROM, re-backed up everything, till I find out the Camera has that "No External Storage Message"... I will have to check out that ParanoidAndroid ROM. Thanks for the help, look's like I am on my way to rocking a rooted Android once again!
Quick question, I couldn't find a link to the official CM10 based ROM you had mentioned, can you possibly provide the link?
If best, what is the most stable ROM available for this device? I would prefer to avoid experimenting as I am in school and don't have enough time to do so
darkgiant said:
Quick question, I couldn't find a link to the official CM10 based ROM you had mentioned, can you possibly provide the link?
If best, what is the most stable ROM available for this device? I would prefer to avoid experimenting as I am in school and don't have enough time to do so
Click to expand...
Click to collapse
I'm sorry man, I just realized that the version available for PA isn't what I said. That's my bad. I'll chat with @thomas.raines and see if he can provide a link or something. I'll get back to you on that one.
As far as other stable ROMs, this is AOKP, it was the first rom I Flashed after I rooted, so it has a special place in my heart. I checked the rom link, it's good:
http://forum.xda-developers.com/showthread.php?t=1989825
I haven't ran it in a long while, but I remember it being stable and fast.
This is Liquidsmooth, another I ran that was also stable. I don't remember much about it but I saw that I had it in my signature for a little bit. I won't stay with a rom if it's not stable, so since it was in a sig, it must have been good:
http://forum.xda-developers.com/showthread.php?t=2284763
Try these two and see what you think. If you don't like em, I'll figure something out with thomas and see if I can't get PA back up.
This is a VERY slim gapps package. I'm running it right now on my phone and my Tab. When I say slim, I mean it has Play store and all syncing abilities. That's it. No Search, Gmail, Hangouts, etc. If you want something with all the Google goodies, look around. I'm not one to run gapps with a bunch of Google stuff so I don't know where to look for an updated 4.1.2 package.
http://forum.xda-developers.com/showthread.php?t=2240652
So, experiment. Have fun. And if you need speakerphone, scanning camera, then you want to stay at 4.1.2. If those things aren't important, look into the kitkat ROMs, they're excellent. If you decide to go kitkat, you MUST update your recovery.
Sent from my GT-P5110 using XDA Premium 4 mobile app
njstein said:
I'm sorry man, I just realized that the version available for PA isn't what I said. That's my bad. I'll chat with @thomas.raines and see if he can provide a link or something. I'll get back to you on that one.
As far as other stable ROMs, this is AOKP, it was the first rom I Flashed after I rooted, so it has a special place in my heart. I checked the rom link, it's good:
http://forum.xda-developers.com/showthread.php?t=1989825
I haven't ran it in a long while, but I remember it being stable and fast.
This is Liquidsmooth, another I ran that was also stable. I don't remember much about it but I saw that I had it in my signature for a little bit. I won't stay with a rom if it's not stable, so since it was in a sig, it must have been good:
http://forum.xda-developers.com/showthread.php?t=2284763
Try these two and see what you think. If you don't like em, I'll figure something out with thomas and see if I can't get PA back up.
This is a VERY slim gapps package. I'm running it right now on my phone and my Tab. When I say slim, I mean it has Play store and all syncing abilities. That's it. No Search, Gmail, Hangouts, etc. If you want something with all the Google goodies, look around. I'm not one to run gapps with a bunch of Google stuff so I don't know where to look for an updated 4.1.2 package.
http://forum.xda-developers.com/showthread.php?t=2240652
So, experiment. Have fun. And if you need speakerphone, scanning camera, then you want to stay at 4.1.2. If those things aren't important, look into the kitkat ROMs, they're excellent. If you decide to go kitkat, you MUST update your recovery.
Sent from my GT-P5110 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the links, I will install both! You mentioned you install the slimest possible GAPPS, why is that, if I may ask?
EDIT: I reflashed the AOKP ROM, no luck. I am going to flash the other Liquid Smooth ROM and see what happens.
Sorry for the double post again, but I went ahead and installed the AOKP ROM you had posted.
When I go through CWM, it picks up my SD card that I am using, but for some reason, when I have the phone booted up, I go to my camera and get an error that reads similar to what I was getting with the original CM10 which is "No external storage available". Any ideas on how to fix this? I did hit to mount my sdcard on CWM, but no luck. Did reboots and what not, still no luck.
Hmm... In the camera settings, is there an option to change the directory of where a picture saves? Or, and you should check this first, open a file Explorer and go to your ext sd card. Do you have a folder named DCIM?
I don't like all the Google Apps mainly because they cause a ton of wakelocks and I don't ever use them. I use Chrome, but DL'ing that from the Play store asked me to Greenify it, keeping it under control.
Sent from my SAMSUNG-SGH-T769 using XDA Premium 4 mobile app
njstein said:
Hmm... In the camera settings, is there an option to change the directory of where a picture saves? Or, and you should check this first, open a file Explorer and go to your ext sd card. Do you have a folder named DCIM?
I don't like all the Google Apps mainly because they cause a ton of wakelocks and I don't ever use them. I use Chrome, but DL'ing that from the Play store asked me to Greenify it, keeping it under control.
Sent from my SAMSUNG-SGH-T769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
My external SD card does exist when I go to file explorer, and can access all my files on it. I cannot save anything at the moment (from Screenshot, to downloading, to viewing gallery) as I get that dang "No external storage available" message.
darkgiant said:
My external SD card does exist when I go to file explorer, and can access all my files on it. I cannot save anything at the moment (from Screenshot, to downloading, to viewing gallery) as I get that dang "No external storage available" message.
Click to expand...
Click to collapse
Is the DCIM folder there?
Also when you download files what browser are you using?
Sent from my SAMSUNG-SGH-T769 using XDA Premium 4 mobile app
darkgiant said:
Thanks for the links, I will install both! You mentioned you install the slimest possible GAPPS, why is that, if I may ask?
EDIT: I reflashed the AOKP ROM, no luck. I am going to flash the other Liquid Smooth ROM and see what happens.
Click to expand...
Click to collapse
After installing a new ROM, it looks like I still get the error. Any workaround to this?
EDIT: DCIM folder is there, if I were to download anything it would be through the browser.
Alright, so here's what I'm thinking. The stock cameras (if I remember) don't have the option to save to external storage. It was this limitation that made me use a different camera app. So, go to Play Store and get Camera JB+, it has an option to save to external SD card. Find the option (long press the screen, go to settings) change it to external and see if that helps. Or, go into stock camera and see if it has that option. Same with the browser, within settings somewhere there should be an option to change storage location.
If none of that works, my last suggestion is to format both internal and external in recovery. Of course this deletes everything, so transfer all files you want to keep to a computer then format both. Reflash rom on clean install (format cache, dalvik, data, and system) then Reflash everything.
In fact, what did you format/wipe before you Flashed the rom and gapps? This is important and might be the issue...
Sent from my GT-P5110 using XDA Premium 4 mobile app
njstein said:
Alright, so here's what I'm thinking. The stock cameras (if I remember) don't have the option to save to external storage. It was this limitation that made me use a different camera app. So, go to Play Store and get Camera JB+, it has an option to save to external SD card. Find the option (long press the screen, go to settings) change it to external and see if that helps. Or, go into stock camera and see if it has that option. Same with the browser, within settings somewhere there should be an option to change storage location.
If none of that works, my last suggestion is to format both internal and external in recovery. Of course this deletes everything, so transfer all files you want to keep to a computer then format both. Reflash rom on clean install (format cache, dalvik, data, and system) then Reflash everything.
In fact, what did you format/wipe before you Flashed the rom and gapps? This is important and might be the issue...
Sent from my GT-P5110 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I originally was running ICS Stock, after that I flashed to CM10. After that, it was AOKP 4.2.1, and now it is Liquid Smooth's 4.2.1. When I plug my phone into the computer, I cannot access the internal memory card either (just noticed this).
SO... I have fixed the issues!
I found the Stock ROM, flashed that, and suddenly my Camera worked again. After that, I decided to reflash AOKP, and now everything works fluidly! I can't tell what exactly the problem was, but it looks like I have resolved the issues.
Thanks a lot for your help! I look forward to learning more and contributing to the community!
darkgiant said:
SO... I have fixed the issues!
I found the Stock ROM, flashed that, and suddenly my Camera worked again. After that, I decided to reflash AOKP, and now everything works fluidly! I can't tell what exactly the problem was, but it looks like I have resolved the issues.
Thanks a lot for your help! I look forward to learning more and contributing to the community!
Click to expand...
Click to collapse
That's excellent! Glad it worked out. Just a question, before you flashed AOKP, did you do any formatting or wiping in recovery?
Sent from my GT-P5110 using XDA Premium 4 mobile app
njstein said:
That's excellent! Glad it worked out. Just a question, before you flashed AOKP, did you do any formatting or wiping in recovery?
Sent from my GT-P5110 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I did the usual Format and wipe Cache, I usually do those every time when I would flash a new ROM.