Related
Hi guys, each time that I try to upgrade 4.04 by OTA, it stopped and appear the Android with the red exclamation on it.
I've used the 'WugFresh unlocked toolkit' to root/unlock Galaxy Nexus.
For install OTA 4.0.4 from Google, I need to lock the phone again?
If I back to default configs - using WugFresh again - the OTA, and after the root/unlock, work without problems?
Thanks.
That's the stock recovery you're seeing.
What images have you changed?
If you revert to the stock ones (radio/bootloader/etc) you should get the OTA.
Jubakuba said:
That's the stock recovery you're seeing.
What images have you changed?
If you revert to the stock ones (radio/bootloader/etc) you should get the OTA.
Click to expand...
Click to collapse
Why dont you show this guy the light and let him flash google factory image by himself..
OP: there you go http://forum.xda-developers.com/showthread.php?p=23229558
Galaxy Nexus AOKP m5 Franco kernel m3
Thank you, guys.
RaptorHawk said:
Hi guys, each time that I try to upgrade 4.04 by OTA, it stopped and appear the Android with the red exclamation on it.
I've used the 'WugFresh unlocked toolkit' to root/unlock Galaxy Nexus.
For install OTA 4.0.4 from Google, I need to lock the phone again?
If I back to default configs - using WugFresh again - the OTA, and after the root/unlock, work without problems?
Thanks.
Click to expand...
Click to collapse
You are seen that screen because you have something on your device that is not stock. (Unlocked and rooted makes no difference.)
To be 100% sure that an OTA update will install automatically, you need to have all of the following:
1) the radio that came with the ROM that you are using;
2) the stock recovery that came with the ROM that you are using;
3) the stock kernel that came with the ROM that you are using;
4) all of the original files in /system that came with the ROM that you are using.
Have a look at the thread here. It is for manual installation of an update, but the requirements still apply to an automatic update OTA.
So if I uninstalled apps to the system and do the lock/unroot, this will cause problems when I try to upgrade from version 4.0.2 to version 4.0.4?
I uninstalled Google Maps, Youtube and Earth.
RaptorHawk said:
So if I uninstalled apps to the system and do the lock/unroot, this will cause problems when I try to upgrade from version 4.0.2 to version 4.0.4?
I uninstalled Google Maps, Youtube and Earth.
Click to expand...
Click to collapse
You are not reading at all at what efrant says and you havent looked at the link i provided.. Until you do so you wont go farther
Galaxy Nexus AOKP m5 Franco kernel m3
Yes, I read, but maybe I did not quite understand ...
To recap: I used Wug's Toolkit and now I can no longer install the 4.0.4 update official Google OTA. So I would like to know how to undo it, install 4.0.4 and then apply the Wug toolkit again.
According to the links, I need to undo the changes before, but I can not undo the root by Wug's Toolkit, because he can not download a file, appear an error message that could not be found.
What I wonder is, how to get back to what it was prior to applying the 4.0.4 update and then do the root again? Is that possible?
Thanks.
Forget about toolkits, follow this guide please
http://forum.xda-developers.com/showthread.php?p=25477039
Galaxy Nexus AOKP m5 Franco kernel m3
RaptorHawk said:
Yes, I read, but maybe I did not quite understand ...
To recap: I used Wug's Toolkit and now I can no longer install the 4.0.4 update official Google OTA. So I would like to know how to undo it, install 4.0.4 and then apply the Wug toolkit again.
According to the links, I need to undo the changes before, but I can not undo the root by Wug's Toolkit, because he can not download a file, appear an error message that could not be found.
What I wonder is, how to get back to what it was prior to applying the 4.0.4 update and then do the root again? Is that possible?
Thanks.
Click to expand...
Click to collapse
There are two ways to get 4.0.4:
1) Flash a full 4.0.4 ROM, which is what the link msedek posted is.
2) Upgrade 4.0.2 to 4.04, which is the link I posted a couple of posts back.
In the first case, you easily end up with a clean install, but your data is erased (so back up before)
In the second case, you need to make sure that you undo any modifications you made to the /system partition, the kernel, the radio, and the recovery. Then you apply the update, and you will have an upgraded ROM with all your data and settings intact.
RaptorHawk said:
So if I uninstalled apps to the system and do the lock/unroot, this will cause problems when I try to upgrade from version 4.0.2 to version 4.0.4?
I uninstalled Google Maps, Youtube and Earth.
Click to expand...
Click to collapse
Actually, this is true. I was having the same issues. When i rooted, I deleted system apps I did not want. For weeks and weeks I kept receiving the popup message saying that the update to 4.0.4 was available. When attempting to upgrade, it would always fail on reboot.
Just two days ago, I received the upgrade notice again. I immediately went into Recovery mode, and attempted to manually install the update file from the system directory. When I did, I received an error right away saying the update could not find "TabletBooks.apk" (I deleted Google Play Books since I dont use it).
I reinstalled a clean image of 4.0.2 I made with ROM Manager weeks ago, then applied the update to 4.0.4 again, and it ran smoothly with no errors, since all System apps were installed with the clean image I saved.
Hope this helps...
PaisanNYC said:
Actually, this is true. I was having the same issues. When i rooted, I deleted system apps I did not want. For weeks and weeks I kept receiving the popup message saying that the update to 4.0.4 was available. When attempting to upgrade, it would always fail on reboot.
Just two days ago, I received the upgrade notice again. I immediately went into Recovery mode, and attempted to manually install the update file from the system directory. When I did, I received an error right away saying the update could not find "TabletBooks.apk" (I deleted Google Play Books since I dont use it).
I reinstalled a clean image of 4.0.2 I made with ROM Manager weeks ago, then applied the update to 4.0.4 again, and it ran smoothly with no errors, since all System apps were installed with the clean image I saved.
Hope this helps...
Click to expand...
Click to collapse
If you are going to install a clean image anyway, it doesn't make much sense to install 4.0.2 and upgrade to 4.0.4. Just install the 4.0.4 image immediately...
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
If you are going to install a clean image anyway, it doesn't make much sense to install 4.0.2 and upgrade to 4.0.4. Just install the 4.0.4 image immediately...
Click to expand...
Click to collapse
Because you cant just download the full 4.0.4 image and install it via Recovery, can you? I thought you can only install the full image via ADB?
I was able to do all of this while sitting down in the lil boys room, doing my business LOL
PaisanNYC said:
Because you cant just download the full 4.0.4 image and install it via Recovery, can you? I thought you can only install the full image via ADB?
I was able to do all of this while sitting down in the lil boys room, doing my business LOL
Click to expand...
Click to collapse
LOL!
Well, I'm not sure where you got a stock 4.0.2 CWM-flashable file, but FYI, you can flash 4.0.4 the same way if you have a 4.0.4 CWM-flashable file (or just replace the 4.0.2 image with the 4.0.4 image in the same CWM-flashable file.
efrant said:
LOL!
Well, I'm not sure where you got a stock 4.0.2 CWM-flashable file, but FYI, you can flash 4.0.4 the same way if you have a 4.0.4 CWM-flashable file (or just replace the 4.0.2 image with the 4.0.4 image in the same CWM-flashable file.
Click to expand...
Click to collapse
Thanks, that's good to know! I come from HTC phones (G1, Nexus One, etc), so Samsung and modding is kinda new to me.
I had a CWM-flashable 4.0.2 file because ROM Manager created the image for me when I first rooted and wanted a backup of a clean stock ROM. I wouldnt even know where to find a CWM-flashable 4.0.4 file on the web. I only know of the stock source files Google has posted. I read that those files can only be flashed with ADB on a PC.
Thanks again!
PaisanNYC said:
Thanks, that's good to know! I come from HTC phones (G1, Nexus One, etc), so Samsung and modding is kinda new to me.
I had a CWM-flashable 4.0.2 file because ROM Manager created the image for me when I first rooted and wanted a backup of a clean stock ROM. I wouldnt even know where to find a CWM-flashable 4.0.4 file on the web. I only know of the stock source files Google has posted. I read that those files can only be flashed with ADB on a PC.
Thanks again!
Click to expand...
Click to collapse
Oh, you were referring to a CWM backup. I understand now.
But regardless, you can still flash the Google images via CWM, they just have to be packaged up in a CWM-flashable zip.
Sent from my Galaxy Nexus using Tapatalk 2
Thanks for all help. I'm succesfull flash my GNex.
Okay, I was on ICS 4.0.4 Yakju build. I flashed it using Gnex tool kit and then rooted the phone as well. Also left the bootloaded unlocked.
Today I received the OTA 4.1.1 Jelly Bean update. I began with the procedure and it downloaded well and good but then the installation was interrupted and the phone booted into my old 4.0.4 version. As it turns out, you should not accept the OTA update if you're rooted (lucky, I got away with it). I dont exactly know what caused my installation to fail, the root or the unlocked bootloader or both. Anyway, I used Gnex Tool Kit and 'Flashed the Google Factory Stock Rom' (exactly the same way how I got the yakju 4.0.4 build in the first place) , that left my phone with just as new Stock 4.0.4, UNROOTED with locked bootloader! Just like out of the box. Then I went on with my OTA update and it went through like a charm.
Anyway, now I'm on 4.1.1 Jelly Bean. I want to root the phone because I use too many apps that requires root access. So the latest version of Gnex Tool Kit (7.4) supports Jelly Bean root. But I dont wanna Root my phone this time unless I know how to UnRoot it. Don't wanna go against OTAs. (might start using CM rom when the next android version comes out) but till then I only want OTA updates.
So, can anyone tell me how to UNROOT the 4.1.1 Jelly Bean? (without wipe or deleting all the data) It'll be awesome if it can be done by Gnext Tool Kit. If not, then I dont mind doing it the hard way.
I wanted to post this question in 'Gnext toolkit' forum but I dont have enough privileges. So please help me out
As you can see I'm a noob. So please excuse my ignorance :/
Thanks a lot
Nobody? Please anyone help
Well root and your bootloader status (unlocked or not) really shouldn't affect your ability to receive an OTA IIRC. It should still work successfully although you may lose root.
Anywho, to unroot all you have to do is delete the 'superuser' application whether it be Superuser or SuperSu and then delete 'su' in /system/bin. That should work though IMO the cleanest way to unroot is to just restore the stock images.
Unlawful said:
Anywho, to unroot all you have to do is delete the 'superuser' application whether it be Superuser or SuperSu and then delete 'su' in /system/bin. That should work though IMO the cleanest way to unroot is to just restore the stock images.
Click to expand...
Click to collapse
Well, I guess you cant uninstall SuperUser. I tried that before updating but it acts like a system app and you cant delete it, unless you have 'System app remover' software, but then again it needs Root access to work so the whole thing is pointless I guess
And restore stock image HOW? I mean can you elaborate a lil please!
Using Gnex Tool Kit, which option? (my guess, 'Flash Google Factory Stock Rom' cuz for me it works but it wipes all your data.. backup solution?)
Super su has an unroot option
Here's a screenshot attached
Hit Thanks if i helped
Niallfitzy1 said:
Super su has an unroot option
Click to expand...
Click to collapse
Hey thanks
But does it work on Jelly Bean?? Also, when you Root Gnex using ToolKit then you have SuperUser and not SuperSU :| Whats the way around it?
tojonegi said:
Hey thanks
But does it work on Jelly Bean?? Also, when you Root Gnex using ToolKit then you have SuperUser and not SuperSU :| Whats the way around it?
Click to expand...
Click to collapse
Installing supersu and giving it root access to update such binary removes original superuser apps control you can switch just by downloading super su so it should work, cannot test myself though
Hit thanks if I helped
Niallfitzy1 said:
Installing supersu and giving it root access to update such binary removes original superuser apps control you can switch just by downloading super su so it should work, cannot test myself though
Hit thanks if I helped
Click to expand...
Click to collapse
Okay thanks, I'm gonna try this ^^
Hope it works well in the future while receiving OTA updates
P.S. I'd already hit Thanks
I'm running the JB 4.1 version that was released with the dev units during Google I/O -- Now it's constantly telling me to update, and when I update, it fails.
Now, I want to "upgrade" to a CM 10 nightly.
Do I have to wipe and install or can I just install?
If you want to go to CM10, you need to 100% wipe that device before installing.
If you want to try and diagnose the issue you're having taking the OTA to 4.1.1, we can work through that too.
Alright. What do you need to know?
iFargle said:
Alright. What do you need to know?
Click to expand...
Click to collapse
To try and accept the OTA?
How did you install this 4.1? Did you flash the proper radio with it? Do you have a custom recovery? Are you rooted? Have you changed or uninstalled any system apps? What error do you get (what happens) when you try to accept the OTA?
We need to know what you flashed... Did you just flash the ROM or flashed radio, bootloader and recovery for that variant? If you didn't flash them, you gotta do it. If not, you can't update.
However, if you did flash everything, just flash them one more time just to make sure. Sometimes, people get confused and flash wrong version of radio and stuff...
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
I am rooted and unlocked, yes. I installed this 4.1 image using clockworkmod recovery. I don't even know what a custom recovery is, so I assume I do not have one of those.
Ah, I did disable one system app -- Google Play Magazines. As soon as the update popup comes back I will try again... Since now when I go and click on the check updates button it tells me I'm up to date, even though it's still 4.1.
iFargle said:
I am rooted and unlocked, yes. I installed this 4.1 image using clockworkmod recovery. I don't even know what a custom recovery is, so I assume I do not have one of those.
Ah, I did disable one system app -- Google Play Magazines. As soon as the update popup comes back I will try again... Since now when I go and click on the check updates button it tells me I'm up to date, even though it's still 4.1.
Click to expand...
Click to collapse
Disabling any apps wouldn't matter. However, you just said that you have Clockworkmod, right? If it's, there's your problem. Flash stock recovery and you should be good to go
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz
I can see Android v4.1.1 on System, About, but I totally forget what ROM I flashed. One of the more popular ones, last October or so. How do I tell what is on the phone?
Thanks, and sorry for the dumb question...
Dougmeister said:
I can see Android v4.1.1 on System, About, but I totally forget what ROM I flashed. One of the more popular ones, last October or so. How do I tell what is on the phone?
Thanks, and sorry for the dumb question...
Click to expand...
Click to collapse
Don't you have the rom zip saved? It should say what rom it is. Although you should know what you are flashing.
Sent from my Clean Bean v2.6 Galaxy S3
Dougmeister said:
I can see Android v4.1.1 on System, About, but I totally forget what ROM I flashed. One of the more popular ones, last October or so. How do I tell what is on the phone?
Thanks, and sorry for the dumb question...
Click to expand...
Click to collapse
System settings / build number
Sent from my blue galaxy
miller710 said:
System settings / build number
Click to expand...
Click to collapse
Hmmm. Maybe I never *did* flash anything...
"Build number JRO03L.L710VPBLJ7"
Doesn't that mean plain old Jelly Bean?
I vaguely remember installing Clockwork Mod so I could get JellyBean early.
I guess I want to uninstall Clockwork Mod so I can do OTA updates from Sprint, etc. I found these threads, but they are for Galaxy Tab 2...:
http://forum.xda-developers.com/showthread.php?t=1800175How to Uninstall Clockwork Mod Recovery?[/URL]
[ODIN STOCK ROM] GT-P3113 Stock ROM for Odin flash
But since last fall, I've had to re-install Windows.
So, two questions:
1) Jellybean is standard on Galaxy S3's by now, right?
2) What do I need to install on my PC to uninstall Clockwork Mod Recovery? Odin? Anything else?
Thanks.
Dougmeister said:
Hmmm. Maybe I never *did* flash anything...
"Build number JRO03L.L710VPBLJ7"
Doesn't that mean plain old Jelly Bean?
I vaguely remember installing Clockwork Mod so I could get JellyBean early.
I guess I want to uninstall Clockwork Mod so I can do OTA updates from Sprint, etc. I found these threads, but they are for Galaxy Tab 2...:
http://forum.xda-developers.com/showthread.php?t=1800175How to Uninstall Clockwork Mod Recovery?[/URL]
[ODIN STOCK ROM] GT-P3113 Stock ROM for Odin flash
But since last fall, I've had to re-install Windows.
So, two questions:
1) Jellybean is standard on Galaxy S3's by now, right?
2) What do I need to install on my PC to uninstall Clockwork Mod Recovery? Odin? Anything else?
Thanks.
Click to expand...
Click to collapse
I would suggest searching the Q&A thread for all this. You should read up before you start installing roms or doing any mods to your phone.
Sent from my Freeza MC3 Stock Rooted Galaxy S3
TheSocalGuy79 said:
I would suggest searching the Q&A thread for all this. You should read up before you start installing roms or doing any mods to your phone.
Sent from my Freeza MC3 Stock Rooted Galaxy S3
Click to expand...
Click to collapse
Thanks. Will do.
Dougmeister said:
Hmmm. Maybe I never *did* flash anything...
"Build number JRO03L.L710VPBLJ7"
Doesn't that mean plain old Jelly Bean?
I vaguely remember installing Clockwork Mod so I could get JellyBean early.
I guess I want to uninstall Clockwork Mod so I can do OTA updates from Sprint, etc. I found these threads, but they are for Galaxy Tab 2...:
http://forum.xda-developers.com/showthread.php?t=1800175How to Uninstall Clockwork Mod Recovery?[/URL]
[ODIN STOCK ROM] GT-P3113 Stock ROM for Odin flash
But since last fall, I've had to re-install Windows.
So, two questions:
1) Jellybean is standard on Galaxy S3's by now, right?
2) What do I need to install on my PC to uninstall Clockwork Mod Recovery? Odin? Anything else?
Thanks.
Click to expand...
Click to collapse
Might I interject here? If the only reason you want to go back to stock recovery is to get the OTA updates, I personally don't think you need to. Typically, Freeza has the most up-to-date Stock, Rooted Rom over in his thread. In my case, he usually has it well before I get the OTA notification from Sprint. If you think his thread is daunting to look at, you really only want to flash one of the following (I always remove direct links to the Roms out of respect for the dev's):
freeza said:
[size=+4]Leaked Builds[/size]
MC3 Full ROM (DeOdex): Sprint Touchwiz Jelly Bean 4.1.2 L710VPBMC3 | Mirror (Thanks HashTagHell)
MD5: 8D714F25612D2CA8F103A63DF902E607
[size=+4]Official Software[/size]
FULL ROM:
DeOdex:
Sprint Touchwiz Jelly Bean 4.1.2 L710VPBMB1 | Mirror | Mirror 2 (Not yet active)
MD5: 37E1CCCB3A30959C64DF238D0BD2B23C
Click to expand...
Click to collapse
The MC3 Rom is a leak of a new OTA that might come out soon (or it'll be incorporated in a future OTA). The MB1 Rom is the most current, stock Rom. All you have to do is flash it and you're updated. If you need help with how to flash it, you can look to my post over here. Since you're going from 4.1.1 to 4.1.2, I'd recommend a "clean install" (step 5 in my instructions) just to minimize the chance of Force Closes, but you should be good if you want to do a "dirty flash" (only wipe cache and dalvik cache). If you dirty-flash, though, any and all troubleshooting will boil down to doing a clean install and seeing if the problem persists.
Also, CNexus has written up a really good OTA Guide to help you understand the whole OTA thing more and to recognize your options. You can check out his post over here.
Hope this helps!
Edit: It might also be good to update your Recovery before proceeding. Depending on how old your CWM is, it might be best to get an updated one (with hopefully fewer bugs). Thankfully, Naddict has created updates that are flashable from the Recovery itself. All you have to do is download the one you want (I'm using TWRP 2.5.0.0, but CWM is fine, too) and flash it in your custom Recovery, then reboot into recovery again.
topherk, thanks!
I took your advice and upgraded my ClockworkMod. (I also installed TWRP, which I think overwrote it, but that's another story).
I'm going to go over your post in more detail (hopefully) this weekend.
I tried flashing some different ROMs to see what they were like. I was not impressed, so I went back to stock.
Can you tell me something? If I use TWRP to back up everything, I still need to install GAPPS, right? Then I need to do something with GAPPS and Platinum Backup before I wipe/re-install to keep all/most of my programs/settings, right? Then run GAPPS again after I flash the new ROM?
Dougmeister said:
I took your advice and upgraded my ClockworkMod. (I also installed TWRP, which I think overwrote it, but that's another story).
Click to expand...
Click to collapse
Yeah, you can only have one recovery installed at once. I use TWRP, others use CWM. In my opinion, it shouldn't matter too much. They're both good and as far as I'm aware, the newest of each are relatively bug-free. The only thing is once you have backups for one, you can't restore them with the other. This isn't that big of a deal, but just an FYI.
Dougmeister said:
Can you tell me something? If I use TWRP to back up everything, I still need to install GAPPS, right? Then I need to do something with GAPPS and Platinum Backup before I wipe/re-install to keep all/most of my programs/settings, right? Then run GAPPS again after I flash the new ROM?
Click to expand...
Click to collapse
I'll break your questions here:
As far as I'm aware, all TouchWiz Roms include GAPPS in them by default. Of the flip side, no AOSP Roms will include them. This is because Google has asked dev's to not include them (in a Rom) unless specifically approved by Google. Samsung has gotten that approval for their TW framework, so any Rom based on TW can (and do) include GAPPS. If you're in doubt and the Rom doesn't say, first re-read the thread, as it's a common question. Then you can just flash the Rom without GAPPS and load up your phone. If GAPPS is included, you'll have a play store. If not, then you can just reboot into recovery and install it. Easy as pie.
I believe you mean Titanium Backup (another precious metal). Using TiBk, I actually have an automatic restore done every morning at 3am. Then if I decide to flash a new Rom, I always have an up-to-date backup of my apps. I never restore system apps, as that's just asking for trouble when switching Roms. I always back up my messages and phone log, but nothing that's red in TiBk. And for most apps, you don't have to restore data (only the app). I only restore data for games and apps like Hulu so I don't have to log in again.
Hoep this helps!
Yeah stock based roms will include GAPPS, AOSP roms cant because they arent officially licensed to distribute them...
As for the original question, I think I have it figured out. If you go to /system/build.prop and open that file, the great majority of devs will modify the relevant lines to the name of their custom roms. On cm roms theres a line called "cm.version=", which devs will usually modify that on a CM rom
The name is in there somewhere...could be changed on a couple lines, or on ALL the relevant lines, but it will be changed most of the time
Hope this helps
Is there a way to just directly upgrade Jellybean from 4.1.1 to 4.1.2 without having to re-install (via Gapps?) all of my applications, etc.?
I thought I read that I could unroot, do the OTA upgrade, then root again? I'm reading the OTA guide by CNexus, and 'freezing' the update app seems like a good option, but that just keeps the nag screen away.
Dougmeister said:
Is there a way to just directly upgrade Jellybean from 4.1.1 to 4.1.2 without having to re-install (via Gapps?) all of my applications, etc.?
I thought I read that I could unroot, do the OTA upgrade, then root again? I'm reading the OTA guide by CNexus, and 'freezing' the update app seems like a good option, but that just keeps the nag screen away.
Click to expand...
Click to collapse
All you need to do is follow the guide. You can download the MB1 firmware from freezas thread, and then flash an updated version of your rom. If you are on stock rooted, then you can flash one of freezas plain stock rooted roms over what you have (i would recommend a backup first though)
Just a small correction Gapps strictly refers to Google made apps (maps, play store, books, etc) you usually only flash these when working with AOSP roms. You sound like your talking about Touchwiz roms and thus your not loading all your apps through gapps, because Gapps are already included with Touchwiz roms. What you are referring to is reloading all your apps through Google Play Store and using the Google restore feature.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Yes! I'm talking about:
1) Backing up everything on my Galaxy S3
2) Installing other ROMs (sometimes stock, sometimes AOSP)
(side question: "stock" = "TouchWiz"???)
3) Magically re-installing *all* of my apps in the new ROM by clicking a single button
To do that, I'll need to use the "Google restore" feature?
Dougmeister said:
Yes! I'm talking about:
1) Backing up everything on my Galaxy S3
2) Installing other ROMs (sometimes stock, sometimes AOSP)
(side question: "stock" = "TouchWiz"???)
3) Magically re-installing *all* of my apps in the new ROM by clicking a single button
To do that, I'll need to use the "Google restore" feature?
Click to expand...
Click to collapse
Titanium backup is what I use. Paid version and you dont have to click ok for each app
Sent from my blue galaxy
miller710 said:
Titanium backup is what I use. Paid version and you dont have to click ok for each app
Sent from my blue galaxy
Click to expand...
Click to collapse
You don't have to hit ok for each app when you use google restore the correct way. It automatically reloads your apps on your device. TB is a great also but never restore data it is the root of most issues caused when people use it.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Hi, I have a rooted nexus 7 and wanted to run multiple ROMs using Multirom and have and use root access on each of them. I cant figure out a way to do this and would like a little help. My Nexus 7 is running Android 4.4.4 and fully rooted on stock kernel and ROM at the moment. If anyone knows how to enable root on multiple ROMs please help me and let me know how. Thanks!
> Phoenex
Phoenex said:
Hi, I have a rooted nexus 7 and wanted to run multiple ROMs using Multirom and have and use root access on each of them. I cant figure out a way to do this and would like a little help. My Nexus 7 is running Android 4.4.4 and fully rooted on stock kernel and ROM at the moment. If anyone knows how to enable root on multiple ROMs please help me and let me know how. Thanks!
> Phoenex
Click to expand...
Click to collapse
1. Download MultiROM Manager From The Play Store
2. Download the files required. Install Them. (This will install The TWRP recovery)
3. Download A Rom.
4. Reboot Into Recovery Mode->Advanced->MultiROM->Add New Rom
A Delailed Guide Is Available. Just Google "Multirom Nexus 7 XDA"
aniket0317 said:
1. Download MultiROM Manager From The Play Store
2. Download the files required. Install Them. (This will install The TWRP recovery)
3. Download A Rom.
4. Reboot Into Recovery Mode->Advanced->MultiROM->Add New Rom
A Delailed Guide Is Available. Just Google "Multirom Nexus 7 XDA"
Click to expand...
Click to collapse
Thank you for your quick response, I already have MultiROM installed but want root access on the other ROMs. Whenever I boot the other ROMs now most Google applications crash instantly and I can't open them without them crashing again. When I open SuperSU it says that Android versions after 4.3 need to re-root to update binary. How would I update the binary and prevent Google Applications from crashing when opened?
Phoenex said:
Thank you for your quick response, I already have MultiROM installed but want root access on the other ROMs. Whenever I boot the other ROMs now most Google applications crash instantly and I can't open them without them crashing again. When I open SuperSU it says that Android versions after 4.3 need to re-root to update binary. How would I update the binary and prevent Google Applications from crashing when opened?
Click to expand...
Click to collapse
Need more info:
Which ROM?
Which GAPPS?
How did you install them?
Don't Say Thanks.
Press The Thanks Button.
My Devices:
Nexus 7 2013 LTE "DEB"
Stock ROM 4.4.3
Stock Kernel
Build: KUT48L
"Everything's Impossible. Until Someone Does It."
The Dark Knight
Most custom Roms are already rooted. Crashes are not normal. Are you using a patched kernel? Are you choosing to share kernel? Like previous poster said, you need to give more info. You're missing something.
My ROM is just a stock ROM. I am using MultiROM and SuperSU to manage ROMs and root access. Here is a screenshot of my main ROM which is the same one as the secondary. Also, I provided screenshots of SuperSU recognizing MultiROM which I granted access to. I don't see a reason for not having root access on both but I am new to rooting and may have overlooked something. I installed the ROMs and rooted using Nexus Root Toolkit. Let me know if you need more information I would be happy to share.
Why not flash a pre rooted ROM for secondary? And ROM management should be handled in twrp. In twrp select advanced then multirom. You can flash zips for secondary rom there.
I used TWRP to install my secondary ROM. What pre-rooted ROM's would you recommend? I'm looking for some new ROMs to run and I don't know where to start.
Phoenex said:
I used TWRP to install my secondary ROM. What pre-rooted ROM's would you recommend? I'm looking for some new ROMs to run and I don't know where to start.
Click to expand...
Click to collapse
I use PAC ROM for my secondary ROM. I keep rooted stock as my primary, but I plan to swap them soon once I get it set up right.
Cm does not work right in MultiROM for me. Paranoid Android, PAC, Slimroms, etc should be good.
Press Thanks If I Helped You!
Sent from my dead Nexus 7 2013 LTE! ???