I am trying to update my Radio/modem file with the JB Android 4.3 Radio file. It requires that I install CWM 6.0.3.7. Can I install this alongside my TWRP 2.6.3.0 installation or as I have read, it will overwrite my TWRP recovery mode? If it will overwrite, how do I switch between? Just reflash through ODIN using PDA? That seems like a lot of work and the possibilities of breaking might be high just overwriting Customer Recoveries?
If I would install this JB Radio for Android 4.3, how would I go back to GB? I can't find a single GB Radio/Modem. Could I use Radio files for GB instead of wiping and installing stock GB ROM [No Root, No Custom Recovery, but it includes the GB Radio/modem]. The reason I am worried about this, if I need to load my original stock GB 2.3.6 backup with root from my nandroid, I would need the original GB Radio and the nandroid backup/restore feature doesn't include that. All advice is greatly appreciated.
The Radio Does Not Get Backed Up By Cwm/twrp Backup(nandroid) Method.
Click to expand...
Click to collapse
[RADIO][UCMC1] For I727/I727R [09-APR-2013]
http://forum.xda-developers.com/showthread.php?t=2228292
[Q] I have CWM and TWRP installed, is that OK?
http://forum.xda-developers.com/showthread.php?t=2122152
[ROM][ics][uclf5] •∞ EMBRYO •∞ 4.1 •∞ [08-jul-2012] [It has ICS radio files, but no GB files]
http://forum.xda-developers.com/showthread.php?t=1754473
Just flash it with twrp. It'll work just like if you did it with cwm.
I have read that some of the zip files does work with TWRP as well. However I am interested in using the following Custom Rom [SuperLite AOKP JB 4.3 v1.0]. That installation requires CWM 6.0.3.7, because it will prevent the infamous black screen reboot issue. What about GB radio file & installing on top of or installing side by side TWRP & CWM?
[ROM][AOKP]SUPERLITE AOKP JB 4.3 V1.0| BYO | SLgapps | SEPT 30/13
http://forum.xda-developers.com/showthread.php?p=46066949
Pick a recovery and use it. Backups are not cross compatible. If you make a backup with cwm it won't work with twrp.
You can flash radios with either. Just pick one.
Sent from my HTC One using Tapatalk 4
lowao said:
I have read that some of the zip files does work with TWRP as well. However I am interested in using the following Custom Rom [SuperLite AOKP JB 4.3 v1.0]. That installation requires CWM 6.0.3.7, because it will prevent the infamous black screen reboot issue. What about GB radio file & installing on top of or installing side by side TWRP & CWM?
[ROM][AOKP]SUPERLITE AOKP JB 4.3 V1.0| BYO | SLgapps | SEPT 30/13
http://forum.xda-developers.com/showthread.php?p=46066949
Click to expand...
Click to collapse
If you have not already installed a 4.3 ROM, then you are recommended (nay, required) to use CWM 6.0.3.7 to do the initial wipe and install, after that you can switch to TWRP for any flashing after that.There is something that 6.0.3.7 does to the data partition that TWRP doesn't, on the initial setup. Once that is done, it doesn't matter. Flash the JB radio when you flash the 4.3 ROM. And going back to GB if you need to is fairly simple, just follow Vincom's guide. There are lots of flashable zips of GB radios you can use.
I am still a bit confused regarding TWRP & CWM being installed at the same time or side by side. So, let me get this straight. If I want to install JB 4.3 ROM, I must first boot into ODIN, install CWM through ODIN, reboot, boot into CWM, wipe the system, reboot, boot back into ODIN, install TWRP, reboot, boot into TWRP, install the JB 4.3 ROM, and finally preform the last reboot. Is this correct & it won't break either of the custom recoveries? However rpr69 said "switch back to TWRP." Are you inferring TWRP & CWM can be installed side by side? If so, how do I access one over the other?
Regarding GB's radio files:
Which of the following links is the Radio/modem files? Is it the second one? I know of them is the official stock ROM and the other requires the OTA updates. However the poster didn't include the OTA updates yet...
ATT-UCLI3-odexed-cwm.zip http://d-h.st/rDZ
kernel-ucli3-sgh-i727-RD01-cwm.zip http://d-h.st/QfR
[ROM][ICS][UCLI3][09-NOV-2012] Stock odexed & deodexed UNTOUCHED
http://forum.xda-developers.com/showthread.php?t=1982467
Try this, wipe cache and dalvik.....no promises lol [Link is dead.]
https://dl.dropbox.com/u/60567424/modem-UCLI3.zip
http://forum.xda-developers.com/showpost.php?p=33344009&postcount=22
Sadly no link for UCLI3 [GB's Radio files.]
[ROM][ics][uclf5] •∞ EMBRYO •∞ 4.1 •∞ [08-jul-2012]
http://forum.xda-developers.com/showthread.php?t=1754473
The 1Stop post from Vincom:
http://forum.xda-developers.com/showthread.php?t=1785999
Sadly there are no more links for GB / UCLI3 radio files.
I know you posted but its confusing, let me simplify, I hope:
im assuming you have either cwm or twrp installed, if on stock read this.
you cannot have two recoveries installed at the sametime:
recovery install procedure:
if not on cwm6037 flash cwm6037 with what ever recovery you have now and reboot back into recovery.
then flash any custom jb4.3 rom, preferably latest cm10.2 nightly found here and reboot rom at least twice.
if you like cwm 6037 stay with it, I don't, or else just flash twrp 2.6.3.0 w/cwm 6037 and reboot back into recovery or rom.
now you can just stay w/the cm10.2 nightly you flashed with cwm 6037 or flash any other rom w/twrp 2.6.3.0 which is now your installed recovery.
that's it you should not have the reboot problems on any jb4.3 roms.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
above recovery install procedure is only if a jb4.3 rom on its 2nd reboot just has a black screen and wont boot into rom, but 2nd boot does usually take longer than normal upto a full minute.
if flashing a rom or restoring from nandroid(recovery backup) prior to jb4.3 and then later decide to flash a jb4.3 rom you need todo above recovery installation procedure b4 flashing a jb4.3 rom.
restoring backups only work with whatever recovery they were made with, you cannot restore a cwm backup w/twrp recovery and vice a versa.
newest versions of recoveries should restore backups made with their older versions.
why do u want an old radio, they will not work w/jb roms
old radios are linked in the 1stop sticky under "old stuff".
installing the radio has nothing todo with the recovery you are using.
flash jb radios for jb roms which happen to be all the current roms.
reread the radio section in the 1stop sticky.
I linked this post in the recovery section of the 1stop sticky
Thank you vincom for explaining the process of using both CWM 6.0.3.7 & TWRP 2.6.3.0 together. I am familiar with backups ONLY working with their original customer recovery. I didn't even think about older versions of backups (not) working with newer custom recoveries. Was there an issue working with older backups in the past?
The reason I need the old GB Radio/Modem files, because when I have to return the phone to stock & load up my old Gingerbeard nandroid, I will be able to return it back to AT&T with the original Radio files and the original Gingerbeard OS. Anywho, thank you for the GB radio. I really appreciate it!
lowao said:
Thank you vincom for explaining the process of using both CWM 6.0.3.7 & TWRP 2.6.3.0 together. I am familiar with backups ONLY working with their original customer recovery. I didn't even think about older versions of backups (not) working with newer custom recoveries. Was there an issue working with older backups in the past?
The reason I need the old GB Radio/Modem files, because when I have to return the phone to stock & load up my old Gingerbeard nandroid, I will be able to return it back to AT&T with the original Radio files and the original Gingerbeard OS. Anywho, thank you for the GB radio. I really appreciate it!
Click to expand...
Click to collapse
u can return any phone that has any stock firmware, with our phones that would be stock jb4.1.2 and using odin would be the way to do it , link in my sig. this is assuming your carrier used the latest firmware as with att and rogers.
I am with AT&T and I never got the official ICS or JB through updates. Actually, I thought ICS was discontinue, because it was bricking phones. Thus the stock ICS & JB Roms here were ported over?
lowao said:
I am with AT&T and I never got the official ICS or JB through updates. Actually, I thought ICS was discontinue, because it was bricking phones. Thus the stock ICS & JB Roms here were ported over?
Click to expand...
Click to collapse
these are untouched full official stock firmwares( radio, recovery, kernel and apps/bloatware), just use odin and flash whatever version you want, all info is in the restore to stock sticky
lowao said:
I am with AT&T and I never got the official ICS or JB through updates. Actually, I thought ICS was discontinue, because it was bricking phones. Thus the stock ICS & JB Roms here were ported over?
Click to expand...
Click to collapse
nope, both are fine and are still available officially. You don't need gingerbread to return it.
Sent from my HTC One using Tapatalk 4
I have to go to Samsung's website and download their Kies software to upgrade to Jelly Bean right? It won't be pushed out through Settings > About Phone > System Update then?
Or you can use Odin.
Sent from my HTC One using Tapatalk 4
So if you're flashing 4.3 ROMs just use cwm? Went from twrp to cwm and back to twrp and am getting the same black boot screen on a slim 4.3 weekly.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
beachmiles said:
So if you're flashing 4.3 ROMs just use cwm? Went from twrp to cwm and back to twrp and am getting the same black boot screen on a slim 4.3 weekly.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
To properly set everything up, you need to use the recommended CWM for 4.3, do a full factory wipe, and make sure that data is formatted. Then install the ROM and boot it up. Reboot to verify it works properly. Then you can go to TWRP 2.6.0.1 or later.
I've been using twrp since release and not had any issues why do we need cwm? What's the technical reasoning.
Sent from my XT1080 using Tapatalk
Didn't work
I followed this procedure exactly and it still didn't work.
I gave it ten minutes between boots and ended up having to pull the battery each of the three times I rebooted.
Fortunately I've gotten into the habit of making a backup before flashing, so it was just a loss of 45 minutes of my evening.
I was trying to get the latest CM10.2 Stable build. Has anyone gotten this thing to flash and work as well as 10.1.3 RC2 or 10.1.3 Final? This issue started for me with the second 10.2 Nightly.
...
Just NOW began seeing the replies to the main post. I don't have ANOTHER fresh install in me: I've already had to do that twice with the 2012 Nexus7 and once with the Skyrocket in the last six weeks.
Related
Hi all,
I'm sorry about my stupid question but I really don't know nothing about that . I had rooted and flashed my NS and installed the matr1x kernel (very good btw), and now I knew that JB will be available to NS. My question is, need I back to stock kernel to receive the update?
Thanks
Sent from my Nexus S using xda app-developers app
Gnng
You have to understand that installing an OTA (official update) on a rooted device regardless of what kernel can cause problems, as it did with my Nexus S before. I suggest you make a NANDroid backup at all times before you install any ROMs, official or Custom. You can also use Titanium backup and others.
There's still a slight while until the new JB 4.1 comes out. It's suggested that you install a Custom JB 4.1 ROM for your Nexus S as though you don't cause any problems. I think it's OK if you do it with the kernel pre-installed. But people always install the Custom ROM THEN they install the Kernel, I think installing a new ROM always overwrites the kernel, if it comes with it.
EDIT:
In short, wait for the JB Custom ROM and you don't have to revert back to stock kernel, when you do the update it will automatically overwrite. Most Custom ROMs come with Stock/ordinary kernels. So then the user can flash whatever kernel they like in your case, matr1x.
Wish you the best of luck, and I am waiting for the Nexus S JB to come out as soon as possible
Ota binary patches the boot image iirc. So it can get all messed up.
Sent from my Samsung Epic 4G using Tapatalk 2
Yeah, what he said!
MДЯCЦSДИT said:
Ota binary patches the boot image iirc. So it can get all messed up.
Click to expand...
Click to collapse
andezzat,
Thank you very much for the help.
andezzat said:
Gnng
You have to understand that installing an OTA (official update) on a rooted device regardless of what kernel can cause problems, as it did with my Nexus S before. I suggest you make a NANDroid backup at all times before you install any ROMs, official or Custom. You can also use Titanium backup and others.
Click to expand...
Click to collapse
I didn't any backup before flashing a new kernel :crying:, so what can I do now if I want my stock kernel back?? What's a NANDroid (I know that is a tool but how can I do it?) ? Is Titanium bkp easily?
There's still a slight while until the new JB 4.1 comes out. It's suggested that you install a Custom JB 4.1 ROM for your Nexus S as though you don't cause any problems. I think it's OK if you do it with the kernel pre-installed. But people always install the Custom ROM THEN they install the Kernel, I think installing a new ROM always overwrites the kernel, if it comes with it.
Click to expand...
Click to collapse
I prefer wait for stock JB Rom and probaby I'll , but, can I already find some JB ROM?
In short, wait for the JB Custom ROM and you don't have to revert back to stock kernel, when you do the update it will automatically overwrite. Most Custom ROMs come with Stock/ordinary kernels. So then the user can flash whatever kernel they like in your case, matr1x.
Click to expand...
Click to collapse
I don't need to remove the kernel even unroot my cell, alright?
Thank you!!
Gnng said:
I didn't any backup before flashing a new kernel :crying:, so what can I do now if I want my stock kernel back?? What's a NANDroid (I know that is a tool but how can I do it?) ? Is Titanium bkp easily?
Click to expand...
Click to collapse
A NANDroid backup is a internal memory backup. You can create one by booting into Recovery (Power off your phone and Hold Power and Down on your volume buttons.) If you rooted your phone and unlocked your bootloader (that's what you had to do to flash a new kernel), you should be able to load ClockworkMod or TeamWin Recovery and do a backup of your phone.
Gnng said:
I prefer wait for stock JB Rom and probaby I'll , but, can I already find some JB ROM?
Click to expand...
Click to collapse
There's one rom but it's a port from the SDK and the amount of major bugs is high so it's not recommended but you could try another custom rom meanwhile, I can't go back to stock after trying custom roms, like AOKP and Cyanogenmod 9. Make sure you backup your apps and some settings (not everything will be compatible between stock and custom so pay close attention to which system setting you'll backup) with Titanium Backup.
To sum it all up for you
There's a Jelly Bean release which is unstable and has no sound, and will not be fixed until the REAL version comes out.
NANDroid backs up the whole internal memory on the phone including the system, it can be done from clockworkmod recovery.
Titanium backup, backs up specific settings and information that you choose, available from the playstore.
You don't need to unroot or go back to a STOCK kernel in order to flash a CUSTOM ROM. DO not however flash a STOCK rom after rooting, as at times that can cause problems.
If you want to go back to a STOCK ROM after rooting a device, there's a way, check this guide
http://forum.xda-developers.com/showthread.php?t=1063664
and choose your Nexus S model: To acquire model, go to Settings - About - Baseband version. if it says I9023 at the start that's your Nexus S's model
Choose one of the Fastboot Stock ROMs and use the Fastboot method to flash the ROM. That is a good way to go back to STOCK ROM if anything bad happens
By the way you should expect the new OTA official 4.1 update for the Nexus S to be on your model's page.
NOTE: Using Fastboot to flash a ROM is very clean. However this will delete all your data and if you do everything correctly will lock your bootloader and unroot your phone. So use Fastboot only when you really feel the need to.
Cheers
and stay tuned for Jelly Bean :victory:
andezzat said:
To sum it all up for you
You don't need to unroot or go back to a STOCK kernel in order to flash a CUSTOM ROM. DO not however flash a STOCK rom after rooting, as at times that can cause problems.
Click to expand...
Click to collapse
That means, when I receive the official 4.1 update notification, I should unroot my phone first and just install it after?
Gnng said:
That means, when I receive the official 4.1 update notification, I should unroot my phone first and just install it after?
Click to expand...
Click to collapse
OK first off, do not install the update using the system update method from about, as that is a 100% stuff up if you're still rooted or on a Custom ROM.
However to update I think flashing a stock ROM but USING Clockworkmod works fine!
Someone please confirm, as I am not 100% sure
However what I am sure about is that if you run into any troubles installing your STOCK ROM using Fastboot is very very good and clean, however there are 2 things:
1. You will wipe everything COMPLETELY
2. You need the ROM to be in a fastboot format kind of way for you to flash it
There's a guide and everything for fastboot.
---------- Post added at 12:35 AM ---------- Previous post was at 12:33 AM ----------
Personally I will wait for a custom ROM for 4.1 if it doesn't take too long as that's guaranteed and will obviously be faster and safer to install on a ROOTED device.
Someone still confirm if installing Stock ROM while over Custom ROM while ROOTED through CWM is OK or not!?
Hummm, ok...
I'm already using the Stock ROM, I just flashed a new kernel, and I prefer install the stock kernel and unroot my phone. Just to let it clean.
After I install the JB official update, maybe I flash and root again, depends of Google :laugh:
Do you know where can I download a trust official 4.0.4 kernel from the forums? My phone is a Nexus S I9020AUCKJ1, Version Number: IMM76D
Thanks!!!
I've been unable to flash CM9 without getting stuck in boot, no matter what I try. I rooted before the OTA upgrade to ICS, and was never able to upgrade.
I was going to use CWM to do a factory reset and try to update to ICS before trying again. I have backed up to the internal and an external SD card, but I wanted to be sure that doing a factory reset with CWM wouldn't make me lose root or clockwork mod. Every tutorial or FAQ I've read fails to suggest. It wouldn't be a big issue to re-root if the reset works, but I'm worried it will suffer the same problems as I'm having with CM9, and I'll be unable to boot into recovery.
sounds like the OTA removed root. this is not uncommon but not sure for your phone.
Sent from my HTC Glacier using xda premium
you will lose root and cwm if you install stock firmware through odin, you can flash cwm flashable stock, wont lose cwm but will lose root, more info in 2nd link in my sig, read the stickies, well mine anyways
romuloxiii said:
sounds like the OTA removed root. this is not uncommon but not sure for your phone.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
No, I still have root. The OTA didn't work. Titanium backup works, as does tethering.
I just want to know if resetting with CWM will let me go back if it doesn't work.
interkin3tic said:
No, I still have root. The OTA didn't work. Titanium backup works, as does tethering.
I just want to know if resetting with CWM will let me go back if it doesn't work.
Click to expand...
Click to collapse
The OTA didn't work because u don't have strock recovery. make a backup, flash stock recovery, flash OTA. If OTA doesn't work, flash back custom recovery and restore backup. You'll want to restore custom cam anyway, so there's that
icenight89 said:
The OTA didn't work because u don't have strock recovery. make a backup, flash stock recovery, flash OTA. If OTA doesn't work, flash back custom recovery and restore backup. You'll want to restore custom cam anyway, so there's that
Click to expand...
Click to collapse
I tried flashing "near stock" (http://forum.xda-developers.com/showthread.php?t=1764747) and got another boot animation loop. Is that what you mean by "flash stock recovery."
interkin3tic said:
I tried flashing "near stock" (http://forum.xda-developers.com/showthread.php?t=1764747) and got another boot animation loop. Is that what you mean by "flash stock recovery."
Click to expand...
Click to collapse
Right now you have cwm recovery. He wants you to flash the stock Samsung recovery. I'm pretty sure there is a link in one of Vincom's stickies.
Why don't you just Odin stock 4.0.4, flash cwm in Odin and then flash cm9 in cwm?
Which version of cwm are you on btw?
------------------------------------------------
Sent from my Skyrocket i727 running AOKP JB
For a one stop shop are Vincom's threads
Everything Root: http://forum.xda-developers.com/showthread.php?t=1773659
Returning to Stock: http://forum.xda-developers.com/showthread.php?t=1652398
Mike on XDA said:
Right now you have cwm recovery. He wants you to flash the stock Samsung recovery. I'm pretty sure there is a link in one of Vincom's stickies.
Why don't you just Odin stock 4.0.4, flash cwm in Odin and then flash cm9 in cwm?
Which version of cwm are you on btw?
------------------------------------------------
I'm on CMW 5.0.2.7.
I was trying the one I linked to because it seemed simpler and because I knew I could get into recovery mode with CWM. I was paranoid that reverting to stock with Odin would leave me with a boot loop and no CMW to restore from.
I suppose Odin to flash CWM worked last time, when I rooted the phone in the first place, and you guys seem to know what you're talking about, so I'll try that tomorrow.
Click to expand...
Click to collapse
interkin3tic said:
I'm on CMW 5.0.2.7.
I was trying the one I linked to because it seemed simpler and because I knew I could get into recovery mode with CWM. I was paranoid that reverting to stock with Odin would leave me with a boot loop and no CMW to restore from.
I suppose Odin to flash CWM worked last time, when I rooted the phone in the first place, and you guys seem to know what you're talking about, so I'll try that tomorrow.
Click to expand...
Click to collapse
First, flash sk8's cwm 6.0.1.2 in your current cwm recovery. Reboot. Go back into recovery (it will now be the updated recovery) try one more time to get cm9 running. Wipe data/factory reset, cache, dalvik, format/data, format/system, format/cache all x3. (Format/ is under mounts and storage. Dalvik cache is in advanced). Then flash ROM, followed by radio (if you aren't already on an ICS radio), and gapps. When you are done let the phone sit for a good 10 minutes as the cache's need to build and the first boot always takes much longer. It may be your outdated cwm that is holding you back. Try this first and if you still are boot looped then Odin back to stock
------------------------------------------------
Sent from my Skyrocket i727 running AOKP JB
For a one stop shop are Vincom's threads
Everything Root: http://forum.xda-developers.com/showthread.php?t=1773659
Returning to Stock: http://forum.xda-developers.com/showthread.php?t=1652398
When I wipe dalvik cache, an error comes up "E: unknown volume for path [/sd-ext]
I assume this is because I don't have an external SD card in.
Installing CM9 after all those wipes and formats failed.
"Assert failed: getprop("ro.product.device")=="SGHI727" ||getprop("ro.build.product")
Has similar things for "SGHI727", "hercules", "and "skyrocket".
Looks like it's looking at the zip files for CM9, the radio, and the near stock rom I mentioned earlier.
So instead I flashed the near stock rom, will follow with the ICS radio/modem from the same source.
I also hadn't waited 10 minutes previously.
Anyway, that worked, I now have ICS at least. I'm going to hold off on flashing CM9 for the moment.
Your problems are with cwm 5.0.2.7 and then flashed a current ROM.
Flash cwm as stated above, version 6 from recovery, format system data and caches, then flash whatever ROM you want.
1. Copy cwm v6 to your sdcard
2. From your current cwm recovery install the new cwm 6
3. Reboot back into recovery, should now be version 6
4. Format system data and both caches
5 then flash your favorite rom
Posted w/xda app w/ i727R
MY STICKIES
| ROMS | KERNELS | FIRMWARE | RADIOS | HOWTO'S | GUIDES | INFo |
NEWB GUIDES TO: RESTORE TO STOCK | USE ODIN | INSTALL CWM | ROOT |
So I just rooted my Verizon Galaxy S3 and unlocked the bootloader. I flashed Clockworkmod recovery using Rom Manager to update to the latest version. Made a nandroid, installed Titanium Backup, linked it to my Dropbox and uploaded. I downloaded the latest CM10 nightly to flash but the stock android recovery appeared instead of CWM. Found some info that I need to flash a clockwork compatible kernel first. The questions I have are: If I install the latest CM 10 nightly will it automatically install a clockwork compatable kernel? If not, where can I download it from? and if I do need to flash a kernel first can anyone give me detailed instructions how to do this as i'm relatively new to this stuff and don't want to brick my phone. Thanks, any info would help.
iwearthebelt said:
So I just rooted my Verizon Galaxy S3 and unlocked the bootloader. I flashed Clockworkmod recovery using Rom Manager to update to the latest version. Made a nandroid, installed Titanium Backup, linked it to my Dropbox and uploaded. I downloaded the latest CM10 nightly to flash but the stock android recovery appeared instead of CWM. Found some info that I need to flash a clockwork compatible kernel first. The questions I have are: If I install the latest CM 10 nightly will it automatically install a clockwork compatable kernel? If not, where can I download it from? and if I do need to flash a kernel first can anyone give me detailed instructions how to do this as i'm relatively new to this stuff and don't want to brick my phone. Thanks, any info would help.
Click to expand...
Click to collapse
Did you unlock your bootloader? for a custom recovery to stick you need to unlock your bootloader. Follow this guide
http://forum.xda-developers.com/showthread.php?t=1762709
darkhawk3383 said:
Did you unlock your bootloader? for a custom recovery to stick you need to unlock your bootloader. Follow this guide
http://forum.xda-developers.com/showthread.php?t=1762709
Click to expand...
Click to collapse
I did, had it unlocked and rooted. I guess there was some sort of issue with Rom Manager on the S3. I use it on my Galaxy Nexus and have no issues. I ended up abandoning what I was doing, uninstalling Rom Manager and going a different route. I have no prior experience with Odin but figured out how to install CWM . Downloaded I535vrblk1, flashed CWM, unlocked & rooted again. . Thanks anyway for the reply.
You can reinstall ROM Manager. It is something to do with some of the newer OTA's and the leaks. I have read a few posts in the forums about this in the GS3 and I really can't remember the fix but your recovery not sticking had nothing to do with ROM Manager. I think the fix was when you rebooted to recovery to flash a kernel right away, whether it be KT747, LK, or any of the other. Now that I typed this I'm about 99% sure that was the fix. Like I said above though, it has nothing to do.with ROM Manager, so if you're like me and find a lot of the tools in it handy you should be able to reinstall it. If you have a problem again just flash a kernel.
Sent from one of the many Anthropomorphic Personalities on the Disc
I bought an S3 today that was already rooted with CleanRom 5.5.1 installed. I am wanting to install CM10. What are the steps I need in order to do so?
Harikiri13 said:
I bought an S3 today that was already rooted with CleanRom 5.5.1 installed. I am wanting to install CM10. What are the steps I need in order to do so?
Click to expand...
Click to collapse
Download latest cm10,gapps, go to recovery, wipe data/system/cache/dalvic, flash Rom then gapps. Make sure you have the latest recovery whether it's twrp or cwm.
Also if your going to flash a kernel, make sure it's aosp and and 3.4 if you're going to flash the latest cm10. I usually set up my phone and then go back to recovery and flash a kernel.
Also,I would backup your imei. There's a few threads around about why to do so and how to back it up. Sorry, can't post any links at the moment
Sent from my SCH-I535 using Tapatalk 4 Beta
Don't forget to backup your current ROM if it isn't already and
Go over to rootzwiki there is a stickied thread there about making a special backup for your nv items (imei meid n stuff)
So like the title says I have been out of the ROM game for a little bit. Every couple of months I check in and see whats new and flash something else.
I was on the Jelly Beans ROM (Build 16 I think) and Android 4.1. I did some searching last night as was going to try flashing Gummy ROM…bad idea. I am guessing I needed something prior to jumping up to a 4.4 base. I booted to recovery and wiped everything and tried to flash with no luck. So the phone would not boot and I could only get into recovery and download mode. I did not have my micro SD adapter in order to get jelly beans back on it to flash so I ended up having to use odin to flash a stock rooted 4.1 image. Finally got everything back up and running but I still want to try some of the 4.4 ROMs. So what exactly do I need first in order to flash one? (Modem maybe)…if you know for sure why that happened and what I need to do please let me know. Thanks!
My Current "About Phone" Info...
Android Version - 4.1.2
Baseband version - I535VRBMB1
Jelly Beans - Build 20
P.S. I have tried doing the research and nothing I have found has been clear but one thing I came across is the official 4.3 update was bad news and broke the root methods? So should I stay away from 4.3 ROMs and is the old root method blocked in 4.4 as well or is that a different case since it wasn't actually released for our phone. If that makes sense lol
aholeinthewor1d said:
So like the title says I have been out of the ROM game for a little bit. Every couple of months I check in and see whats new and flash something else.
I was on the Jelly Beans ROM (Build 16 I think) and Android 4.1. I did some searching last night as was going to try flashing Gummy ROM…bad idea. I am guessing I needed something prior to jumping up to a 4.4 base. I booted to recovery and wiped everything and tried to flash with no luck. So the phone would not boot and I could only get into recovery and download mode. I did not have my micro SD adapter in order to get jelly beans back on it to flash so I ended up having to use odin to flash a stock rooted 4.1 image. Finally got everything back up and running but I still want to try some of the 4.4 ROMs. So what exactly do I need first in order to flash one? (Modem maybe)…if you know for sure why that happened and what I need to do please let me know. Thanks!
My Current "About Phone" Info...
Android Version - 4.1.2
Baseband version - I535VRBMB1
Jelly Beans - Build 20
P.S. I have tried doing the research and nothing I have found has been clear but one thing I came across is the official 4.3 update was bad news and broke the root methods? So should I stay away from 4.3 ROMs and is the old root method blocked in 4.4 as well or is that a different case since it wasn't actually released for our phone. If that makes sense lol
Click to expand...
Click to collapse
you need the latest recoveries to flash kk roms. cwm is here https://www.clockworkmod.com/rommanager
and twrp is here http://teamw.in/project/twrp2/102. make sure you download the d2vzw version
if you're rooted you should have no problems flashing 4.4 rom. I recommend beanstalk from here http://forum.xda-developers.com/showthread.php?t=2354113. has worked great for me. you have to also update the modem to ML1 from here http://forum.xda-developers.com/showthread.php?t=1788313
as always do a nandroid before you do anything and you should backup your sd card to your computer. they probably will move post this to another thread.
good luck
dandydon414 said:
you need the latest recoveries to flash kk roms. cwm is here https://www.clockworkmod.com/rommanager
and twrp is here http://teamw.in/project/twrp2/102. make sure you download the d2vzw version
if you're rooted you should have no problems flashing 4.4 rom. I recommend beanstalk from here http://forum.xda-developers.com/showthread.php?t=2354113. has worked great for me. you have to also update the modem to ML1 from here http://forum.xda-developers.com/showthread.php?t=1788313
as always do a nandroid before you do anything and you should backup your sd card to your computer. they probably will move post this to another thread.
good luck
Click to expand...
Click to collapse
ahh I didn't even think of that? I do know for a fact whatever version of CWM i had was not recent..Are you sure that is the only issue? so with a newer recovery...like I have now that I fixed my phone..I can flash a 4.4 ROM no problem? I could have sworn I remember hearing something about needing a certain modem...or something similar
aholeinthewor1d said:
ahh I didn't even think of that? I do know for a fact whatever version of CWM i had was not recent..Are you sure that is the only issue? so with a newer recovery...like I have now that I fixed my phone..I can flash a 4.4 ROM no problem? I could have sworn I remember hearing something about needing a certain modem...or something similar
Click to expand...
Click to collapse
yes. flash the ML1 modem. I provided the link in my previous post. it's a fact that earlier recoveries won't flash kk roms. I found out the hard way myself. hopefully you'll have titanium or rom toolbox to backup your apps with data.
dandydon414 said:
yes. flash the ML1 modem. I provided the link in my previous post. it's a fact that earlier recoveries won't flash kk roms. I found out the hard way myself. hopefully you'll have titanium or rom toolbox to backup your apps with data.
Click to expand...
Click to collapse
Thanks a lot!!.. So how do I know if my recovery is new enough? I was never a fan of the touch recoveries because I felt like it would be easier to do something on accident so I haven't tried one in a while...I am using clockwork mod recovery 6.0.4.5. Is that new enough??
Also one lasttttt question I swear...can someone give me a quick list of the different recovery options that are out there now...and maybe list some features of each...thank you
aholeinthewor1d said:
Thanks a lot!!.. So how do I know if my recovery is new enough? I was never a fan of the touch recoveries because I felt like it would be easier to do something on accident so I haven't tried one in a while...I am using clockwork mod recovery 6.0.4.5. Is that new enough??
Also one lasttttt question I swear...can someone give me a quick list of the different recovery options that are out there now...and maybe list some features of each...thank you
Click to expand...
Click to collapse
that recovery is fine. i've only used cwm and twrp.. had some problems with philz recovery so I ditched it. basically they're all the same. twrp lets you name your back where as cwm just uses some default name which of course you can change with a file manager. twrp also wipes all 3 (system, cache and dalvik) with one swipe where as cwm requires 3 separate operations. I really haven't done much in recovery other than wiping and flashing. I'm actually on the latest twrp and have had no problems flashing kk roms. keep in mind that you can't backup in cwm and restore it using twrp and vice versa. it's really more a personal preference as far as I'm concerned.