Related
So I found out the hard way that Jelly Bean 4.1 isn't compatible with verizon phones, when trying to upgrade to the OTA release anyway.
With that in mind, will Verizon ever get a release? Or is there a way now to make it work?
Thanks
iamTWOcats said:
So I found out the hard way that Jelly Bean 4.1 isn't compatible with verizon phones, when trying to upgrade to the OTA release anyway.
With that in mind, will Verizon ever get a release? Or is there a way now to make it work?
Thanks
Click to expand...
Click to collapse
??? The OTA release was for the GSM version. There are many, many 4.1 Android Jellybean roms within the Verizon-specific development sub forum (even some are clean 4.1 with only some prop changes to make it as stock 4.1 possible)
Unlock your phone and root your phone.
Use Rom manager to flash Clockwork Mod recovery.
Download a 4.1 rom from development, put on the root of your /sdcard.
Boot into clockwork with rom manager.
Make a backup of your current rom incase anything goes wrong.
Go into Advanced, Wipe Dalvik Cache.
From main menu, Wipe cache partition.
From main menu, Wipe data partition.
Install zip from sdcard, choose the rom you downloaded. After it installs there is usually the superuser zip you then flash afterword to get root.
Reboot, be patient for the first boot
Profit
iamTWOcats said:
So I found out the hard way that Jelly Bean 4.1 isn't compatible with verizon phones, when trying to upgrade to the OTA release anyway.
With that in mind, will Verizon ever get a release? Or is there a way now to make it work?
Thanks
Click to expand...
Click to collapse
Oh my Lord. Are you serious? This must be a mistaken case of "I can't read a damn thing."
Yeah, I've been running one of these clean 4.1 verizon-specific roms for about a week now, with no issues.....
NeoMagus said:
Unlock your phone and root your phone.
Use Rom manager to flash Clockwork Mod recovery.
Download a 4.1 rom from development, put on the root of your /sdcard.
Boot into clockwork with rom manager.
Make a backup of your current rom incase anything goes wrong.
Go into Advanced, Wipe Dalvik Cache.
From main menu, Wipe cache partition.
From main menu, Wipe data partition.
Install zip from sdcard, choose the rom you downloaded. After it installs there is usually the superuser zip you then flash afterword to get root.
Reboot, be patient for the first boot
Profit
Click to expand...
Click to collapse
This.
Hi there, I'm new to the forum but have been rooting for about a year. Here is my problem...
I was running stock firmware on my SGS3 and went through the standard cm10 root/rom install process. I flashed CMW with Odin, booted to recovery, installed cm10, jb gapps, cleared cache and delvik cache and rebooted. All the above processes worked fine and once it boots into JB, nothing seems to work. My home button does nothing, the top status bar is blank, no wifi, no keyboard (the process just crashes when I attempt to type).
I know this isn't an issue with CM10 on the SGS3 as this works for most people but does anyone have any ideas on how to remedy this? This may be a unique issue as I can't seem to find anyone else experiencing this.
Also...
I should also mention that I've tried a restore in recovery, reinstalled cm10, blah blah blah, and same results. I've also tried the cm10.m2 roms with the identical results. After reboot I don't even get the welcome wizard. It just boots right into the blank, default JB home screen and starts popping up process failure errors. I can navigate around (though the home button doesn't work) but can't use the keyboard etc.
Am I missing something? Is there a way for me to do a clean restore and try again?
Some technical info:
ClockworkMod Recovery v5.8.4.7
cm-10.0.0-d2att.zip
gapps-JB-20121130-signed.zip
Did you do a complete wipe? Data, cache, Davlik , System and then install cm10.
Coming from stock you need to fully wipe.
Sent from my SAMSUNG-SGH-I747 using xda premium
Machoscrawn said:
I should also mention that I've tried a restore in recovery, reinstalled cm10, blah blah blah, and same results. I've also tried the cm10.m2 roms with the identical results. After reboot I don't even get the welcome wizard. It just boots right into the blank, default JB home screen and starts popping up process failure errors. I can navigate around (though the home button doesn't work) but can't use the keyboard etc.
Am I missing something? Is there a way for me to do a clean restore and try again?
Some technical info:
ClockworkMod Recovery v5.8.4.7
cm-10.0.0-d2att.zip
gapps-JB-20121130-signed.zip
Click to expand...
Click to collapse
Your clockworkMod is out of date to run CM10 & the gapps. Upgrade to the latest clockwork mod, then the latest CM then the latest Gapps and you should be good to go.
dynamiclynk said:
Did you do a complete wipe? Data, cache, Davlik , System and then install cm10.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Thanks for the reply. This is what I did...
(Main cwm menu) -wipe cache partition
(Advanced) -wipe dalvik cache
+++go back+++
-reboot system now
Is there something additional I should clear?
Kweli87 said:
Your clockworkMod is out of date to run CM10 & the gapps. Upgrade to the latest clockwork mod, then the latest CM then the latest Gapps and you should be good to go.
Click to expand...
Click to collapse
Thanks for the reply,
How do i update to the latest clockworkMod? Do you happen to have a URL? I think I found the latest 6.something, but they all seem to be in .iso format.
You can't go from stock rom to CM10 without clearing factory reset thing in CWM.. I don't know the exact text string it uses but it should be right on top of clearing cache.. It looks like you only cleared cache and flashed a new rom.
i386W7 said:
You can't go from stock rom to CM10 without clearing factory reset thing in CWM.. I don't know the exact text string it uses but it should be right on top of clearing cache.. It looks like you only cleared cache and flashed a new rom.
Click to expand...
Click to collapse
Sorry I may have missed mentioning that. The first thing I did was the -factory restore/reset
If updating CWM doesn't help, I'd recommend re-downloading the CM10 zip and verifying the MD5 hash. It could be that the download got corrupted somehow...
goodtimes50 said:
If updating CWM doesn't help, I'd recommend re-downloading the CM10 zip and verifying the MD5 hash. It could be that the download got corrupted somehow...
Click to expand...
Click to collapse
Two questions:
1) What is the best way for me to update cwm?
2) I've seen this MD5 hash recommendation here and there. I have no idea what that means. How would I "verify the MD5 hash".
Machoscrawn said:
Two questions:
1) What is the best way for me to update cwm?
2) I've seen this MD5 hash recommendation here and there. I have no idea what that means. How would I "verify the MD5 hash".
Click to expand...
Click to collapse
Flash one of the rooted stock ROMs. Preferably an ICS one since you are on an older cwm. Wipe data, cache, dalvik. Download ROM manager from the play store. Update your recovery to the latest through that. Than flash back to cm10.
BAM1789 said:
Flash one of the rooted stock ROMs. Preferably an ICS one since you are on an older cwm. Wipe data, cache, dalvik. Download ROM manager from the play store. Update your recovery to the latest through that. Than flash back to cm10.
Click to expand...
Click to collapse
Ok thanks! I'm going to give that a shot and see how it goes.
Machoscrawn said:
Ok thanks! I'm going to give that a shot and see how it goes.
Click to expand...
Click to collapse
Ok so I tried flashing a stock rooted ICS ROM and now I'm stuck on the Samsung logo boot screen. Here is the method I tried, using Odin. http://forum.xda-developers.com/showthread.php?t=1739426
I used the "Bell Image (This works with Canadian Virgin Mobile SGH-I747M) - Old Image I747MVLALH1 (ICS 4.0.4)"
After flashing I booted into the stock recovery and cleared the cache partition then rebooted. Still stuck on the Samsung boot screen.
UPDATE: I just let it sit on the Samsung logo boot screen and it eventually loaded into ICS.
Machoscrawn said:
Two questions:
1) What is the best way for me to update cwm?
2) I've seen this MD5 hash recommendation here and there. I have no idea what that means. How would I "verify the MD5 hash".
Click to expand...
Click to collapse
1) I believe Rom Manager (from the Play Store) can do this.
2) Basically an MD5 value is generated when the file is created and is usually listed on the download page (on get.cm look for "md5sum" right under the download link for each build). There are apps that create an MD5 value from the file that you download and compare against the original to ensure that it's intact. If the values don't match, something's wrong with the file. Check out FastSum (there are lots of others out there too).
goodtimes50 said:
1) I believe Rom Manager (from the Play Store) can do this.
2) Basically an MD5 value is generated when the file is created and is usually listed on the download page (on get.cm look for "md5sum" right under the download link for each build). There are apps that create an MD5 value from the file that you download and compare against the original to ensure that it's intact. If the values don't match, something's wrong with the file. Check out FastSum (there are lots of others out there too).
Click to expand...
Click to collapse
Ok cool. Well i have downloaded ROM Manager but when I try to flash the latest recovery and it gives me a list of devices, mine isn't there. The only S3 listed is "Galaxy S3 (MetroPCS)". The list itself looks incomplete, maybe only 20 devices listed. I've rebooted the phone since installing ROM Manager but the list still only shows the one SGS3.
Machoscrawn said:
Ok cool. Well i have downloaded ROM Manager but when I try to flash the latest recovery and it gives me a list of devices, mine isn't there. The only S3 listed is "Galaxy S3 (MetroPCS)". The list itself looks incomplete, maybe only 20 devices listed. I've rebooted the phone since installing ROM Manager but the list still only shows the one SGS3.
Click to expand...
Click to collapse
Try to download GooManager and select the Flash Roms option, it will prompt you, select *Find one for me* reboot into recovery try to wipe/reset and reinstall the ROM and gapps and see if it works
wally3614 said:
Try to download GooManager and select the Flash Roms option, it will prompt you, select *Find one for me* reboot into recovery try to wipe/reset and reinstall the ROM and gapps and see if it works
Click to expand...
Click to collapse
Ok I tried the Goomanager route. When I'm in recovery doing the install of the rom, I get a FAILED error right after it tries updating partition... I've tried installing from internal and external sd with the same results...
I've attached a screenshot. Well I attempted to with my webcam, hopefully it's semi-readable.
Machoscrawn said:
Ok I tried the Goomanager route. When I'm in recovery doing the install of the rom, I get a FAILED error right after it tries updating partition... I've tried installing from internal and external sd with the same results...
I've attached a screenshot. Well I attempted to with my webcam, hopefully it's semi-readable.
Click to expand...
Click to collapse
Well at least you have the proper twrp definitely try and re download the ROM, carefully make sure it is absolutely the correct ROM(I rushed once, thought I was sure n dl'd the wrong one and bricked my older s3) if u have the slightest break during DL this can happen. I KNOW it is frustrating but worth it in the end
wally3614 said:
Well at least you have the proper twrp definitely try and re download the ROM, carefully make sure it is absolutely the correct ROM(I rushed once, thought I was sure n dl'd the wrong one and bricked my older s3) if u have the slightest break during DL this can happen. I KNOW it is frustrating but worth it in the end
Click to expand...
Click to collapse
Alright, I downloaded the latest stable (the only one) build of CM 10 from get.cm. Removed the current version from my internal sd and tried the process again. Same error...
So again, I'm now using GooManager, TeamWin Rocovery v2.3.1.0, CM10 Stable. Doing a factory reset, then wiping system, then install cm10, this is where it fails.
Any way that I can restore everything on my phone completely to stock and start from scratch? Anything else you/anyone can recommend?
Machoscrawn said:
Alright, I downloaded the latest stable (the only one) build of CM 10 from get.cm. Removed the current version from my internal sd and tried the process again. Same error...
So again, I'm now using GooManager, TeamWin Rocovery v2.3.1.0, CM10 Stable. Doing a factory reset, then wiping system, then install cm10, this is where it fails.
Any way that I can restore everything on my phone completely to stock and start from scratch? Anything else you/anyone can recommend?
Click to expand...
Click to collapse
If youre looking to completely start over. Just grab an unrooted stock .tar from one of the links somewhere around here, put your phone in download mode and let it flash. Clean slate.
Hi, I am currently on Cm10 rom and I want to update to cm10.1. I have Clockwork installed and Goo Manager. I am trying to update my rom through Goo Manager but it keeps bringing me the to Clockwork boot screen, what do I do next? I have no idea what to select to update my rom using Goo, I've tried searching and all the videos I've seen of people using Goo Manager, they never get into the problem since they don't have clockworkmod installed. I tried to uninstall Clockworkmod but it does not give me the option to. Someone please Help!
Its either Rom Manager + CWM or Goo Manager + TWRP, you cant mix and match unless you wanna have issues
For the S3 I would highly recommend TWRP, however you wont be able to restore your backups made with CWM through TWRP
To install TWRP, go into Goo Manager and select "install openrecovery script" and it'll install it. Then try to flash the update again.
CNexus said:
Its either Rom Manager + CWM or Goo Manager + TWRP, you cant mix and match unless you wanna have issues
For the S3 I would highly recommend TWRP, however you wont be able to restore your backups made with CWM through TWRP
To install TWRP, go into Goo Manager and select "install openrecovery script" and it'll install it. Then try to flash the update again.
Click to expand...
Click to collapse
I don't need to try and uninstall CWM? If I download openrecovery script, would it still bring me to the CWM mode? or will it just update my rom through Goo manager? NOTE: In the youtube videos I've watched, they did not wipe cache, etc. when updating a cyanogen rom, I did not do so either, would that be a problem also?
vizi0nz said:
I don't need to try and uninstall CWM? If I download openrecovery script, would it still bring me to the CWM mode? or will it just update my rom through Goo manager? NOTE: In the youtube videos I've watched, they did not wipe cache, etc. when updating a cyanogen rom, I did not do so either, would that be a problem also?
Click to expand...
Click to collapse
Goo Manager will install TWRP over CWM, so you dont need to do anything but wait for it to do its thing. When you go into recovery, it will look different because it will no longer be clockworkmod recovery, it will be TWRP (team win recovery project)
No, when you flash without clearing (also called a dirty flash) thats usually reserved for updates only, because either things were added that dont need clearing, or some files were changed to fix bugs. Although updates are usually done this way, the nature of some updates may still require you to do a full wipe and then flash, but for CM a dirty flash is usually fine. The dev will usually clearly state whether a dirty / clean flash is required for a particular update
Also, remember to make a backup before flashing though! You never know what may go wrong, or if the rom itself may be a bad download, so its better to play it safe and make a nandroid
CNexus said:
Goo Manager will install TWRP over CWM, so you dont need to do anything but wait for it to do its thing. When you go into recovery, it will look different because it will no longer be clockworkmod recovery, it will be TWRP (team win recovery project)
No, when you flash without clearing (also called a dirty flash) thats usually reserved for updates only, because either things were added that dont need clearing, or some files were changed to fix bugs. Although updates are usually done this way, the nature of some updates may still require you to do a full wipe and then flash, but for CM a dirty flash is usually fine. The dev will usually clearly state whether a dirty / clean flash is required for a particular update
Also, remember to make a backup before flashing though! You never know what may go wrong, or if the rom itself may be a bad download, so its better to play it safe and make a nandroid
Click to expand...
Click to collapse
Thanks so much for the help! I actually found the openrecovery script part, now I'm letting it do it's thing, hope it all turns out great! I'll let you know how it turns out!
It turned out great! No problems at all!
What's the best way to update since I can't update with the version that sprint pushed out since I'm rooted. Is it like a hacked version of the update that I can just update with? Yeah I'm a noob at this.
Thanks!
Not sure if your talking about 4.2 which is to my knowledge only with cm 10 or liquidsmooth or aokp most likely or 4.1.2 md4 either case download the appropriate file of your choice and flash from recovery do make sure backup amyways hope that answers your question
Sent from my SPH-L710 using XDA Premium HD app
six3onei said:
What's the best way to update since I can't update with the version that sprint pushed out since I'm rooted. Is it like a hacked version of the update that I can just update with? Yeah I'm a noob at this.
Thanks!
Click to expand...
Click to collapse
I think you mean update to 4.1.2. Check your version in settings about device. If it's 4.1.1 go here :
http://forum.xda-developers.com/showthread.php?p=586
Sent from my SPH-L710
Cm10.1
Sent from my SPH-L710 using xda app-developers app
Deviant Xone (linked in my sig). Awesome 4.2.2 ROM.
If you're going to any AOSP rom, be sure to update your recovery to the latest!
Also - Create a 0 folder in the root of your internal storage and move all of your files into /sdcard/0 (and I mean everything, files, folders, etc.) When you boot into latest recovery, it'll treat the sdcard/0 as your sdcard root folder. Once you flash an AOSP based rom, it will always use sdcard/0 as the root so if you create the 0 folder prior to flashing, you'll have all of your internal memory accessible.
Overstew said:
If you're going to any AOSP rom, be sure to update your recovery to the latest!
Also - Create a 0 folder in the root of your internal storage and move all of your files into /sdcard/0 (and I mean everything, files, folders, etc.) When you boot into latest recovery, it'll treat the sdcard/0 as your sdcard root folder. Once you flash an AOSP based rom, it will always use sdcard/0 as the root so if you create the 0 folder prior to flashing, you'll have all of your internal memory accessible.
Click to expand...
Click to collapse
Apparently you can avoid this by updating your recovery....the emulated 0 folder, I mean
Sent from my SPH-L710
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
I'm running stock rom that I rooted... The phone version as of now is 4.1.2... as of 1 week I recieved an over the air update from sprint. I was thinking its 4.2 something maybe? maybe I wrong. I was wondering how could I get that update to install? Would i have to un-root then re-root?
Thanks!
six3onei said:
I'm running stock rom that I rooted... The phone version as of now is 4.1.2... as of 1 week I recieved an over the air update from sprint. I was thinking its 4.2 something maybe? maybe I wrong. I was wondering how could I get that update to install? Would i have to un-root then re-root?
Thanks!
Click to expand...
Click to collapse
Hey six3onei,
I'm assuming you just got the notification for the OTA (Over-The-Air) update. The newest version of the Stock Rom is MD4 which is still 4.1.2. Android version 4.2.x probably won't come out for your phone for a couple of months (that's my guess with no data to back it up other than my own intuition).
As far as upadating, you actually don't have to apply the OTA to get the latest and greatest for our phone. All you have to do is flash Freeza's Stock Rooted Rom (You'll want the DeOdex MD4 Rom). It'll give you the most up-to-date Stock Rom with Root. I've linked and quoted a previous post I made which will give you directions to flash it. Also, CNexus has done a great guide about OTAs over in the general sub-forum. I suggest giving that a look-through.
Also, just a note on the flashing sequence below: In step 4 below, if you're coming from a stock Rom and you're going to a stock Rom, all you have to do is wipe Cache and Dalvik Cache. If you're going to a different Rom, it's best to do a full wipe (in my opinion).
Ok, let's start at the very beginning (it's a very good place to start).
Before we get started, I'm going to make the following assumptions:
You successfully rooted your phone through Odin.
You currently have a custom recovery (either TWRP or CWM).
You have a Rom you'd like to flash on either your internal storage or your SDcard (I'd recommend the SDcard, but that's your prerogative).
If either of the first two is not true, I'd recommend going back to qbking77's thread and check out the videos on how to use Odin to gain root and a custom recovery.
If number 3 above is not true, download a ROM (nor someone new to flashing/custom Roms, I'd recommend Freeza's stock rooted Rom, as it's identical to stock TW, but just with Root). Once you download a Rom, check it's md5sum to verify that it's a good download. Copy the file to your SD card and get ready to flash (make sure you have decent battery life left, I try to keep at least 50% or more when flashing Roms, although it shouldn't take too long.
I'll give directions on how to flash a Rom below. The instructions will be for TWRP, but CWM has similar options/settings
Turn your phone completely off (hold down power for 3-5 seconds)
Boot your phone into recovery. Hold Up, Menu, and Power for a few seconds (until SAMSUNG appears on your screen and the phone vibrates)
Make a Nandroid backup. I can't emphasize this enough. In flashing, it's almost a certainty that one time, something will mess up. When that happens, you want to be able to restore a backup. In TWRP, just go into Backup Menu and choose where you want it (internal vs. External storage). It takes my phone a few (5-10) minutes to completely backup my data.
In TWRP, click the wipe button, then system. This will completely wipe the Rom from your phone. Doing this will allow you to get a "clean" install, without any settings or leftover files from your old Rom getting in the way. Instead, you could only wipe data (factory reset), which is good enough for most Roms. I'd still recommend a system wipe, though.
Also while in the Wipe menu, wipe Cache and Dalvik Cache.
Go back to the TWRP main menu.
Click Install, then find your Rom zip file (may have to switch from internal to external storage).
Let TWRP do it's thing.
If you're installing a TW-based Rom, chances are it had gapps already installed. If not, you should now flash the correct gapps package from goo.im. Make sure you're flashing the correct one, as if you don't, your google apps will force close upon use.
Reboot into system and give it time to boot (first boot sometimes takes a couple of minutes).
Set up your phone the way you like.
These should be the directions to follow whenever you flash a new Rom. Some Roms have the Aroma installer, so you'll have more options once you choose to flash the Rom zip, but those are typically easy to follow (and vary from Rom to Rom, so I won't be able to give you a good guide on that).
Hope this helps!
Click to expand...
Click to collapse
The rom you want to download off of Freeza's page is:
DeOdex:
Sprint Touchwiz Jelly Bean 4.1.2 L710VPBMD4 | Mirror
MD5: 77262D9D6CF1A6AF30A8981A95A75D57
Click to expand...
Click to collapse
Hey all I'm pretty noob with the flashing and wondering if someone can help me move from the ics stock zvb to something 4.2.2
I'm looking for something stable with minimal bugs and no showstopper bugs to use as a daily driver. I want something I can keep a while without reflashing.
All help and handholding appreciated.
I really don't know what steps I have to take and in what order...
Do I have to reflash the radio again?
Thanks
greenmansofla said:
Hey all I'm pretty noob with the flashing and wondering if someone can help me move from the ics stock zvb to something 4.2.2
I'm looking for something stable with minimal bugs and no showstopper bugs to use as a daily driver. I want something I can keep a while without reflashing.
All help and handholding appreciated.
I really don't know what steps I have to take and in what order...
Do I have to reflash the radio again?
Thanks
Click to expand...
Click to collapse
To jump on the 4.2.2 bandwagon you will need to do all of these steps and depending on the actual ROM might take more really read the installation steps before trying anything and definitely make a backup of your current configuration
Make sure you are on the jb ota (android os 4.1.2) or used the appropriate teeny bin
Must be unlocked ( using freegee... available in the market ), rooted, and using team win recovery (twrp)
Make sure ROM and gapps are on your sdcard
Reboot into recovery
Factory reset
Wipe system (not data/media)
Wipe cache and dalvick cache
Flash ROM
Flash gapps
Then reboot and set everything up
spleef said:
To jump on the 4.2.2 bandwagon you will need to do all of these steps and depending on the actual ROM might take more really read the installation steps before trying anything and definitely make a backup of your current configuration
Make sure you are on the jb ota (android os 4.1.2) or used the appropriate teeny bin
Must be unlocked ( using freegee... available in the market ), rooted, and using team win recovery (twrp)
Make sure ROM and gapps are on your sdcard
Reboot into recovery
Factory reset
Wipe system (not data/media)
Wipe cache and dalvick cache
Flash ROM
Flash gapps
Then reboot and set everything up
Click to expand...
Click to collapse
I didn't get the OTA update, I updated via flash to the zvb stock JB using freegee goomanager and twrp. So do I need the zv9 or zvb teenybin? That's one thing confusing me.
Or should I revert back to stock ICS, then do ota to JB then do Freegee again and flash to 4.2.2?
Aftyer all this, my next phone is going to be a Nexus.
greenmansofla said:
I didn't get the OTA update, I updated via flash to the zvb stock JB using freegee goomanager and twrp. So do I need the zv9 or zvb teenybin? That's one thing confusing me.
Or should I revert back to stock ICS, then do ota to JB then do Freegee again and flash to 4.2.2?
Aftyer all this, my next phone is going to be a Nexus.
Click to expand...
Click to collapse
Okay I got my phone restored back to stock zv8 ota updated to sv9 then zvb
Next I saved a bunch of backups both efs and twrp
Then I flashed my new rom, The very lovely Revolt JB. and after clearing cache and wiping it booted...but....I forgot Gapps...:silly:
Question:
can I flash it over the existing install or do I need to reflash both the rom and Gapps at the same time?
Thanks and cheers
just drop gapps in storage and flash it in recovery you dont need to flash rom again
greenmansofla said:
Okay I got my phone restored back to stock zv8 ota updated to sv9 then zvb
Next I saved a bunch of backups both efs and twrp
Then I flashed my new rom, The very lovely Revolt JB. and after clearing cache and wiping it booted...but....I forgot Gapps...:silly:
Question:
can I flash it over the existing install or do I need to reflash both the rom and Gapps at the same time?
Thanks and cheers
Click to expand...
Click to collapse