Related
I have a nandroid of my rooted honeycomb 3.2.1 install. If I want to flash the leaked stock ICS, is it possible to go back to the nandroid and then go back to stock recovery to install the leak?
I understand I can use the unrooting method but I'm just trying to understand this better and understand my options. I don't wish to go back to the stock images and lock the boot loader again just to flash the update and unlock and root again if I don't have to unless that is just the best way to do it.
crankerchick said:
I have a nandroid of my rooted honeycomb 3.2.1 install. If I want to flash the leaked stock ICS, is it possible to go back to the nandroid and then go back to stock recovery to install the leak?
I understand I can use the unrooting method but I'm just trying to understand this better and understand my options. I don't wish to go back to the stock images and lock the boot loader again just to flash the update and unlock and root again if I don't have to unless that is just the best way to do it.
Click to expand...
Click to collapse
I would really advise that you flash the most recent EOS wingray. Rom #36 and the GApps (Google System apps) package version 10. It seems to be more complete than the ota update, it's easier to flash and you preserve your root and recovery.
Thanks, nice to see someone offer a comparison of the two packages. I'm currently running EOS build 34 from the other night. I guess i was just curious about the stock update. I know there are still some things non-functional with eos and figured the stock rom would be completely functional minus whatever bugs. It does seem like a bit of work to flash it though, since the only thing i can seem to find on what to do is saying to unroot and relock using the moto stock files.
Seems like if im interested in trying a stock rom i shojld just wait for the ota and a rom made from it with root already.
I will miss the notification tray settings in eos if i go stock!
crankerchick said:
Thanks, nice to see someone offer a comparison of the two packages. I'm currently running EOS build 34 from the other night. I guess i was just curious about the stock update. I know there are still some things non-functional with eos and figured the stock rom would be completely functional minus whatever bugs. It does seem like a bit of work to flash it though, since the only thing i can seem to find on what to do is saying to unroot and relock using the moto stock files.
Seems like if im interested in trying a stock rom i shojld just wait for the ota and a rom made from it with root already.
I will miss the notification tray settings in eos if i go stock!
Click to expand...
Click to collapse
True, that.
EOS wingray version 36 with the version 10.1 GApps really fixed most of the remaining issues. There should be a new nightly and there is a new GApps 10.2 to flash today.
Hi everyone!
I am fairly new with android and I just rooted my transformer last night. I was also able to install a custom ROM, revolver 3.11.1 (Honeycomb).
If I want to flash an ICS ROM (Revolver, Android Revolution or Codename), from a custom HC ROM, do I have to do anything else? Or can I just flash it straight away?
Based on what I've read, if ever I wish to downgrade back to honeycomb, I would not just flash a honeycomb ROM. I have found a few guides on how to downgrade back to Honeycomb from ICS. Is this correct?
Since you have cwm, It's as simple as going into recovery and flashing your desired custom rom.
Normal procedure (to avoid conflicts/problems) is to wipe and/or format before flashing a new rom.
A good tool to have is the superwipe lite script found in the Revolution HD thread. (I personally use that instead of the wipe option that is in CWM).
Oh...and you can also backup your current ROM and state by using the backup function in CWM BEFORE you wipe/format. Just in case you don't like the new rom and want to revert.
FYI...if you go ICS and want to restore your HC rom...a restore then a reflash of the HC Rom is needed.
Thanks for the reply!
Just to clarify, once I flash an ICS custom ROM and didn't like it, I can't just flash back to a HC custom rom or stock HC rom. Is this correct?
ragnaboy2010 said:
Thanks for the reply!
Just to clarify, once I flash an ICS custom ROM and didn't like it, I can't just flash back to a HC custom rom or stock HC rom. Is this correct?
Click to expand...
Click to collapse
Yup. Even if you use the restore function...you need to flash that particular HC ROM over the restore. (Because the backup doesn't backup the kernel...so if you don't flash the HC rom...the ICS kernel is still there...and you won't be able to boot)
sorry to hijack the thread but my question is similar so i dun want to start a new one
I am currently on revolver 3.11 as well and thinking to update to a ICS custom rom
I am using the blade OC kernel at the moment. I just want to ask if the new rom comes with the ICS kernel or do I need to look for an ICS kernel to put it manually?
Also, I just want to check that Ti Backup does not back up downloaded data right?
Thanks a million
strikeraj said:
sorry to hijack the thread but my question is similar so i dun want to start a new one
I am currently on revolver 3.11 as well and thinking to update to a ICS custom rom
I am using the blade OC kernel at the moment. I just want to ask if the new rom comes with the ICS kernel or do I need to look for an ICS kernel to put it manually?
Also, I just want to check that Ti Backup does not back up downloaded data right?
Thanks a million
Click to expand...
Click to collapse
Everything is included when you flash one of the available ICS ROM.
There is no custom ICS kernel right now anyway as Asus have not released the kernel source.
Hi everyone i have never flashed before.
I have atrix2 att 2.3.5.
I deleted bloatware and wanted to goto stock and then start applying roms.
I followed the guide for flashing and installed bootstrap, CWM, and J.Y.Daddy's BOOT INTO CWM RECOVERY ON BOOT, and also reset.zip.
Knowing that without bloat there is no chance to go 2.3.6 i followed these steps but when i booted the phone it has a new notification bar etc, but when i checked the about phone iam at 2.3.6
55.13.25
build number is SuperCharged V 5 Update1
So what now? is it normal, or am i in a bad situation?
RaXxaa said:
Hi everyone i have never flashed before.
I have atrix2 att 2.3.5.
I deleted bloatware and wanted to goto stock and then start applying roms.
I followed the guide for flashing and installed bootstrap, CWM, and J.Y.Daddy's BOOT INTO CWM RECOVERY ON BOOT, and also reset.zip.
Knowing that without bloat there is no chance to go 2.3.6 i followed these steps but when i booted the phone it has a new notification bar etc, but when i checked the about phone iam at 2.3.6
55.13.25
build number is SuperCharged V 5 Update1
So what now? is it normal, or am i in a bad situation?
Click to expand...
Click to collapse
Along with just about every custom rom comes custom status bar icons, UI look/feel, etc. This is all a part of running custom roms rather than using stock Moto rom. Don't worry, this is what happens!
Sent from my MB865 using xda premium
Apex_Strider said:
Along with just about every custom rom comes custom status bar icons, UI look/feel, etc. This is all a part of running custom roms rather than using stock Moto rom. Don't worry, this is what happens!
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
True, but I am not sure he knew he flashed a rom.
You may have problems because you just installed a 2.3.6 system on top of a 2.3.5 kernel, among other parts. I did this forever, and it had some issues.
What you should do is fxz back to stock 2.3.5 (read the noob guide, this has been said how to do way to many times, if you don't understand it, search and read more). Then you can do the OTA update and install a rom again if you want.
Yes, i did not flash any rom yet, i was installing the CWM recovery on boot so i would not be in trouble if ever i flashed a rom, but iam already at 2.3.6 some how.
If this 2.3.6 has everything the ota 2.3.6 has then i can stay with this, if not then i will have to fxz stock 2.3.5 and ota again and will have to restore everything :s
RaXxaa said:
Yes, i did not flash any rom yet, i was installing the CWM recovery on boot so i would not be in trouble if ever i flashed a rom, but iam already at 2.3.6 some how.
If this 2.3.6 has everything the ota 2.3.6 has then i can stay with this, if not then i will have to fxz stock 2.3.5 and ota again and will have to restore everything :s
Click to expand...
Click to collapse
it does not have anything, and I promise that you flashed scv6 if that is what is showing as the build. you should fxz then ota
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 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.